-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Aerospike agent and dashboards #19188
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
base: master
Are you sure you want to change the base?
Aerospike agent and dashboards #19188
Conversation
The changelog type |
4 similar comments
The changelog type |
The changelog type |
The changelog type |
The changelog type |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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 |
The changelog type |
updated the expected metric names used in testing
The changelog type |
sdded additional metrics required for assertion
The changelog type |
corrected metadata.csv to match the incoming metrics
The changelog type |
sorted metric names in metadata added missing metrics between commons.py and metadata.py
The changelog type |
reverted latency metrics treatment as gauge, will include this along with latency dashboard
…aerospike-datadog-integrations-core into aerospike-agent-and-dashboards
modified dashboards with the updated metric naming convention
…aerospike-datadog-integrations-core into aerospike-agent-and-dashboards
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