Comments (6)
a way to use CRDs to configure the rules directly via the Kubernetes APIs
A definite +1 for this!
from amazon-managed-service-for-prometheus-roadmap.
Hey @razvan-moj,
Thank you for posting this issue! I would love to better understand this use case, and had a few follow up questions for you.
-
Have you seen our slack integration via SNS blog post? It walks through how to integrate AMP's alertmanager with Slack such that you have a very similar configuration paradigm to the native slack receiver. The blog can be found here. Would this solve your problem and allow you to use the AMP Alert Manager? If not, we'd love to learn a bit more as to why!
-
We are looking to eventually add support for the native slack receiver. If AMP's alert manager had the native slack receiver support, would that enable you to use the AMP Alert Manager? If not, would love to learn a little bit more about what's driving the use case!
Thank you for submitting this feature proposal! Excited to learn a bit more about the use case from you.
from amazon-managed-service-for-prometheus-roadmap.
Hey @ampabhi-aws !
- Have you seen our slack integration via SNS blog post? It walks through how to integrate AMP's alertmanager with Slack such that you have a very similar configuration paradigm to the native slack receiver. The blog can be found here. Would this solve your problem and allow you to use the AMP Alert Manager? If not, we'd love to learn a bit more as to why!
We have many (4000 odd as listed above) rules and alerts defined by users in their namespaces; those rules are picked up by Alertmanager once the .yaml is applied. Users do not have access to the AWS API. To change their setup to AMP it seems we need to need to change their workflow from kubectl apply
to terraform apply
and figure out a way to validate edits so they don't eg overwrite each other, something done now by the namespace isolation and a validation webhook. This work would not be needed if we could just configure the AWS Prometheus to read prometheusrules
from the namespaces and hook with the in-cluster Alertmanager.
- We are looking to eventually add support for the native slack receiver. If AMP's alert manager had the native slack receiver support, would that enable you to use the AMP Alert Manager? If not, would love to learn a little bit more about what's driving the use case!
I don't think this is a problem for us, if we decide to use the AWS API to interact with Prometheus, we can also allow SNS and our users are familiar with how it works.
from amazon-managed-service-for-prometheus-roadmap.
Thanks for the clarification @razvan-moj!
If we provided you a way to use CRDs to configure the rules directly via the Kubernetes APIs, and similarly configure your AMP alert manager via those CRDs, would that alleviate the need for an in-cluster Alertmanager? Trying to get a better sense of if the problem is (1) the AMP Alert manager is inconvenient to use, or (2) Doesn't fit the use case entirely.
from amazon-managed-service-for-prometheus-roadmap.
from amazon-managed-service-for-prometheus-roadmap.
@ampabhi-aws what are the next steps here?
from amazon-managed-service-for-prometheus-roadmap.
Related Issues (20)
- Amazon Managed Prometheus cannot send to Chatbot to route alerts to Slack [Feature Request] HOT 2
- Import existing Cortex metrics
- Ability to delete individual and/or multiple metrics/time series HOT 10
- Document or raise size limit for HELP text HOT 2
- Backfilling metrics data for migration purposes
- implement present_over_time() range function HOT 1
- Workspace's service quotas accessible through UI and CLI HOT 1
- Additional metrics and logging for query performance visibility
- Add ability to expose AMP endpoint *only* to private VPC HOT 2
- [Feature] Support for month-over-month and quarter-over-quarter queries HOT 1
- Make Prometheus TSDB metrics available for faster debugging of active usage
- Provide ability to wipe off data for AMP workspace/metrics HOT 3
- support alert manager "active_time_intervals" HOT 1
- Remove 1h backfilling limitation
- Enable remote read api protocol HOT 1
- Support for native histograms HOT 2
- Revise the custom storage retention solution HOT 1
- Expose additional Cortex API on Managed Prometheus to alert manager integration using Cortex type in Grafana HOT 1
- Managed Prometheus Workspaces Cost allocation based on metric labels
- DescribeLoggingConfiguration is missing from ReadOnlyAccess policy HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from amazon-managed-service-for-prometheus-roadmap.