-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
+
This is the issue for System folks.
Define and implementation of:
- Grafana dashboards
- Prometheus rules
Datasources:
- System components exposing metrics. Seems that for now, only system-sidekiq component exports metrics.
- kube-state-metrics (https://issues.redhat.com/browse/THREESCALE-4679)
- aggregated health endpoints metrics. (https://issues.redhat.com/browse/THREESCALE-4681)
System guys have the domain knowledge to define useful dashboards and effective prometheus rules. Ops teams can help you with the syntax.
Setup your development environment with latest monitoring tools enabled: https://docs.google.com/document/d/1ogntOEYyi39E2SPp9DiHl-og4p_Ti3PPiEb4tCkZzv8/edit#
System team internal tracking doc: https://docs.google.com/document/d/1aLI2VoK0kPds4YsuPPCeXmhmvxo99_XKAVCCm5ruucs/edit?usp=sharing
THREESCALE-6168 and THREESCALE-5698 are also sub-tasks of this issue but they are moved out in order to be targeted to 2.11
- blocks
-
THREESCALE-4640 System grafana dashboard(s) and Prometheus rule definition
- Closed
- is related to
-
THREESCALE-6168 Hide client_id and client_secret
- Closed
-
THREESCALE-6446 3scale monitoring grafana/prometheus issues
- Closed
-
THREESCALE-6508 3scale monitoring grafana/prometheus issue - swapped descriptions
- Closed
-
THREESCALE-5698 Implement ActiveRecord level monitoring
- Closed
- relates to
-
THREESCALE-2509 Review with System team whether changes related to Yabeda impact templates/operator
- Closed