You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chronos11 -- Unfortunately, eventData is not in a good place for UI/UX purposes.
28
-
The eventData object has a key of 'Event' and a value of an object with hundreds of keys as metric names
29
-
with their associated values and timestamps due to the way kubernetes metrics are being tracked/logged in the database.
24
+
Chronos11 -- Unfortunately, eventData is not in a good place for UI/UX purposes. These charts are being rendered 1:1 with the list of metrics (over 500).
30
25
These metrics are scraped and generated by Prometheus, and should be sent to a Grafana instance
31
-
to be displayed with a Grafana dashboard, but we didn't realize this until we were too close to launch to fix it.
32
-
For now, the 'selectedMetrics' array is still an array with one object on it with a key of 'event', and a value of an array with
33
-
the hundreds of metric names as strings inside. The eventData is an object with the key of event, and a value of an object with
34
-
the hundreds of metrics as keys, and their values as the metrics and timestamps.
26
+
to be displayed with a Grafana dashboard, but we didn't realize this was happening until we were too close to launch to fix it.
35
27
It would be wonderful if a future iteration could manipulate the prometheus configuration in the kubernetes example to send its data
36
28
to an instance of Grafana, and integrate Grafana's dashboard into Chronos to visualize the data.
0 commit comments