Skip to content

Commit

Permalink
"meta" metrics: gmetad status --> gmond --> gmetad
Browse files Browse the repository at this point in the history
gmond module for collecting stats from the new gmetad status call and
sending them back through the system.  This allows the existing
rrdtool & gweb infrastructure to graph them, but has obvious downsides
for monitoring when something goes wrong.  See
https://github.com/OHamm/monitor-core/wiki/Gmetad-Internal-Metrics-(developers)
for metrics descriptions
  • Loading branch information
cburroughs committed Mar 2, 2015
1 parent 9f740e8 commit 05b4fcc
Show file tree
Hide file tree
Showing 2 changed files with 509 additions and 0 deletions.
46 changes: 46 additions & 0 deletions gmetad_meta_status/conf.d/gmetad_meta_status.pyconf
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
modules {
module {
name = "gmetad_meta_status"
language = "python"

# Which gmetad instance to monitor
param gmetad_host {
value = "localhost"
}

# The gmetad interactive port
param gmetad_port {
value = 8652
}

# Which metrics to report. choices=['basic-only', 'raw', 'rate',
# 'all'] 'basic' metrics are included in all 'raw' and 'rate'.
param metrics {
value = "all"
}

# This module calculates all metrics (including derived) rates at
# once and then serves them out of a cache. This determines the
# minimum TTL.
param check_every {
value = 30
}
# Where to log information from this module (syslog facility)
param syslog_facility {
value = "user"
}
# log level, WARNING is not expected to produce any output
param log_level {
value = "WARNING"
}
}
}

collection_group {
collect_every = 30
time_threshold = 60

metric {
name_match = "gmetad_meta_status_(.+)"
}
}
Loading

0 comments on commit 05b4fcc

Please sign in to comment.