Install and configure Elastic Stack to monitor IBM® Component Pack for Connections.
Before you begin
Before attempting to install Elastic Stack verify that the following tasks were successfully completed:
About this task
The following components are deployed as part of the Elastic Stack offering:
- Filebeat
- Logstash
- Kibana
- Elasticsearch-curator
Procedure
-
Install the Elastic Stack Helm chart by running the following command:
helm install \
--name=elasticstack extractedFolder/microservices_connections/hybridcloud/helmbuilds/elasticstack-0.1.0-20200321-174055.tgz \
--set \
global.onPrem=true,\
global.image.repository=Docker_registry/connections
Note: If you want to filter out logs from collection by Elastic Stack, include the
logstash.filterOut
Helm parameter as explained in
Filtering out logs.
What gets deployed?
- 1 Filebeat pod per Kubernetes node
- 3 Logstash pods (hosted on infrastructure workers if available)
- 3 Kibana pods (hosted on infrastructure workers if available)
-
Verify that Elastic Stack was successfully deployed:
-
Verify that the installation completed by running the helm list command.
When the installation completes, the chart's status shows as
DEPLOYED. It can take up to 5 minutes for all pods to start and begin
to process logs.
-
Run the following command to check the status of all of the pods:
In the following example, connections
is the name of the namespace.
kubectl get pods -n connections