Graphite configuration parameters

To configure the service, use the following configuration parameters in ADCM.

NOTE

To apply a changed parameter in ADCM, perform one of the following actions:

  • Restart the Graphite service using the Restart service action. Additionally, restart the Grafana service (this is necessary since Grafana uses Graphite).

  • Reinstall the ADET cluster using the Reinstall cluster action.

Paths
Parameter Description Default value

Data storage

A path to the directory for storing metrics

/opt/monitoring

Configuration directory

A path to the directory that contains Graphite configuration files

/etc/graphite

Logs directory

A path to the directory for storing Graphite service logs

/var/log/graphite

ip_and_ports
Parameter Description Default value

Host IP address

IP address where the metrics receiver is available. Filled automatically after the installation is completed or can be set manually

 — 

Web-interface TCP port

TCP port on which the Graphite web interface is available

80

Metrics receiver TCP port

TCP port used by the metrics receiver to accept data in Carbon plaintext protocol format. For details, see Graphite documentation

2015

Metrics receiver UDP port

UDP port used by the metrics receiver to accept data in Carbon plaintext protocol format. For details, see Graphite documentation

2016

Other
Parameter Description Default value

Carbon services command-line options

Additional command-line arguments for all Carbon services (e.g. --debug for debug logging)

 — 

Storage schema
Parameter Description Default value

Carbon retentions

Retention schema configuration for storing metrics in the Carbon cache, defined as <precision>:<retention_period>, where

  • <precision> is the time interval between individual datapoints;

  • <retention_period> is the total duration for keeping data.

For example, 60:90d value saves 1 datapoint every 60 seconds and keeps data for 90 days

60:90d

Default graphite retentions

The rules that control how long Graphite keeps data and how data granularity decreases over time.

The value is a comma-separated list of retention stages, ordered from the newest to the oldest. When data moves to an older stage, Graphite automatically merges multiple high-granularity datapoints into an individual lower-granularity datapoint.

Each stage uses the <precision>:<retention_period> format, where

  • <precision> is the time interval between individual datapoints;

  • <retention_period> is the total duration for keeping data.

Possible time units: s (seconds), m (minutes), h (hours), d (days), w (weeks), or y (years).

For example, 60s:90d,10m:2y value keeps high-granularity data (one datapoint every 60 seconds) for 90 days. After 90 days, the service aggregates these datapoints into one historical datapoint every 10 minutes and stores them for 2 years

60s:90d,10m:2y

Found a mistake? Seleсt text and press Ctrl+Enter to report it