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

OCPBUGS-34784: Collect aggregated Prometheus Alertmanager instances #941

Conversation

ncaak
Copy link
Contributor

@ncaak ncaak commented May 28, 2024

This PR implements a new data enhancement to the gatherers. It creates a new gatherer that collects instances of Prometheus and AlertManager deployments that are outside of the openshift-monitoring namespace.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • docs/insights-archive-sample/config/aggregated/custom_prometheuses_alertmanagers.json

Documentation

  • docs/gathered-data.md

Unit Tests

  • pkg/gatherers/clusterconfig/gather_aggregated_instances_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

  • No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-12758
https://issues.redhat.com/browse/OCPBUGS-34784

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 28, 2024
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 28, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 28, 2024

@ncaak: This pull request references CCXDEV-12758 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.17.0" version, but no target version was set.

In response to this:

This PR implements a new data enhancement to the gatherers. It creates a new gatherer that collects instances of Prometheus and AlertManager deployments that are outside of the openshift-monitoring namespace.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • docs/insights-archive-sample/config/aggregated/custom_prometheuses_alertmanagers.json

Documentation

  • docs/gathered-data.md

Unit Tests

  • pkg/gatherers/clusterconfig/gather_aggregated_instances_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

  • No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-12758

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.

Copy link

openshift-ci bot commented May 28, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

openshift-ci bot commented May 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncaak

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2024
@ncaak ncaak marked this pull request as ready for review May 28, 2024 15:09
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 28, 2024
@openshift-ci openshift-ci bot requested review from rhrmo and tremes May 28, 2024 15:15
docs/gathered-data.md Outdated Show resolved Hide resolved
docs/gathered-data.md Outdated Show resolved Hide resolved
@tremes
Copy link
Contributor

tremes commented May 30, 2024

Thank you!
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2024
@ncaak
Copy link
Contributor Author

ncaak commented May 30, 2024

/retest

Copy link

openshift-ci bot commented May 30, 2024

@ncaak: 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.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 3, 2024

@ncaak: This pull request references CCXDEV-12758 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.17.0" version, but no target version was set.

In response to this:

This PR implements a new data enhancement to the gatherers. It creates a new gatherer that collects instances of Prometheus and AlertManager deployments that are outside of the openshift-monitoring namespace.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • docs/insights-archive-sample/config/aggregated/custom_prometheuses_alertmanagers.json

Documentation

  • docs/gathered-data.md

Unit Tests

  • pkg/gatherers/clusterconfig/gather_aggregated_instances_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

  • No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-12758
https://issues.redhat.com/browse/OCPBUGS-34784

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.

@ncaak ncaak changed the title CCXDEV-12758: Collect aggregated Prometheus Alertmanager instances OCPBUGS-34784: Collect aggregated Prometheus Alertmanager instances Jun 3, 2024
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 3, 2024
@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-34784, which is invalid:

  • expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "4.16.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR implements a new data enhancement to the gatherers. It creates a new gatherer that collects instances of Prometheus and AlertManager deployments that are outside of the openshift-monitoring namespace.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • docs/insights-archive-sample/config/aggregated/custom_prometheuses_alertmanagers.json

Documentation

  • docs/gathered-data.md

Unit Tests

  • pkg/gatherers/clusterconfig/gather_aggregated_instances_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

  • No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-12758
https://issues.redhat.com/browse/OCPBUGS-34784

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.

@ncaak
Copy link
Contributor Author

ncaak commented Jun 3, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 3, 2024
@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-34784, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.0) matches configured target version for branch (4.17.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @JoaoFula

In response to this:

/jira refresh

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.

@openshift-ci openshift-ci bot requested a review from JoaoFula June 3, 2024 11:34
@openshift-merge-bot openshift-merge-bot bot merged commit 90d750b into openshift:master Jun 3, 2024
9 checks passed
@openshift-ci-robot
Copy link
Contributor

@ncaak: Jira Issue OCPBUGS-34784: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-34784 has been moved to the MODIFIED state.

In response to this:

This PR implements a new data enhancement to the gatherers. It creates a new gatherer that collects instances of Prometheus and AlertManager deployments that are outside of the openshift-monitoring namespace.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • docs/insights-archive-sample/config/aggregated/custom_prometheuses_alertmanagers.json

Documentation

  • docs/gathered-data.md

Unit Tests

  • pkg/gatherers/clusterconfig/gather_aggregated_instances_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

  • No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-12758
https://issues.redhat.com/browse/OCPBUGS-34784

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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-insights-operator-container-v4.17.0-202406031213.p0.g90d750b.assembly.stream.el9 for distgit ose-insights-operator.
All builds following this will include this PR.

@ncaak
Copy link
Contributor Author

ncaak commented Jun 7, 2024

/cherry-pick 4.16

@openshift-cherrypick-robot

@ncaak: cannot checkout 4.16: error checking out "4.16": exit status 1 error: pathspec '4.16' did not match any file(s) known to git

In response to this:

/cherry-pick 4.16

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.

@ncaak
Copy link
Contributor Author

ncaak commented Jun 7, 2024

/cherry-pick release-4.16

@openshift-cherrypick-robot

@ncaak: new pull request created: #948

In response to this:

/cherry-pick release-4.16

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.

@ncaak
Copy link
Contributor Author

ncaak commented Jun 20, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot

@ncaak: new pull request created: #950

In response to this:

/cherry-pick release-4.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants