This better reflects its purpose as otherwise it would imply
that you need Elastic Stack for it. Graylog also reads from
Elasticsearch instances, this could serve as additional integration
here.
Main focus: Object attributes and their value types. Originates from the
API Event Streams patch to document their value types. Now applied to
the entire configuration objects chapter.
The API chapter and their value types has been changed to capitalized
type identifiers.
Value types are now explicitly told about inside monitoring basics. This
has been adopted into the Icinga 2 training material a long time ago
and finds its way into the docs too.
The CheckResult and PerfdataValue value types have been moved into the
advanced topics chapter. mkdocs doesn't like multiple `#` headings in one file
and did just hide it.
Also moved the Influxdb details into the features documentation where it
belongs.
Many small references and URLs to other chapters added.
E.g. dedicated chapters for object accessor examples, to better link against
time dependent thresholds.
Can serve as patch basis and reference for ITL documentation where the
value types are missing too.
This commit also fixes the non-requirement of "legacy-timeperiod" which
also is a default template import since 2.6.
This also fixes the state mapping issue.
fixes#4015
This makes it easier for cluster and client setups with or
without the Icinga Director.
Note: Clients will still not receive synced configuration if
accept_config is not enabled (which is the default, and can be changed
during setup).
fixes#5106
Replace the previous notification scheme - now using getops in place of ENV
variables, giving the ability to integrate with the Icinga Director.
refs #5170
Signed-off-by: Michael Friedrich <michael.friedrich@icinga.com>
This helps a lot when configuring client checks as command endpoint
where the check command definitions are both used on the master
and the client.
fixes#10722
Adds an Icinga2 object to directly interface with InfluxDB's native HTTP API.
This supports optional basic authorization, and TLS transport. InfluxDB didn't
appear to like having the TLS stream kept open, so instead this object buffers
data points which are then flushed to InfluxDB as a batch write, either driven
by a configurable timeout or threshold.
As InfluxDB is a schema-less database the host and service templates are user
configurable allowing both the measurement field and tags to be set by the
end user via macro expansion. This allows access to tag fields from arbitrary
data associated with host.vars or service.vars. If a particular value is
unable to be resolved, the tag will be dropped and not transmitted to InfluxDB.
Also alters URL handling to omit array brackets when only a single value is
attached to a key, otherwise InfluxDB has a strop with non-standard syntax.
fixes#10480
Signed-off-by: Michael Friedrich <michael.friedrich@netways.de>
Markus Frosch
Michael Insel
Max Rosin
Jean Flach
Dirk Goetz
Gunnar Beutner
Michael Friedrich
Michael
Christian Gut
pv2b
Marianne Spiller
Kai Goller
Gunnar Beutner
Michael Friedrich
Simon Murray
Daniil Yaroslavtsev
Gunnar Beutner