Configuration Guide

Plugin configuration

To configure your plugin, you need to follow the folling steps:

1. Create a new environment with the Fuel web user interface.
2. Click on the Settings tab of the Fuel web UI.
3. Select the LMA collector plugin in the left column. The LMA Collector settings screen appears.

4. Select the LMA collector plugin checkbox and fill-in the required fields.

1. Select “Local node” for Events analytics if you deploy the Elasticsearch-Kibana plugin on a dedicated node in the same environment.
2. Select “Remote server” for Events analytics if you have an Elasticsearch-Kibana server already deployed and running. In that case, you have to enter the IP address or the fully qualified name of the server.
3. Select “Local node” for Metrics analytics if you deploy the InfluxDB-Grafana plugin on a dedicated node in the same environment.
4. Select “Remote server” for Metrics analytics if you have an InfluxDB-Grafana server already deployed and running. In that case, you have to enter the IP address or the fully qualified name of the server as well as the credentials and database to store the metrics.
5. Select “Alerts sent by email” for Alerting if you wish to receive alerts by email.
6. Select “Alerts sent to a local node” for Alerting if you deploy the LMA Infrastructure Alerting plugin on a dedicated node in the same environment.
7. Select “Alerts sent to a remote Nagios server” for Alerting if you have a Nagios server already deployed and running.

5. Configure your environment as needed.
6. Assign roles to the nodes for the environment.
7. Verify networks on the Networks tab of the Fuel web UI.
8. Deploy your changes.

Plugin verification

Once the OpenStack environment is ready, you may want to check that both collectd and hekad processes are running on the controller nodes:

[root@node-1 ~]# pidof hekad
5568
[root@node-1 ~]# pidof collectd
5684

Please refer to the Troubleshooting section otherwise.

Troubleshooting

If you see no data in the Kibana and/or Grafana dashboards, use the instructions below to troubleshoot the problem:

1. Check if the LMA collector service is up and running:

   # On the controller nodes
   [root@node-1 ~]# crm resource status lma_collector
   
   # On nodes which are not controllers
   [root@node-1 ~]# status lma_collector
   

2. If the LMA Collector is down, restart it:

   # On the controller nodes
   [root@node-1 ~]# crm resource start lma_collector
   
   # On nodes which are not controllers
   [root@node-1 ~]# status lma_collector
   

3. Look for errors in the LMA Collector log file (located at /var/log/lma_collector.log) on the different nodes.

4. Look for errors in the collectd log file (located at /var/log/collectd.log) on the different nodes.

5. Check if the nodes are able to connect to the Elasticsearch server on port 9200.

6. Check if the nodes are able to connect to the InfluxDB server on port 8086.