Monitoring: различия между версиями
Sirmax (обсуждение | вклад) |
Sirmax (обсуждение | вклад) (→Heka) |
||
Строка 64: | Строка 64: | ||
* [http://wiki.sirmax.noname.com.ua/index.php/Heka_Debugging Heka debuging review] |
* [http://wiki.sirmax.noname.com.ua/index.php/Heka_Debugging Heka debuging review] |
||
* [http://wiki.sirmax.noname.com.ua/index.php/Heka_Filter_afd_example How to create your own Heka filter, Output and Nagios integration] |
* [http://wiki.sirmax.noname.com.ua/index.php/Heka_Filter_afd_example How to create your own Heka filter, Output and Nagios integration] |
||
+ | ==Nagios== |
||
+ | Passive checks overview: ToBeDone! |
Версия 17:31, 9 февраля 2016
Monitorimg
Any complicated system need to be monitored.
LMA (Logging Monitoring Alerting) Fuel Plugins provides complex logging, monitoring
and alerting system for Mirantis Openstack. LMA use open-source products and can be also integrated with currently existing monitoring systems.
In this manual will be described complex configuration include 4 plugins:
- ElasticSearch/Kibana – Log Search, Filtration and Analysis
- LMA Collector – LMA Toolchain Data Aggregation Client
- InfluxDB/Grafana – Time-Series Event Recording and Analysis
- LMA Nagios – Alerting for LMA Infrastructure
(more details about MOS fuel plugins: MOS Plugins overview
It is possible to use LMA-related plugins separately but the are designed to be used in complex. In this document all examples are from cloud where all 4 plugins are installed and configured.
LMA DataFlow
LMA is complex system and contains the follwing parts:
- Collectd - data collecting
- Heka - data collecting and aggregation
- InluxDB - non-SQL database for time-based data, in LMA it is is used for charts in Grafana
- [https://www.elastic.co/ ElasticSearch - non-SQL database, in LMA it is used to save logs.
- Grafana - Graph and dashboard builder
- Kibana - Analytics and visualization platform
- Nagios - Monitoring system
+--------------------------------+ Grafana dashboard Kibana Dashboard |Node N (compute or controller) | ------------------- ---------------------- | | ^ ^ |* collectd --->---+ | | | | | | +-<- Some data generated locally is looped to-<+ | | | | | | to be aggregated | | | |* hekad <---<---+ | | ^ | | | | | +-------------------------------------------+ | ^ | | +------------->To Aggregator|------>| Heka on aggregator (Controller with VIP) |---+------------+ | | | | | +-------------------------------------------+ | | | | | |to |to |to | | | | | |Influx |ElasticSearch |Nagios | | | +---------------------------|->-------->--- +-------->--|------->------|--->---------->---------->--------------[ InfuxDB ] ^ | | | | | | | | | | | | | +---------------------------|------------------------>--+------->------|--->---------->---------->--------------[ ElasticSearch ]-------------------------------+ | | | +--------------------------------+ | +----------------------------------------[ Nagios ]---> Alerts (e.g. email notifications)
Collectd
Collectd is collecting data, all details about collect are in separate document.
Heka
Heka is comolex tool so data flow in Heka is described in separate documents and divided on parts
- Heka in general
- Heka inputs details
- Heka Splitters
- Heka Decoders
- Heka debuging review
- How to create your own Heka filter, Output and Nagios integration
Nagios
Passive checks overview: ToBeDone!