Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add database_account azure metricset #16234

Merged
merged 13 commits into from
Feb 27, 2020
Merged

Add database_account azure metricset #16234

merged 13 commits into from
Feb 27, 2020

Conversation

narph
Copy link
Contributor

@narph narph commented Feb 11, 2020

Should solve #15758

Lightweight metricset based on monitor

Config:

  - module: azure
    metricsets:
    - database_account
    enabled: true
    period: 300s
    client_id: '${AZURE_CLIENT_ID:""}'
    client_secret: '${AZURE_CLIENT_SECRET:""}'
    tenant_id: '${AZURE_TENANT_ID:""}'
    subscription_id: '${AZURE_SUBSCRIPTION_ID:""}'

extra config options as in the other metricsets:

resources:
 - resource_group: []
 - resource_id: []

The metrics in https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported#microsoftdocumentdbdatabaseaccounts should be retrieved.
The DatabaseName dimension is applied for the metrics which support it.

cc: @sorantis

@narph narph requested a review from a team as a code owner February 11, 2020 13:57
@narph narph self-assigned this Feb 11, 2020
@narph narph added [zube]: In Progress Metricbeat Metricbeat Team:Platforms Label for the Integrations - Platforms team labels Feb 11, 2020
"databasename" : "testdb"
},
"database_account" : {
"timegrain" : "PT5M",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this field mapped by fields.yml?, we may need to add an entry

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps we should move it to azure.timegrain? as it's common to all metricsets

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed, I have moved timegrain inside the azure object as this is a common property for all metricsets

default: true
input:
module: azure
metricset: monitor
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️ to see this!

},
"database_account" : {
"timegrain" : "PT5M",
"provisionedthroughput" : {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we grouping metrics with the same dimensions & resource in a single document? That would save some space and make queries faster

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, all metrics with the same timegrain, dimension and resource are grouped in the same event

@narph narph requested a review from exekias February 25, 2020 13:47
x-pack/metricbeat/module/azure/_meta/fields.yml Outdated Show resolved Hide resolved
@narph narph merged commit 6816bb1 into elastic:master Feb 27, 2020
@narph narph deleted the azure-db branch February 27, 2020 09:52
@narph narph added the needs_backport PR is waiting to be backported to other branches. label Feb 27, 2020
narph added a commit to narph/beats that referenced this pull request Feb 27, 2020
* add metricset

* work on database_Account

* fix

* work on tests

* mage fmt update

* work on manifest

* update json

* move timegrain

* uppercase

(cherry picked from commit 6816bb1)
narph added a commit that referenced this pull request Feb 28, 2020
* Add database_account azure metricset (#16234)

* add metricset

* work on database_Account

* fix

* work on tests

* mage fmt update

* work on manifest

* update json

* move timegrain

* uppercase

(cherry picked from commit 6816bb1)

* changelog
@narph narph added test-plan Add this PR to be manual test plan v7.7.0 and removed needs_backport PR is waiting to be backported to other branches. labels Mar 27, 2020
@andresrc andresrc added the test-plan-added This PR has been added to the test plan label Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metricbeat Metricbeat Team:Platforms Label for the Integrations - Platforms team test-plan Add this PR to be manual test plan test-plan-added This PR has been added to the test plan v7.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants