Skip to content
Discussion options

You must be logged in to vote

Filebeat has some capabilities to reestablish connections to Logstash and continue forwarding when the connection is lost, but I don't think we're doing anything specific to adjust it from the defaults.

You can monitor the logstash pipelines via the pipeline API which is available via the Malcolm API at /mapi/logstash/.

If you are using an external elasticsearch or opensearch instance, then Logstash uses a persistent queue in case the connection to the data store is lost. When Malcolm uses its own embedded opensearch instance, it uses whatever logstash's default queue type is.

I'm not sure what you mean by "monitoring plan".

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by mmguero
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
elastic Related to issue with external ElasticSearch/Kibana output logstash Relating to Malcolm's use of Logstash opensearch Relating to Malcolm's use of OpenSearch performance Related to speed/performance
2 participants