-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
No
-
---
-
---
-
-
-
MK - Sprint 228
WHAT
We want to figure out what capabilities the RHOBS Observability Operator has and if it could potentially superseed ours.
Repo: https://github.com/rhobs/observability-operator
WHY
It doesn't make sense to have two Operators doing the same thing. The RHOBS Observability Operator is also now installed on every OSD cluster, see SD ADR 0053 - Addons Monitoring.
HOW
Figure out if the RHOBS OO can fulfill all our requirements including the handling of logging.
DONE
- Any results of investigations done as part of this task is documented here: Addon Monitoring with Managed Application Services
Guidelines
The following steps should be adhered to:
- Required tests should be put in place - unit, integration, manual test cases (if necessary)
- CI and all relevant tests passing
- Changes have been verified by one additional reviewer against:
- each required environment
- each supported upgrade path
- If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged
- relates to
-
-
- Closed
-
1.
|
Investigate federation support |
|
New | 
|
Unassigned |
2.
|
Investigate configuration of monitoring stack using the addon config |
|
New |
|
Unassigned |
3.
|
Investigate if multiple services can share a single monitoring stack |
|
New |
|
Unassigned |
4.
|
Investigate use of RHOBS OO with the Observatorium proxy |
|
New |
|
Unassigned |