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. These charts are being rendered 1:1 with the list of metrics (over 500).
52
-
These metrics are scraped and generated by Prometheus, and should be sent to a Grafana instance
53
-
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.
52
+
These metrics are scraped and generated by Prometheus, and should be sent to a Grafana instance to be displayed with
53
+
a Grafana dashboard, but we didn't realize this was happening until we were too close to launch to fix it.
54
54
It would be wonderful if a future iteration could manipulate the prometheus configuration in the kubernetes example to send its data
55
55
to an instance of Grafana, and integrate Grafana's dashboard into Chronos to visualize the data.
healthData - Pull in all the health data via HealthContext
25
-
selectedMetrics - Pull in the list of ALL user-selected metrics via QueryContext as strings, even if they don't pertain to this category.
26
-
category - Destructure category from props. This category was passed down from the GraphsContainer and creates a new tab in Chronos to view charts pertaining only to the category.
27
-
Think of each <HealthContainer /> as the new tab in Chronos. It will only create charts pertaining to that category.
28
-
healthChartsArr - local state that gets updated with an array of <HealthChart />'s that display user-selected data.
29
-
`service` - only used to determine if we should display our health charts (because kafka and kubernetes specifically don't use HealthChart to display data).
0 commit comments