Coralogix provides a seamless integration with
Metricbeat so help you send your metric data from anywhere and create metric dashboards.
This document includes cluster dependent URL’s. Each URL has a variable part (in Italic). Please match this part with a row entry within the following table. Copy the table row entry located under the column that matches the top level domain of your Coralogix account (.com, .in etc.). Replace the variable part of the URL with this entry.
Metricbeatinstalled, for more information on how to install: https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-installation.html
Private Key – A unique ID that represents your company. The private key can be found under ‘settings’->’ send your logs’. It is located in the upper left corner.
Company Id – A unique number which represents your company. You can get your company id from the settings tab in the Coralogix dashbaord.
Application Name – The name of your main application, for example, a company named “SuperData” would probably insert the “SuperData” string parameter or if they want to debug their test environment they might insert the “SuperData– Test”.
SubSystem Name – Your application probably has multiple subsystems, for example: Backend servers, Middleware, Frontend servers etc. in order to help you examine the data you need, inserting the subsystem parameter is vital.
Metricbeat configuration file and configure it to use
Logstash. For more information about configuring
Metricbeat to use
Logstash please refer to: https://www.elastic.co/guide/en/beats/metricbeat/current/logstash-output.html
Metricbeat to output to Coralogix logstash server:
In addition you should add Coralogix configuration from the General section.
Here is a basic example of metricbeat.yml file for collecting metrics from a
Note: If you want to send all additional metadata, the fields_under_root option should be equals to false.
Build Docker image with your metricbeat.yml:
You can also deploy with Docker-compose:
Make sure you change owner of metricbeat.yml file to root (uid=1000). /n /n