Skip to content

Latest commit

 

History

History
74 lines (44 loc) · 2.31 KB

10-User-Guide.md

File metadata and controls

74 lines (44 loc) · 2.31 KB

User Guide

This guide describes the basic usage of the module and how to access its data quickly.

To understand the status behavior, see the chapter about behavior.

Creating views

Views can be created in the TLV overview with the "Add" button, or directly in the module's configuration directory.

Example: /etc/icingaweb2/modules/toplevelview/views/example.yml

The module ships a very basic configuration editor, which allows to to edit the bare YAML configuration within the web interface.

After a view is created it will show up in the TLV overview.

Finding problems

Unhandled problems can be identified based on color saturation of the tiles.

In addition counters show you how many states of what kind lay below.

Unhandled colors

Handled colors

Drilling down

When you click on tiles in the topmost tile view, you drill down into a tree view of that tile.

The tree view is collapsing everything that is in an OK state. So you see the problems first.

Everything can be expanded via the arrow handle or a click on the title area.

Deeper branches can be opened in a new view by clicking on the title text, but this is only needed to filter the shown data.

Every Icinga status object, a host, service or host group is a single tile here.

Counters are meant to give you an indication about how many problems, or even objects are there.

Viewing Icinga details

By clicking on an Icinga tile you get dropped into the object's details,

Clicking on a service tile will bring you service detail view, same goes for hosts.

The host group tile gives 2 options, default will take you to a service overview for that host group, sorted by problems.

While clicking on the X hosts link in the tile brings you an overview over hosts in that group.

Using the TLV Cache

Please be aware that the data displayed in the Top Level View is cached for 60 seconds by default. This can be adjusted using the URL parameter cache. For example: toplevelview/show/tree?name=example-view&cache=30

Latest state changes will only be reflected after that caching time.