Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Observability Tooling #519

Open
omrishiv opened this issue May 8, 2024 · 0 comments
Open

feat: Observability Tooling #519

omrishiv opened this issue May 8, 2024 · 0 comments

Comments

@omrishiv
Copy link

omrishiv commented May 8, 2024

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Having some observability built in to Data on EKS would be very helpful for understanding the environment performance, application status, and cost.

Describe the solution you would like

It would be great to have an observability stack built on well supported tooling that would expose: metrics, logs, traces, and costs. A stack built with Grafana, Prometheus, Loki, and OpenCost would support an open source solution that facilitates the pillars of observability.

Describe alternatives you have considered

There is the possibility of using SaaS products for observability, but I believe that a community supported solution should be a minimum availability as part of Data on EKS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant