-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop Monitoring Concept #21
Comments
Das HelmChart gibt es schon (nicht 100% aktuell), aber StatsD Support ist (noch) nicht exposed: |
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
The cloudwatch cluster agent project seems to be quite stale. |
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
There are different ways of how we could implement Monitoring.
Current Ideas:
1. Use Cloudwatch
The cloudwatch cluster agent can be used to push metrics to cloudwatch
Cons:
2. Use Managed Prometheus
Install Prometheus to the cluster to forward metrics to AWS managed prometheus
Pros:
Cons:
3. Use Prometheus Operator
Pros:
Cons:
4. Use Prometheus Operator with Managed Prometheus
Use a combination of both, 3 and 4.
Pros:
We have to come up with an ADR outlining our decisions.
The text was updated successfully, but these errors were encountered: