Download MonAMI v0.9 User Guide

Transcript
Introduction
Plot
18
18
Dataset 1
17
Dataset 2
16
15
14
14
Plot
18
12
18
11
Dataset 1
17
11
Dataset 2
16
10
9
15
9
14
14
8
13
6
5
4
4
12
12
6
7
12
6
11
11
10
9
2
2
0
0
Ice Cream Cones
Ice Cream Cones
13
12
12
8
2
4
6
8
9
2
7
5
10
6
0
6
12
14
16
18
Time
4
4
2
2
0
0
6
2
0
2
4
6
8
10
12
14
16
18
Time
Figure 1.2. Illustration of the three data flows
Internally-triggered monitoring is perhaps the most common. An example of internally-triggered monitoring is periodically asking for (and recording somewhere) the current status of some service. We
might ask an Apache web-server the current activity of its threads; we might ask a MySQL database
how many times its query-cache has been useful. These questions can be asked at any time. Typically
the values are queried at regular intervals and the results are plotted on a graph.
With on-demand monitoring, some external agent asks for data. An example of on-demand monitoring
would be a web-page that returned the current status of a database: the information could be gathered
only when queried by a user. The external agent can request information at any time, although in practice, requests are often periodic. A major benefit of on-demand monitoring flows is that it allows the
monitoring requirements to vary dynamically as greater or lesser volume of information is requested.
A potential problem with on-demand monitoring is with requests overloading the monitoring system.
MonAMI provides some protection against this by allowing the enforcement of a caching policy (see
Section 3.3.2, “The cache attribute”).
The third monitoring flow is event-based monitoring. Events are triggered by the monitoring target
(e.g., the Apache server). The target (such as an Apache server) sends information voluntarily at an
unpredictable time, usually due to something happening externally. Event monitoring flow is most
often used to record that “something” has happened; for example that a web download has completed.
A plugin that supports event-based monitoring flow makes the events available in different channels.
One can subscribe to one or more channels. Information from that channel is then sent to one or
more reporting targets. For example, the Apache web-server monitoring plugin (see Section 3.4.2,
“Apache”) can produce an event for each attempted HTTP transfer (whether successful or not) as
the access channel, so subscribing to the apache target's access channel would provide information on all transfers. A subscription can be more more specific: the channel access.4xx
provides information on only those transfers resulting in an error status-code, and subscribing to
access.4xx.404 will report on only missing page (status-code 404) events.
Explicit examples of each of the three event flows are given in Section 3.8, “Example configurations”.
Although the examples rely on an understanding of the monami.conf format (which Chapter 3,
Configuring MonAMI documents in detail), the examples (along with the accompanying notes) should
be fairly obvious.
1.3. Datatrees
When monitoring something (a service, for example) it is rare that the current status is described by
a single metric. Although you might only want a tiny subset of the available information, the current
3