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

Read Results API service metrics from api-for-watcher #5595

Merged

Conversation

enarha
Copy link
Contributor

@enarha enarha commented Feb 18, 2025

Splitting the load of the Results API service, switched the watcher/controller related request to a new pod which handles most of the load. With the original service now used only by users, it gets much less load (that was the purpose), but it triggers some false positives from the monitoring service. Here we switch the ServiceMonitor to the new pods running most of the load.

Splitting the load of the Results API service, switched the
watcher/controller related request to a new pod which handles most of
the load. With the original service now used only by users, it gets much
less load (that was the purpose), but it triggers some false positives
from the monitoring service. Here we switch the ServiceMonitor to the
new pods running most of the load.
Copy link

openshift-ci bot commented Feb 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: enarha

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

@aThorp96 aThorp96 left a comment

Choose a reason for hiding this comment

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

@enarha I'm worried that this could be a moving target, and could potentially cause the service monitor to falsely alert on request volume for the regular results-api service.

What do you think about instead doing the following, like we do with Tekton Chains:

  • on the Results services, add the labels app.kubernetes.io/component: with watcher and api respectively
  • switch the label selector to use app.kubernetes.io/part-of: tekton-results and app.kubernetes.io/component: api.

@openshift-merge-bot openshift-merge-bot bot merged commit 75a9306 into redhat-appstudio:main Feb 18, 2025
6 checks passed
@enarha enarha deleted the read-metrics-api-for-watcher branch February 19, 2025 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants