MON-4414: Optional Monitoring Capability #1880
Conversation
Goes over the details for the `OptionalMonitoring` capability, which targets putting the in-cluster monitoring stack in a telemetry-only state. Note that the metric targets are not modified under this capability itself, but only when the telemetry collection profile is enabled.
openshift-ci-robot
added
the
jira/valid-reference
|
@rexagod: This pull request references MON-4414 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
rexagod
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
@rexagod: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| 4. Should we downscale Prometheus to a single replica when the | ||
| capability is disabled? | ||
| > Yes, since the monitoring footprint is reduced significantly | ||
| when the capability is disabled, moving away from an HA setup | ||
| to a single replica setup makes sense from a resource consumption | ||
| perspective. All components across OpenShift that rely on Thanos | ||
| will need to be "taught" to query the single Prometheus replica | ||
| directly instead of going through Thanos Querier. |
There was a problem hiding this comment.
(noting here that in this case, we will not support Genie; PTAL at this discussion)
3 participants
Goes over the details for the
OptionalMonitoringcapability, which targets putting the in-cluster monitoring stack in a telemetry-only state. Note that the metric targets are not modified under this capability itself, but only when the telemetry collection profile is enabled.