Prometheus To Cloudwatch Versions Save

what

• Sanitize values before sending to CloudWatch

why

• Throw away data points with known invalid values to avoid the whole batch being rejected by CloudWatch API

what

• Handle OS signals to stop gracefully

why

• Cancel the context on receiving SIGINT or SIGTERM

what

• Add optional metrics filtering

why

• Configuration options to provide whitelist and blacklist patterns for metrics, so that only a subset of available metrics is exported from Prometheus to CloudWatch

what

• Add ability to replace dimensions

why

• This is useful to aggregate metrics across dimensions in the kube-state-metrics namespace. The aggregation across dimensions is necessary for adding CloudWatch alarms to kube-state-metrics for the variable number of pods/container/nodes that will exist in EKS clusters

what

• Update README

why

• Some minor fixes (e.g. screenshots)

what

• Send metrics with additional dimension (ex. instance-id or container-id).

prometheus-to-cloudwatch -cloudwatch_namespace xxx -prometheus_scrape_url http://localhost:4000/metrics -additional_dimension container_id=$(cat /etc/hostname) &

why

• disambiguate data

what

• Update glide dependencies

why

• Wrong Go dependencies in glide.yaml. Travis build fails

what

• Utility for scraping Prometheus metrics from a Prometheus client endpoint and publishing them to CloudWatch

why

• To make it easier to scrape metrics from Prometheus client endpoints and push the metrics to CloudWatch