Reduce deployed MAX_UPDATES_PER_SECOND from 2000 to 500. Deploy grafana with anonymous read access by default.
Change-Id: I63859382065254786e1edba2bdb30e3e0d9770ee
This commit is contained in:
parent
121525e4e6
commit
54705f0a36
@ -22,9 +22,16 @@
|
||||
- name: Set grafana server port
|
||||
ini_file:
|
||||
dest=/etc/grafana/grafana.ini
|
||||
section=server
|
||||
option=http_port
|
||||
value={{grafana_port}}
|
||||
section={{item.section}}
|
||||
option={{item.option}}
|
||||
value={{item.value}}
|
||||
with_items:
|
||||
- section: server
|
||||
option: http_port
|
||||
value: "{{grafana_port}}"
|
||||
- section: auth.anonymous
|
||||
option: enabled
|
||||
value: true
|
||||
become: true
|
||||
|
||||
# disable firewalld (might need to create specific firewall rules or leave it to admin to do via iptables)
|
||||
|
@ -60,12 +60,12 @@ MAX_CACHE_SIZE = inf
|
||||
# prevent over-utilizing the disk and thus starving the rest of the system.
|
||||
# When the rate of required updates exceeds this, then carbon's caching will
|
||||
# take effect and increase the overall throughput accordingly.
|
||||
MAX_UPDATES_PER_SECOND = 2000
|
||||
MAX_UPDATES_PER_SECOND = 500
|
||||
|
||||
# If defined, this changes the MAX_UPDATES_PER_SECOND in Carbon when a
|
||||
# stop/shutdown is initiated. This helps when MAX_UPDATES_PER_SECOND is
|
||||
# relatively low and carbon has cached a lot of updates; it enables the carbon
|
||||
# daemon to shutdown more quickly.
|
||||
# daemon to shutdown more quickly.
|
||||
# MAX_UPDATES_PER_SECOND_ON_SHUTDOWN = 1000
|
||||
|
||||
# Softly limits the number of whisper files that get created each minute.
|
||||
@ -316,7 +316,7 @@ FORWARD_ALL = True
|
||||
# use multiple carbon-cache instances then it would look like this:
|
||||
#
|
||||
# DESTINATIONS = 127.0.0.1:2004:a, 127.0.0.1:2104:b
|
||||
#
|
||||
#
|
||||
# The format is comma-delimited IP:PORT:INSTANCE where the :INSTANCE part is
|
||||
# optional and refers to the "None" instance if omitted.
|
||||
#
|
||||
|
Loading…
x
Reference in New Issue
Block a user