TRT-2333: create an endpoint for a component-monitor report #15
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@smg247: This pull request references TRT-2333 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 story 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smg247 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 |
openshift-ci
bot
added
the
approved
|
/hold this will require a config change to merge around the same time |
openshift-ci
bot
added
the
do-not-merge/hold
…g and extensibility
smg247
force-pushed
the
component-monitor-report-endpoint
branch
from
5f16ef9 to
59550ef
Compare
|
/lgtm |
|
@neisw: changing LGTM is restricted to collaborators 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-sigs/prow repository. |
I'll get a ticket with DPP going to get everyone else added. Going to manually merge this one for now. |
3 participants
This allows the, forthcoming,
component-monitorto send a report to thedashboardapi. The dashboard will handle creating and resolving outages based on that report. Thecomponent-monitorwill not need to know anything about the status of outages, only what the current status of the components it is monitoring is.