amazon-managed-service-for-prometheus-roadmap
amazon-managed-service-for-prometheus-roadmap copied to clipboard
aws
Amazon Managed Service for Prometheus Public Roadmap
I want to integration AMP with Managed Grafana to manage (create/edit/delete) alerts. However, in order to do this the AlertManager datasource must be created with type=Cortex. Unfortunately, AWS support has...
In addition to regular deletion after the (custom #2) retention period, the ability to delete individual and/or multiple metrics/time series is needed. Deletion becomes necessary when * the data quality...
Currently, creating a new AMP workspace always results in a publicly accessible endpoint being created. The endpoint is secured with IAM, but we prefer no public endpoint at all, only...
Please consider adding 'modern' Go syntax behaviors to make formatting templates more idiomatic, functions that I'd propose are: map, dict, split, splitList, regexMatch, lower, contains, strings, if Also a mechanism...
I've reported this to AWS support as well. As near as I can tell 100% of the log messages in AWS cortex are useless. Log messages should provide a hint...
At this time Amazon Managed Prometheus only sends traffic to SNS. Chatbot only supports traffic [routed through event bridge](https://docs.aws.amazon.com/chatbot/latest/adminguide/create-eventbridge-rule.html). Getting alerts through Slack is highly desirable as another route for...
## Use case 1 A Prometheus Counter metrics is an incremental metric that takes a new datapoint and adds/subtracts value to existing counter value. In scenarios where we wish to...
There is a demand for this feature to be supported on AMP, as this is supported on Grafana-agent (which we use to remote-write ec2 metrics) also supports this starting version...
I would like to see provision made for working out the cost of metrics given one or more labels on metrics, much like you would do using Tags on EC2...