You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to monitor/alert situation when pods are not "mutated" by opentelemetry-operator.
For example if opentelemetry-operator is down, annotated pods are not going to be "mutated" and will continue to run without instrumentation.
What are the options to handle this situation
The text was updated successfully, but these errors were encountered:
That's what I was thinking about, but it will require a new application bundled with opetelemetry-operator helm chart, that queries k8s api and expose custom metrics that could be collected by grafana/prometheus. Quite a bit of work, so I wanted to check that I do not miss a simpler solution.
That's what I was thinking about, but it will require a new application bundled with opetelemetry-operator helm chart, that queries k8s api and expose custom metrics that could be collected by grafana/prometheus. Quite a bit of work, so I wanted to check that I do not miss a simpler solution.
But if the operator is down... the new application very likely will not be there neither.
Component(s)
auto-instrumentation
Describe the issue you're reporting
I would like to be able to monitor/alert situation when pods are not "mutated" by opentelemetry-operator.
For example if opentelemetry-operator is down, annotated pods are not going to be "mutated" and will continue to run without instrumentation.
What are the options to handle this situation
The text was updated successfully, but these errors were encountered: