Re: [icinga-users] Metric graphing with Icinga 2
I have just now implemented graphite/grafana at our installation. The graphs look great. One question, though. After running for a little while to get the feel of it, we turned on another metric, specifically, we are now logging switch traffic with check_mrtgtraf. But, the performance metrics aren't making it into graphite. We turned on debuglog (icinga2 feature enable debuglog) and can see the perf data being properly returned, but it just ain't making it into graphite. Poking around in graphite's web app, nothing. Not there. Grafana can't see it, so we can't graph it. Any idea what I might need to do to get this going? I've restarted everything, done "graphite-manage syncdb", etc. What am I missing? Thanks, Michael On 08/10/2016 01:20 PM, Joseph L. Casale wrote: You should look into grafana as graphite frontend. Or when graphite doesn't scale anymore grafana and prometheus. Grafana certainly looks impressive and polished. I imagine Prometheus overlaps with Icinga a bit. What are peoples thoughts on influxdb? Thanks, jlc ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
Re: [icinga-users] Using check_multi with Icinga2
Coming back to this after taking a while working on other stuff.
I'm running into an issue. The issue is that get_host().state is
returning "1" for every host, including those that are UP. See below
for the config I am working with. Just for testing I am using my
"vagrant-minion" box which is running Icinga2. It's UP and has been UP
for a long time, but vars.cluster_data contains "1".
It seems the get_host() is not returning the correct host state. Any thoughts?
object CheckCommand "check_cluster" {
import "plugin-check-command"
command = [
PluginDir + "/check_cluster",
"-h", "",
"-l", "$cluster_label$",
"-w", "$cluster_warning$",
"-c", "$cluster_critical$",
"-d", "$cluster_data$",
]
vars.cluster_warning = "0"
vars.cluster_critical = "1"
}
apply Service "clusterX" {
import "generic-service"
check_command = "check_cluster"
vars.cluster_label = get_host("vagrant-minion").state
vars.cluster_data = get_host("vagrant-minion").state
assign where host.name == "x ['us-east-1a', 'us-east-1d', 'us-east-1e']"
}
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
Re: [icinga-users] Metric graphing with Icinga 2
Hi, > On 12 Aug 2016, at 00:56, Michael Martin wrote: > > I have just now implemented graphite/grafana at our installation. The graphs > look great. > > One question, though. After running for a little while to get the feel of it, > we turned on another metric, specifically, we are now logging switch traffic > with check_mrtgtraf. But, the performance metrics aren't making it into > graphite. We turned on debuglog (icinga2 feature enable debuglog) and can see > the perf data being properly returned, but it just ain't making it into > graphite. Poking around in graphite's web app, nothing. Not there. Grafana > can't see it, so we can't graph it. > > Any idea what I might need to do to get this going? I've restarted > everything, done "graphite-manage syncdb", etc. What am I missing? * Check the debug log for “GraphiteWriter” sending the metrics * Verify that carbon-cache actually processes the data. By default the metrics/minute are set to a pretty low default value (max_updates_per_second, max_creates_per_minute, see my tuning over at the vagrant boxes - https://github.com/Icinga/icinga-vagrant/commit/6a6c53552c74040479331566dd683e3782ec8966) Kind regards, Michael > > Thanks, > > Michael > > > > On 08/10/2016 01:20 PM, Joseph L. Casale wrote: >>> You should look into grafana as graphite frontend. Or when graphite doesn't >>> scale anymore grafana and prometheus. >> Grafana certainly looks impressive and polished. I imagine Prometheus >> overlaps >> with Icinga a bit. >> >> What are peoples thoughts on influxdb? >> >> Thanks, >> jlc >> ___ >> icinga-users mailing list >> icinga-users@lists.icinga.org >> https://lists.icinga.org/mailman/listinfo/icinga-users > > ___ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** OSBConf 2016 - September - osbconf.org ** ** OSMC 2016 - November - netways.de/osmc ** ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
Re: [icinga-users] Using check_multi with Icinga2
Hi,
> On 12 Aug 2016, at 02:32, Michael Martinez wrote:
>
> Coming back to this after taking a while working on other stuff.
>
> I'm running into an issue. The issue is that get_host().state is
> returning "1" for every host, including those that are UP. See below
> for the config I am working with. Just for testing I am using my
> "vagrant-minion" box which is running Icinga2. It's UP and has been UP
> for a long time, but vars.cluster_data contains "1".
>
> It seems the get_host() is not returning the correct host state. Any thoughts?
>
>
> object CheckCommand "check_cluster" {
> import "plugin-check-command"
> command = [
> PluginDir + "/check_cluster",
> "-h", "",
> "-l", "$cluster_label$",
> "-w", "$cluster_warning$",
> "-c", "$cluster_critical$",
> "-d", "$cluster_data$",
> ]
> vars.cluster_warning = "0"
> vars.cluster_critical = "1"
> }
>
> apply Service "clusterX" {
> import "generic-service"
> check_command = "check_cluster"
>
> vars.cluster_label = get_host("vagrant-minion").state
> vars.cluster_data = get_host("vagrant-minion").state
That as such won’t work since the custom attributes values are computed at
config compile time. You are looking for runtime calculated values - which is
why you need to turn the custom attribute values into a function.
Something like that:
vars.cluster_label = {{ get_host("vagrant-minion").state }}
vars.cluster_data = {{ get_host("vagrant-minion").state }}
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc#!/icinga2/latest/doc/module/icinga2/chapter/monitoring-basics#custom-attributes-functions
Kind regards,
Michael
>
> assign where host.name == "x ['us-east-1a', 'us-east-1d', 'us-east-1e']"
> }
> ___
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
--
Michael Friedrich, DI (FH)
Senior Developer
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | michael.friedr...@netways.de
** OSBConf 2016 - September - osbconf.org **
** OSMC 2016 - November - netways.de/osmc **
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
