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.

Sign up for GitHub

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

Jump to bottom

Update Knative Prow to use the new monitoring stack #3253

Open
chizhg opened this issue Apr 11, 2022 · 3 comments
Open

Update Knative Prow to use the new monitoring stack #3253

chizhg opened this issue Apr 11, 2022 · 3 comments
Assignees
@upodroid
Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure kind/enhancement priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Issues which should be fixed (post-triage)

Comments

@chizhg
Copy link
Member

chizhg commented Apr 11, 2022

As per the Prow owners, Knative Prow is currently using a legacy monitoring stack (in https://github.com/knative/test-infra/tree/5094d5004d5b9188e508024789d0e0dee2b1a866/prow/cluster/monitoring), which has been deprecated in favor of https://github.com/GoogleCloudPlatform/oss-test-infra/tree/master/prow/oss/terraform.

Since the legcy monitoring stack is not actively being maintained, and the new one is easier to setup and measure more valid metrics, Prow team's recommendation is to make the switch to it.

Please reach out to Prow team via the k8s/Prow slack channel if there are any questions.

/cc @kvmware @upodroid
@chizhg chizhg mentioned this issue Apr 11, 2022
Merged
@upodroid upodroid mentioned this issue Jun 2, 2022
Merged
@upodroid upodroid added kind/enhancement area/gcp Issues or PRs related to Google Cloud Infrastructure priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jun 7, 2022
@github-actions
Copy link

github-actions bot commented Sep 6, 2022

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 6, 2022
@github-actions github-actions bot closed this as completed Oct 7, 2022
@cardil
Copy link
Contributor

cardil commented Oct 7, 2022

/remove-lifecycle stale
/reopen
/triage accepted

@knative-prow knative-prow bot added the triage/accepted Issues which should be fixed (post-triage) label Oct 7, 2022
@knative-prow knative-prow bot reopened this Oct 7, 2022
@knative-prow
Copy link

knative-prow bot commented Oct 7, 2022

@cardil: Reopened this issue.

In response to this:

/remove-lifecycle stale
/reopen
/triage accepted

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/test-infra repository.

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@upodroid upodroid

Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure kind/enhancement priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Issues which should be fixed (post-triage)
Projects
Infra (Productivity)
Status: In Design/Discussion
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cardil @chizhg @upodroid