-
Notifications
You must be signed in to change notification settings - Fork 33
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
☂️ Monitoring #48
Comments
Additionally, I feel we should expose basic controller metrics for all deployers as well. In terms of further metrics: Maybe it would be interesting, if deployers would expose the connection time metrics? |
you mean how long does it take for a deploy item to be processed? |
That would be another valid option. What I had in mind was focusing more on traffic when there is a distributed setup with deployers and landscaper running in separate clusters. |
metrics added to OCI cache - gardener-attic/component-cli#3 |
a first implementation has been merged with #110 . This enables the landscaper-controller collect metrics of the controller-runtime and its OCI cache(s). Meaningful next steps would include:
Additionally, it could be interesting to expand the cache metrics with a histogram that gives insight into the file sizes. |
@schrodit Label priority/normal does not exist. |
We should also switch to OpenTelementry as poen standard for metrics. Also the controller-runtime is migrating towards that approach: kubernetes-sigs/controller-runtime#305 |
@In-Ko closed because outdated and/or copied into internal project |
How to categorize this issue?
/area monitoring
/kind epic
/priority 3
Umbrella issue to expose landscaper and deployer metrics and tracing got the various reconcile loops.
General:
Landscaper:
The issue is open for other aspects we can monitor
The text was updated successfully, but these errors were encountered: