Результаты поиска

Analysis LMA Collector – LMA Toolchain Data Aggregation Client InfluxDB/Grafana – Time-Series Event Recording and Analysis LMA Nagios – Alerting for LMA Infrastructure

Splitters details There are only one custom splitter: [openstack_splitter] type = "RegexSplitter" delimiter = '(<[0-9]+>)' delimiter_eol = false All strings

toml file. LMA plugin configures openstack services to use 'lma_notifications' as notification_topics, e.g : # cat /etc/nova/nova.conf | grep lma notific

internal format. [test_decoder] type = "SandboxDecoder" filename = "/usr/share/lma_collector/decoders/test_decoder.lua" Decoder code is not so complex: <syntaxhighlight

aggregator, e.g: message_matcher = "Fields[aggregator] All LMA heka config files are located in /etc/lma_collector folder. e.g. on controller there are follwing

Вводная: есть cmd.cgi который пишет данные в файл для того что бы в нагиос можно было отдавть результаты пассивных проверок.CGI медленный надо сделать

Clone Set: clone_lma_collector [lma_collector] Started: [ node-6.domain.tld ] Stop lma_ollector resource: #crm(live)resource# stop lma_collector crm(live)resource#

/augeas/load/NagiosObjects/incl "/etc/nagios3/conf.d/lma_contacts.cfg" augtool> set /files/etc/nagios3/conf.d/lma_contacts.cfg/contact/service_notification_commands

influxdb.InfluxDBClient("<elastic search server's IP addrtess>", "8086", "lma_user", "lma_password") client.get_list_database() Out[41]: [{u'name': u'_internal'}

data and output plugins to send data to another tool (heka is used in MOS LMA) Collectd collects the following metrics: cpu (CPU usage) df (disk usage/free

nova Channel: 2 Exchange: keystone Routing keys: [<<"lma_notifications.info">>] Routed queues: [<<"lma_notifications.info">>] Properties: [{<<"priority">>