User manual Problems

Problems

The problems page displays a filtered list of the system resources, wether they are problems or not. The problems page displays a list of resources grouped by level of criticity (business level).

On the top side of the page, it is possible to filter the list and to set bookmarks that may be global or user specifically stored.

Items

The items displayed in the problems list may be expanded to display more information and actions buttons. If the user is allowed to send commands on the Web UI, he will be able to act on the current element: acknowledge a problem, schedule a downtime, ...

The items can be selected to create a list of selected items on which the allowed user will be able to act in one operation.

Bookmarks

Bookmarks are a list of stored filters. When a user wants to store a filter to reuse later, he may bookmarks this filter and store it with a name. The bookmark may then be reused simply bu clicking on its name in the bookmarks list.

The user can make its bookmarks available for all the Shinken Wtb UI users, simply by making it global.

Filtering

To search for services and hosts (elements), use the following search qualifiers in any combination.

Search hosts or services

By default, searching for elements will return both hosts and services. However, you can use the type qualifier to restrict search results to hosts or services only.

• www type:host Matches hosts with "www" in their hostname.

Search by the state of an element

The is and isnot qualifiers finds elements by a certain state. For example:

• is:DOWN Matches hosts that are DOWN.
• isnot:0 Matches services and hosts that are not OK or UP (all the problems). Equivalent to isnot:OK isnot:UP
• load isnot:ok Matches services with the word "load", in states warning, critical, unknown or pending.
• is:ack Matches elements that are acknownledged.
• is:downtime Matches elements that are in a scheduled downtime.

Search by the business impact of an element

The bp qualifier finds elements by it's business priority. For example:

• bp:5 Matches hosts and services that are top for business.
• bp:>1 Matches hosts and services with a business impact greater than 1.

Search by duration

You can also search by the duration of the last state change. This is very useful to find elements that are warning or critical for a long time. For example:

• isnot:OK duration:>1w Matches hosts and services not OK for at least one week.
• isnot:OK duration:<1h Matches hosts and services not OK for less than one hour.

You can use the following time units: s(econds), m(inutes), h(ours), d(ays), w(eeks).

Of course, you can't use the "=" sign here. Finding something that is exactly matching would be a huge luck.

Search by host group, service group, host tag and service tag

Examples:

• hg:infra Matches hosts in the group "infra".
• sg:shinken Matches services in the group "shinken".
• htag:linux Matches hosts tagged "linux".
• stag:mysql Matches services tagged "mysql".

Obviously, you can't combine htag and stag qualifiers in a search and expect to get results.

Search by contact group and contact tag

Examples:

• cg:admins Matches hosts and services related to contacts in contact group "admins".
• ctag:client Matches hosts and services related to contacts tagged "client".

Find hosts and services by realm

The realm qualifier finds elements by a certain realm. For example:

• realm:aws Matches all AWS hosts and services.