-
Notifications
You must be signed in to change notification settings - Fork 170
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
Emit Cluster Feature Metrics for Cluster Operations #3631
Conversation
0290d4f
to
4288b86
Compare
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.
I have some questions around the specific dimensions we're emitting - I want to make sure that each individual dimension we include on these metrics is explicitly useful to us so we're not introducing noise into our observability.
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.
Good work! I recommended adding unit tests for emitMetrics
and left a few other smaller question/concerns.
4d24062
to
27a3684
Compare
6048e8c
to
ecbdf64
Compare
Add workload identity or cluster service principal metrics emission Add emit features Emit features concerning newly installed clusters. Add emitMetrics to all provisioning states Add logging statements for metrics, Allows metrics being emitted to also be used in kusto dashboards. Constant values are used for all metric names in deminsions. If an error is encountered while gathering metrics, that metric is omitted. Unit tests provide 100% coverage for emitMetrics. Rename emitMetrics to emitProvisioningMetrics, rename emitInstallMetrics to emitMetrics, emitMetrics can be used for all provisioning states, not just creating state. Changed name to reflect this.
ecbdf64
to
9d1aa64
Compare
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
78ff980
to
a99acf9
Compare
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
lgtm
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
Which issue this PR addresses:
ARO-7839
Fixes
What this PR does / why we need it:
Emit metrics for all RP operation types, creating, updating, adminupdating, and deleting.
Test plan for issue:
Covered by unit tests.
Is there any documentation that needs to be updated for this PR?
No
How do you know this will function as expected in production?