When API resource usage has increased either gradually or suddenly, it's important to understand why, so that there aren't resource-related issues that occur as a result of over-utilization of the API pods.
If API resource usage becomes too high, it can result in OOM events with etcd or API pods, and can more severely result in cluster outages if left unaddressed.
It's possible to do this same task with API audit logging, but these results can be
This is an example of the Prometheus dashboard graphing API usage for diagnostic purposes. We can see that Tiller and template service broker are currently responsible for the greatest amount of requests to the API.
cluttered and difficult to interpret.
This is an example of the Prometheus dashboard graphing API usage for diagnostic purposes. We can see that Tiller and template service broker are currently responsible for the greatest amount of requests to the API.
Environment
OpenShift Container Platform
3.11
Prometheus Monitoring
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
~~~
Code surrounded in tildes is easier to read
~~~
Links/URLs
[Red Hat Customer Portal](https://access.redhat.com)
Request a English Translation
Are you sure you want to request a translation?
We appreciate your interest in having Red Hat content localized to your language. Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated.
Generating Machine Translation
Loading…
We are generating a machine translation for this content. Depending on the length of the content, this process could take a while.
