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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add a note to serviceMonitor #345

Merged
merged 2 commits into from
Apr 15, 2021
Merged

docs: add a note to serviceMonitor #345

merged 2 commits into from
Apr 15, 2021

Conversation

shaneutt
Copy link
Member

Sometimes values.yaml fields can be slightly misleading, in
this case setting serviceMonitor.enabled=true doesn't inherently
place the label for all components (such as the admin api) and it
may not be intuitive that several other configurations must be updated
in order to achieve that. As such this commit adds some helper text
and a link to the README to provide some hints, and more context.

Resolves #311

Sometimes `values.yaml` fields can be slightly misleading, in
this case setting `serviceMonitor.enabled=true` doesn't inherently
place the label for all components (such as the admin api) and it
may not be intuitive that several other configurations must be updated
in order to achieve that. As such this commit adds some helper text
and a link to the README to provide some hints, and more context.
@shaneutt shaneutt added the documentation Improvements or additions to documentation label Apr 14, 2021
@shaneutt shaneutt self-assigned this Apr 14, 2021
@shaneutt shaneutt requested a review from a team as a code owner April 14, 2021 21:11
@shaneutt shaneutt requested a review from rainest April 14, 2021 21:12
Copy link
Contributor

@rainest rainest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll still try and push for brevity here 🙂

We also don't want to imply that there are admin API metrics--there aren't, and the label really should be set on one service only. A DeploymentMonitor would be more appropriate for how our metrics actaully work, but the Prometheus operator doesn't offer that.

charts/kong/values.yaml Outdated Show resolved Hide resolved
@rainest rainest changed the base branch from main to next April 14, 2021 21:27
Co-authored-by: Travis Raines <traines@konghq.com>
@shaneutt shaneutt requested a review from rainest April 15, 2021 00:00
@rainest rainest merged commit 474d9e0 into next Apr 15, 2021
@rainest rainest deleted the docs-2021-04-14 branch April 15, 2021 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ServiceMonitor does not select for kong CP
2 participants