Open sky333999 opened 1 month ago
Introduce the ability to publish metrics to Amazon Managed Prometheus as a destination. Key highlights:
metrics_destinations
metrics
cloudwatch
amp
workspace_id
prometheusremotewriteexporter
sigv4authextension
rollup_dimensions
drop_original_metrics
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Manually tested changes on an EC2 to publish cpu metrics to AMP.
cpu
Before commit the code, please do the following steps.
make fmt
make fmt-sh
make lint
This PR was marked stale due to lack of activity.
Description of changes
Introduce the ability to publish metrics to Amazon Managed Prometheus as a destination. Key highlights:
metrics_destinations
undermetrics
section of the agent config. The two supported destinations arecloudwatch
(default if unspecified) andamp
.amp
destination requires theworkspace_id
as a required input. The remote write endpoint is built using a regex on top of the workspace ID.prometheusremotewriteexporter
to publish metrics to AMP.sigv4authextension
to sign API calls made to AMP using AWS credentials.rollup_dimensions
anddrop_original_metrics
functionality into a new processor that can be applied to non-cloudwatch destinations.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Manually tested changes on an EC2 to publish
cpu
metrics to AMP.Requirements
Before commit the code, please do the following steps.
make fmt
andmake fmt-sh
make lint