Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Date

Attendees

Goals

  • By the end of this meeting we need a decision on how to expose required metrics without causing out of memory errors.

Discussion items

ItemNotes
Resources

These are worth pushing into Grafana

heap-memory
heap-used: a gauge tracking the amount of heap memory currently being used in bytes.
heap-max: a gauge tracking the maximum amount of heap memory that can be used in bytes.
heap-committed: a gauge tracking the amount of memory that is committed for the JVM to use in bytes.
non-heap-memory
non-heap-used: a gauge tracking the amount of non-heap memory currently being used in bytes.
non-heap-max: a gauge tracking the maximum amount of non-heap memory that can be used in bytes.
non-heap-committed: a gauge tracking the amount of non-heap memory that is committed for the JVM to use in bytes.
garbage-collection-count: a gauge tracking the number of garbage collections that have ocurred.
garbage-collection-time: a gauge tracking the time spent in garbage collections, measured in milliseconds.
Potential problem with the amount of data in metrics
  • Reference issues

key summary type created updated due assignee reporter priority status resolution
Refresh


  • Concern about out of memory errors
Questions
  • Is node providing metrics (ex running calculations) or just emitting raw data via the metrics port?
Idea: HdrHistogram
  • From Artur via discord "re metrics memory usage: I'm not sure what exactly causes that, but if it's histograms size, using a better reservoir for the metrics, especially one based on HdrHistogram (http://hdrhistogram.github.io/HdrHistogram/), could help"


Action items

  •  
  •  


  • No labels