Change-Id: I5a8ccb235d36c1b4115794904f373a5704c2296d

Change-Id: I646a852be587598ff0866e5941d954a6ac1fdd08

Change-Id: I4fb69e8defa44a9d92a9fb7c23a6280fffc1a3e9

Change-Id: I6b6fbaaebd3e349bf76aa05cb9eb2004a842d9c5

Change-Id: I22e7e4713e20f6a0f79c5ab4b3066f1f0129feb0

Change-Id: Icbbd64144e6619eaa56e02c6c9362c7bcad9dd96

Change-Id: Ifa2787d76cf18e29f54583046349c071c5e9a25e

Change-Id: I64a93135daebe7d55430adc51de2c9186c7a5ad7

Change-Id: I715f78983c69084c81d4efd4a5625d5dfe0f276f

Change-Id: I87d132ce6473715b0992e561b2855456f24bcb3b

Raise severity from warning to critical

Partial-Bug: PROD-15203
Change-Id: I32f19b5520bc200d61280da57f4ab5842b060454

Change-Id: I67531b6ad15a2e96ee05178f17aae2504b3362bf

Change-Id: I59297736406469e5314236cb40851d9a6f94386e

Change-Id: I94f09359f976ccd0f207277da52d20e659b36a69

The other disk alerts use predict_linear() to trigger before a disk gets
full but they don't trigger when the disk is effectively (or nearly)
full.

Change-Id: I8e6794d35bf96378ca3e3d527db4315d2b3a868d

Change-Id: I574c6e1a31f71502eb279cdc3c5768ee483d73fa

Change-Id: I8f2a66c6edafc425794d7cedc8b9217df7ee5951

Pillar values:
linux.monitoring.bond_status.interfaces = [ 'bond0', 'all', 'etc' ]

Leave bond_status.interfaces undefined to disable (default).

Depends-On: Ia07d4c473bf64d98170f51599caaedb46645ede3

Change-Id: I62a7d59251d37cb6c7fc7b761f63a5599930f1dc

This is typically used to mount Docker containers but it generates too
many volatile metrics which aren't useful.

Change-Id: I00117895570515b2c8f9690542e83061309464c3

Change-Id: I1c8e752de9ad3479da830706ae736df6846b977f

Change-Id: Ia7df4918732ce8fcf28b1d6eed629073146a567c

Change-Id: I456ed02ad54a9b55486b4c4a61c9cebfb8f28613

Change-Id: Ie3f9da382c23148836e4a20ff0f37c3929e062cf

Since metrics on dropped packets are counters, the alerts should use
the rate() function. This change also fixes some inconsistencies in the
alert descriptions.

Change-Id: I9abbc0a49f45ba760836c436a3e7e65aa62f652e

Change-Id: I1cc00b41a6a1774d1401a9f71ab4c6364c65d139

Change-Id: Idc73c152a0e71d5ac2a8c10f46c955755d8e77ae

This change adds the Telegraf configuration to collect swap metrics, the
associated Prometheus alarms and graphs to the Grafana dashboard.

Change-Id: I3595fd0b8cab06215c620642da69dd29c398396a

The `linux_netlink.ls` function used a regex to choose which interfaces
to collect metric for.

`_alphanum_re = re.compile(r'^[a-z0-9]+$')`

Unfortunately, by default this excludes vlan and tap interfaces, which
are kind of important.  ie `bond0.120` or `tap2a3dab86-fb`.

We also have a problem where even if we update the regex to include
these interfaces... if someone deletes and spawns a new instance then
the tap device name changes on the compute host, which will not be
monitored unless someone re-runs the `collectd` on the compute again.
Less than ideal.

This commit lets us choose `VerboseInterface "all"` using Pillar data
to avoid this problem.

Change-Id: If50f18367b22338b3fba1ff15902d557a0bdf2ea

Change-Id: I54e02e0741d53ec7b2335145dc968b7b8c8f5e00

Change-Id: If0ee6f1ac5ab697559fcd853225e1520de2e8c1c

Change-Id: Icacb0ca22a34f1ff438a895700040563d250bac9

Change-Id: I008818853c2058746be08365283b949177efa254
Depends-On: I3c3c569a013aff8c3ab8e46cffb93a60d74ddf09

Change-Id: I80193afad1842f67967d1bab164f049078e3cd75

will always be defined since the default is an empty dict)

Change-Id: Id4b0b405872457bd8b20f450e4031d6808d3cf59

Change-Id: I25fb0eb0d4b922b8853eceb0c1c220a4040e1704

Change-Id: I1765fc6aa4a8c3da25330f19bb043ddbf548b9ad

Change-Id: I66576b4ed40ef160c5f13747a908f018f252b6b4

Change-Id: I03bed44bafdebbcd22f487e59ef0de45dfbf3463

Change-Id: Ic3a1e77f2d38c5d916dd3c07211a6ea160559e6f

Change-Id: Ic39fa0f18e0d9aeca0ef73ae6d985d12d15a1c3a

This reverts commit a63f4053f3.

The support for collecting syslog is going to be moved to the rsyslog
formula.

This commit adds more built-in alarms to the Linux formula.