-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Aerospike agent and dashboards #19188
base: master
Are you sure you want to change the base?
Aerospike agent and dashboards #19188
Conversation
modified check and metrics python scripts - -- to include all aerospike metrics most as gauge -- latency metrics are added as histograms added new dashboard covering key aerospike metrics required to be monitored includes, - cluster, node, namespace, sindex, sets, users, xdr, basic system-info and latencies
added CHANGELOG.md with details added and changed.
updated Aerospike pulgin version in about script
reverted the aerospike version to 4.0.0
reverted CHANGELOG.md to earlier and actual version generated changelog using ddev package from pypi with command "ddev release changelog new"
corrected the changelog files location
updated the correct PR number
The changelog type |
incorporated lint feedback and removed unnessary spaces
The changelog type |
removed unneceddary spaces at the end of the line as suggested in lint check
The changelog type |
removed unnecessary blank lines reported by lint at the end of file
The changelog type |
corrected comments
The changelog type |
renamed label cluster_name as aerospike_cluster as it is forbidden as per github checks,
The changelog type |
added mapping for cluster_name to aerospike_cluster - updated check.py
The changelog type |
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.
@mphanias thanks for taking the bull by the horns here!
I have a couple concerns with the PR as it is right now:
- We should not drop support for metrics we already collect. This will cause significant pain to folks who use older versions.
- I don't understand why tests were removed but no new ones were added.
- For the dashboards, have you had a look at these guidelines?
removed unnecessary dashboard links in node-view and sindex-view
1. fixed all dashboards as per the guidelines in document mentioned in review comments 2. fixed grammer issues
removed unique-data and datacenter-comparision dashboardss
Hi iliakur, Thank you for your feedback, please find my response inline,
Regards |
Hi iliakur, We modified the existing overview dashboard to use the actual metric names to ensure existing customer are not impacted. if any custom dashboard are designed by customers using old naming convention would have impact, but current proposed changes will ensure all customers can get the full benefits of all the metrics exposed by Aerospike Prometheus Exporter. Regards |
Hi iliakur, Could you please share your inputs or feedback on the comments I added, really appreciate your support. Regards |
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.
Hi Phani 👋
I'm afraid dropping metrics is out of the question for us. We often support technology that's EOL to avoid breaking the customers (even if they are few) that use it.
Dropping unit tests is also a no-go even if there's no significant transformation done to the prometheus payload. We would like our tests to guarantee the end to end customer experience and that involves ingesting and processing the prometheus payload. How trivial the processing is doesn't matter.
Hi iliakur, I understand your point of supporting EOL customer, I will add back all the test-cases and then re-add my add changes. while testing these changes in my local machine, I am facing some issue, could you please point me to any guide. appreciate your review feedback and support. Regards error I am getting - datadog_checks.base.checks.base.aerospike:aerospike.py:91 The |
What does this PR do?
Modified the aerospike integration to include all the metrics exposed by aerospike-pormetheus-exporter and multiple dashboard consuming the exported metrics.
Motivation
Expanding Metric Collection and Dashboards, we want to ensure all Aerospike metrics are available in datadog, so customers can have better visibility and provide actionable insights for key metrics, including performance, latency, and resource utilization.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged