-
Notifications
You must be signed in to change notification settings - Fork 98
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
Conditional gathering #433
Conditional gathering #433
Conversation
7520a4f
to
4705cba
Compare
@Sergey1011010: This pull request references Bugzilla bug 1966153, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
4705cba
to
3778b05
Compare
/retest |
} | ||
|
||
// GatherConditionalGathererRules stores the gathering rules in insights-operator/conditional-gatherer-rules.json | ||
func (g *Gatherer) GatherConditionalGathererRules(context.Context) ([]record.Record, []error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will go to our docs/gathered-data.md
as I just noticed :) Not sure we want it there....but probably not a big deal. WDYT @jholecek-rh pls? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want it there, imho.
I'm just worried about the terminology. Insights rule developers are part of the primary audience for docs/gathered-data.md
. They will have to pause to realize that it is not talking about Insights rules (like I did right now). I just cannot think of a better name...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good points @jholecek-rh. Thanks!
@Sergey1011010: PR needs rebase. 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. |
00ea498
to
e87db1d
Compare
@Sergey1011010: No Bugzilla bug is referenced in the title of this pull request. 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 kubernetes/test-infra repository. |
/retest Please review the full test history for this PR and help us cut down flakes. |
19 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Waiting for openshift/origin#26264 |
/unhold |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
This PR implements a new gatherer needed by CCXDEV-4431. Right now it collects logs and image streams of namespace "openshift-cluster-samples-operator" if alert "SamplesImagestreamImportFailing" is firing, but it designed in a way that it can be further extended to run X gatherer with Y params on Z condition.
Categories
Sample Archive
docs/insights-archive-sample/conditional/namespaces/openshift-cluster-samples-operator/imagestreams/example.json
docs/insights-archive-sample/conditional/namespaces/openshift-cluster-samples-operator/pods/cluster-samples-operator-8ffb9b45f-49mjr/containers/cluster-samples-operator-watch/logs/last-100-lines.log
docs/insights-archive-sample/conditional/namespaces/openshift-cluster-samples-operator/pods/cluster-samples-operator-8ffb9b45f-49mjr/containers/cluster-samples-operator/logs/last-100-lines.log
Documentation
path/to/documentation.md
Unit Tests
pkg/gatherers/conditional/conditional_gatherer_test.go
Privacy
Yes. The collected image streams are anonymized here https://github.com/openshift/insights-operator/pull/433/files#diff-3244b427f7e3f71fcf8c9788e7648b1ae57233dd685b1cb61807698c1bcddf75R70
Changelog
Breaking Changes
It's not a breaking change, but some code can potentially misfunction because the new format for function names in metadata was added, for example
conditional/image_stream_definitions_of_namespace/namespace=openshift-cluster-samples-operator
where the last part is the gatherer parametersReferences
https://issues.redhat.com/browse/CCXDEV-4431
https://bugzilla.redhat.com/show_bug.cgi?id=???
https://access.redhat.com/solutions/???