Monitor a Jitterbit private agent with Elasticsearch
Introduction
This page shows how you can remotely monitor the performance and behavior of Docker, Linux, or Windows private agents using the Elasticsearch and Kibana observability platform. Once properly configured, your private agents' metrics can be viewed using the Jitterbit-provided pre-built dashboard, or your own custom dashboard.
This feature is currently released as a beta version, supported on private agents version 11.37.0.7 or later. To provide feedback, contact the Jitterbit Product Team.
To set up Elasticsearch and Kibana, follow the steps in these sections in order:
-
Install the Metricbeat and Filebeat agents on the private agent host.
-
(Optional) Import a dashboard.
If you have any problems, consult the Troubleshoot section, or contact Jitterbit support.
Prerequisites
To use Elasticsearch and Kibana to monitor a private agent host, you must have the following:
-
Private agent 11.37.0.7 or later installed and running.
-
A working Elasticsearch and Kibana system installed and configured. To install these, refer to the following pages:
Install the Metricbeat and Filebeat agents
Metricbeat and Filebeat are data collecting agents that forward private agent metrics to your Elasticsearch/Kibana system. To install them, follow these steps:
-
Metricbeat:
-
To install Metricbeat on a private agent host, follow the Metricbeat instructions on the Elastic.co website.
-
To start Metricbeat when the host boots, follow the Metricbeat startup instructions on the Elastic.co website.
-
To check the Metricbeat connection to Elasticsearch, run the following command:
metricbeat test output
-
-
Filebeat:
-
To install Filebeat on a private agent host, follow the Filebeat instructions on the Elastic.co website.
-
To start Filebeat when the host boots, follow the Filebeat startup instructions on the Elastic.co website.
-
To check the Filebeat connection to Elasticsearch, run the following command:
filebeat test output
-
Set the Kibana index lifecycle policy
To set the data retention policy, follow these steps:
-
Open your Kibana web console.
-
Enter
index lifecycle policies
in the search bar, then select the resulting page. -
Click the Create policy button.
-
In the Create policy dialog, set the following values:
- Policy name:
private-agent-metrics-policy
- Policy name:
-
Turn on the Warm phase toggle, then set the following values:
- Move data into phase when: 30 days old.
-
Turn on the Cold phase toggle, then set the following values:
- Move data into phase when: 90 days old.
-
Click the Save policy button, then close the summary drawer.
Create Kibana templates
To create templates, follow these steps:
-
Create the
private-agent-metric-template
template:-
Enter
index management
in the search bar, then select the resulting page. -
Select the Index Templates tab.
-
Click the Create template button.
-
On the Logistics page, enter values for the following fields:
-
Name:
private-agent-metric-template
-
Index patterns:
private-agent-metric-8.15-*
-
-
Click the Next button.
-
On the Component templates page, click the Next button.
-
On the Index settings page, replace the contents of the Index settings field with the following:
{ "index": { "lifecycle": { "name": "private-agent-metrics-policy", "rollover_alias": "private-agent-metric-alias" }, "number_of_shards": "1", "number_of_replicas": "1" } }
-
Click the Next button.
-
On the Mappings page, in the Mapped fields tab, add fields according to the following table. Click the Add field button after each entry:
Field type Field name Keyword fields.env
Keyword private-agent.group
Keyword private-agent.name
-
Select the Advanced options tab, then set the following toggles to On:
-
Map numeric strings as numbers
-
Map date strings as dates
-
-
Click the Next button.
-
On the Aliases page, click the Next button.
-
On the Review details page, click the Create template button, then close the summary drawer.
-
-
Create the
private-agent-filebeat-template
template:-
On the Index Templates tab, click the Create template button.
-
On the Logistics page, enter values for the following fields:
-
Name:
private-agent-filebeat-template
-
Index patterns:
private-agent-filebeat-8.15-*
-
-
Click the Next button.
-
On the Component templates page, click the Next button.
-
On the Index settings page, replace the contents of the Index settings field with the following:
{ "index": { "lifecycle": { "name": "private-agent-metrics-policy", "rollover_alias": "private-agent-metric-alias" }, "number_of_shards": "1", "number_of_replicas": "1" } }
-
Click the Next button.
-
On the Mappings page, in the Mapped fields tab, add fields according to the following table. Click the Add field button after each entry:
Field type Field name Keyword message.fields.environment_name
Keyword message.fields.operation_name
Keyword message.fields.project_name
Keyword message.fields.status
Keyword private-agent.group
Keyword private-agent.name
-
Select the Advanced options tab, then set the following toggles to On:
-
Map numeric strings as numbers
-
Map date strings as dates
-
-
Click the Next button.
-
On the Aliases page, click the Next button.
-
On the Review details page, click the Create template button, then close the summary drawer.
-
Configure the Metricbeat and Filebeat agents
The Jitterbit private agent includes a script to configure Metricbeat and Filebeat. To use it when installing for the first time, or when upgrading from a private agent 11.34-based installation, follow these steps:
-
Run the following in a terminal or PowerShell:
cd /opt/jitterbit/scripts/ ./configure_elasticsearch.sh
cd /opt/jitterbit/scripts/ ./configure_elasticsearch.sh
cd "C:\Program Files\Jitterbit Agent\scripts\" .\configure_elasticsearch.ps
-
Read and respond to the following prompts:
-
Prompt 1:
************* ***WARNING*** ************* Installing the metric configurations will backup and overwrite your metricbeat configuration files. Do you wish to proceed? 1) Yes 2) No
Enter the number corresponding to your choice, followed by the Enter key. The choices are as follows:
-
1
: Continue the script. If you have existing Metricbeat and Filebeat configuration files (/etc/metricbeat/metricbeat.yml
and/etc/filebeat/filebeat.yml
), backup copies are made (/etc/metricbeat/metricbeat.yml.jb.bak
and/etc/filebeat/filebeat.yml.jb.bak
) and new ones are created. -
2
: Stop the script.
-
-
Prompt 2:
************* ***WARNING*** ************* Turning on Agent observability on the agent will turn on Enhanced Capability feature for the agent. Enhanced Capability might affect the operation routing behavior for the agents. Do you wish to proceed? 1) Yes 2) No
Enter the number corresponding to your choice, followed by the Enter key. The choices are as follows:
-
1
: Continue the script. This setsEnhancedCapabilityMetricsEnabled
totrue
in the[AgentCapability]
section ofjitterbit.conf
. -
2
: Stop the script.
-
-
Note
To enable observability in Docker private agents, you must use environment variables.
Import an Elasticsearch dashboard
To import a pre-built Elasticsearch dashboard, follow these steps:
-
Download the Jitterbit Private Agent Elasticsearch dashboard JSON file from the Harmony portal Downloads page.
-
Enter
kibana saved objects
in the Elasticsearch search bar, then select the resulting page. -
Click the Import button.
-
In the Import saved objects dialog, click Import, find the downloaded dashboard JSON file, then select it.
-
Under Import options, select Check for existing objects with Automatically overwrite conflicts.
-
Click the Import button.
-
Click the Done button.
-
To use the dashboard, enter
dashboards
in the Elasticsearch search bar, select the resulting page, then select Jitterbit Harmony Private Agent Dashboard.
Troubleshoot Elasticsearch issues
To help solve any issues with Elasticsearch components, you can check the Elasticsearch documentation, inspect log files, or run diagnostic commands.
Elasticsearch documentation
-
Metricbeat:
-
Filebeat:
Elasticsearch log files locations
-
/var/log/metricbeat
-
/var/log/filebeat