-
Notifications
You must be signed in to change notification settings - Fork 35
/
operations-monasca_agent.xml
97 lines (97 loc) · 3.42 KB
/
operations-monasca_agent.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
<?xml version="1.0"?>
<?xml-stylesheet href="urn:x-suse:xslt:profiling:docbook51-profile.xsl"
type="text/xml"
title="Profiling step"?>
<!DOCTYPE section [
<!ENTITY % entities SYSTEM "entity-decl.ent"> %entities;
]>
<section xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="monasca-agent">
<title>&o_monitor; Agent</title>
<para>
The &o_monitor; agent (monasca-agent) collects information about your cloud using
the installed plugins. The plugins are written in Python, and determine the
monitoring metrics for your system, as well as the interval for collection.
The default collection interval is 30 seconds, and we strongly recommend
not changing this default value.
</para>
<para>
The following two types of custom plugins can be added to your cloud.
</para>
<itemizedlist>
<listitem>
<para>
<emphasis role="bold">Detection Plugin</emphasis>. Determines whether the
monasca-agent has the ability to monitor the specified component or service
on a host. If successful, this type of plugin configures an associated
<emphasis role="bold">check plugin</emphasis> by creating a YAML
configuration file.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Check Plugin</emphasis>. Specifies the metrics to be
monitored, using the configuration file created by the detection plugin.
</para>
</listitem>
</itemizedlist>
<para>
monasca-agent is installed on every server in your cloud, and provides
plugins that monitor the following.
</para>
<itemizedlist>
<listitem>
<para>
System metrics relating to CPU, memory, disks, host availability, etc.
</para>
</listitem>
<listitem>
<para>
Process health metrics (process, http_check)
</para>
</listitem>
<listitem>
<para>
&product;-specific component metrics, such as apache
rabbitmq, kafka, cassandra, etc.
</para>
</listitem>
</itemizedlist>
<para>
&o_monitor; is pre-configured with default check plugins and associated detection
plugins. The default plugins can be reconfigured to monitor third-party
components, and often only require small adjustments to adapt them to this
purpose. Find a list of the default plugins here:
<link xlink:href="https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#detection-plugins"/>
</para>
<para>
Often, a single check plugin will be used to monitor multiple services. For
example, many services use the <literal>http_check.py</literal> detection
plugin to detect the up/down status of a service endpoint. Often the
<literal>process.py</literal> check plugin, which provides process monitoring
metrics, is used as a basis for a custom process detection plugin.
</para>
<para>
More information about the &o_monitor; agent can be found in the following
locations
</para>
<itemizedlist>
<listitem>
<para>
&o_monitor; agent overview:
<link xlink:href="https://github.com/openstack/monasca-agent/blob/master/docs/Agent.md"/>
</para>
</listitem>
<listitem>
<para>
Information on existing plugins:
<link xlink:href="https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md"/>
</para>
</listitem>
<listitem>
<para>
Information on plugin customizations:
<link xlink:href="https://github.com/openstack/monasca-agent/blob/master/docs/Customizations.md"/>
</para>
</listitem>
</itemizedlist>
</section>