
* ensure you define [graphite] and [grafana] in your hosts file. * The grafana service is lightweight and can live on the same host as the graphite host. However, it can also be separated to run on its own server if desired. * Once the graphite-web services are deployed (which also sets up the carbon-cache service), and the grafana service is deployed, you will need to define the data source for your graphite host in the grafana instance. * The grafana service runs on port 3000, and has the default user/pass of admin/admin. * username / password for graphite is set in install/group_vars/all * firewalld is disabled on the grafana and graphite hosts If firewalls are needed, iptables-service is suggested but left us to deployment team. * Added gen_hostfile.sh updates for the needed hosts entries, with comments to the user on what needs to be in 'hosts' file. graphite db sets up Change-Id: I27660b6ecbf019699c124b02b4b4fd6185547a54
18 lines
493 B
Plaintext
18 lines
493 B
Plaintext
# Schema definitions for Whisper files. Entries are scanned in order,
|
|
# and first match wins. This file is scanned for changes every 60 seconds.
|
|
#
|
|
# [name]
|
|
# pattern = regex
|
|
# retentions = timePerPoint:timeToStore, timePerPoint:timeToStore, ...
|
|
#
|
|
# Carbon's internal metrics. This entry should match what is specified in
|
|
# CARBON_METRIC_PREFIX and CARBON_METRIC_INTERVAL settings
|
|
[carbon]
|
|
pattern = ^carbon\.
|
|
retentions = 60:90d
|
|
|
|
[default]
|
|
pattern = .*
|
|
retentions = 10s:7d,60s:90d,1h:180d
|
|
|