-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Conversation
"databasename" : "testdb" | ||
}, | ||
"database_account" : { | ||
"timegrain" : "PT5M", |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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" : { |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
* 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)
Should solve #15758
Lightweight metricset based on
monitor
Config:
extra config options as in the other metricsets:
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