Utility for scraping Prometheus metrics from a Prometheus client endpoint and publishing them to CloudWatch
This tool only published metrics with high resolution when the original prometheus metrics have the label _cw_high_res
.
However, in some cases where we run exporters and prom-to-cloudwatch
is connected to the exporters, we can't add the high res label
aws_session_token
argument, to enable use of temp AWS credentialsThis PR addresses a minor issue whereby temporary AWS credentials cannot be used to authenticate the AWS CloudWatch client. Temporary credentials require the use of an AWS_SESSION_TOKEN. This is currently set to "" in the NewStaticCredentials invocation.
This is mainly for manual testing purposes, as it is likely that most deployments of this app would be within an EC2 instance or Kubernetes cluster etc., where CW permission can be resolved by the chain of credential providers.
The format is:
EXCLUDE_DIMENSIONS_FOR_METRICS=metric_glob*=dim1,dim2;metric2_*=dim3;
# will exclude 'dim1' and 'dim2' from any metric matching 'metric_glob*'
# and 'dim3' from any metric matching 'metric2_*'
error validating data: ValidationError(Deployment.spec.template.spec): unknown field "resources" in io.k8s.api.core.v1.PodSpec;
This is because helm chart Deployment has resources
placed at Deployment.spec.template.spec.resources
where if should be at Deployment.spec.template.spec.containers[0].resources
instead