-
Notifications
You must be signed in to change notification settings - Fork 54
[Docs] Monitoring of Kroxylicious on Kubernetes #2256
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for bootstrapping this @k-wall.
// kroxylicious-operator/index.adoc | ||
|
||
[id='assembly-prometheus-metrics-proxy-{context}'] | ||
= Proxy Metrics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily part of this PR but I think it might be worth talking about how to get an aggregate view of the proxy process and a view of a whole virtual cluster. e.g. total network throughput and then throughput per virtual cluster. As they are likely to the high level questions people operating the proxy are likely to ask.
136e2a3
to
9a97cc0
Compare
@k-wall Hi, Do we need to mentioned about deprecated metrics also? |
@PaulRMellor FYI - just putting this on your radar. |
No, we don't do that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great start.
The Java Operator SDK exposes metrics that allow its behaviour to be understood. These metrics | ||
are enabled by default in the Kroxylicious Operator. | ||
|
||
Refer to the {josdk-metrics}[Java Operator SDK metric documentation] to learn more about metrics. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't sufficient on its own, is it? Don't we need to say there the scrape endpoint is, for example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've covered that in con-proxy-ingesting-metrics.adoc (when running proxy on baremetal) and con-operator-ingesting-metric (when running proxy using the operator).
0c7a58d
to
222071e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, Keith. The procedures look clean, minimal, and easy to follow.
I've left a few more suggestions, mainly for layout and consistency
include::../modules/monitoring/proc-proxy-introducing-metrics.adoc[leveloffset=+1] | ||
include::../modules/monitoring/con-prometheus-metrics-proxy.adoc[leveloffset=+1] | ||
include::../modules/monitoring/con-{guide}-ingesting-metrics.adoc[leveloffset=+1] | ||
include::../modules/monitoring/con-{guide}-integrating-micrometer.adoc[leveloffset=+1] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This need excluding for downstream?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but that applies to the whole proxy-guide. It is just the operator-guide that will be used downstream.
docs/modules/monitoring/proc-operator-setting-log-levels-proxy.adoc
Outdated
F438
Show resolved
Hide resolved
docs/modules/monitoring/proc-operator-setting-log-levels-proxy.adoc
Outdated
Show resolved
Hide resolved
docs/modules/monitoring/proc-operator-setting-log-levels-proxy.adoc
Outdated
Show resolved
Hide resolved
docs/modules/monitoring/proc-operator-setting-log-levels-operator-olm.adoc
Outdated
Show resolved
Hide resolved
docs/modules/monitoring/proc-operator-setting-log-levels-operator-olm.adoc
Outdated
Show resolved
Hide resolved
Separate monitoring when deploying the proxy standalone from when the proxy is deployed by the proxy. Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
…us#2276 Signed-off-by: Keith Wall <kwall@apache.org>
make assembly-prometheus-metrics-operator.adoc a concept file. Signed-off-by: Keith Wall <kwall@apache.org>
Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
…ly-proxy-monitoring.adoc Signed-off-by: Keith Wall <kwall@apache.org>
why: help us keep the structure of the proxy/operator in synch, where it makes sense. Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Signed-off-by: Keith Wall <kwall@apache.org>
Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Signed-off-by: Keith Wall <kwall@apache.org>
|
Type of change
Select the type of your PR
Description
Documentation for the new metrics. The metrics need to be documented from the perspective direct use of the proxy, and use of the proxy via the operator.
Additional Context
Why are you making this pull request?
Checklist
Please go through this checklist and make sure all applicable tasks have been done