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
Currently we don't have a monitoring dashboard of a single Viction node. This dashboard will not only help monitoring metrics, resource spikes and alerts on the fly but also help evaluating our performance updates and bug fixes, to judge if the updates actually brings a performance change or resolves resource leaking overtime, etc.
The first step of implementing a monitoring dashboard like this is put metrics gauges/meters/counters in code where we want to measure. After that, we need to fetch those metrics and index those in a timeseries database like Prometheus or InfluxDB, as data sources for a visualize platform like Grafana.
Currently we don't have a monitoring dashboard of a single Viction node. This dashboard will not only help monitoring metrics, resource spikes and alerts on the fly but also help evaluating our performance updates and bug fixes, to judge if the updates actually brings a performance change or resolves resource leaking overtime, etc.
The first step of implementing a monitoring dashboard like this is put metrics gauges/meters/counters in code where we want to measure. After that, we need to fetch those metrics and index those in a timeseries database like Prometheus or InfluxDB, as data sources for a visualize platform like Grafana.
Checklist:
The text was updated successfully, but these errors were encountered: