You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use logstash-exporter to monitor our logstash instances. It run as containers in host mode using the image you created wing924/logstash-exporter:v0.0.1.
Recently, we noticed the following errors every 30 seconds coming out of one logstash-exporter instance
Our prometheus instance is configured to scrape the the exporter every 15 seconds, so it seems out of every 2 scrapes, 1 times out immediately. Tried to talk to http://hostname:9600/_node/stats directly inside the exporter container with wget, they all succeeded and timeouts were found. Wondering if you may have any idea why could cause this?
Hi @Wing924 ,
We use
logstash-exporter
to monitor ourlogstash
instances. It run as containers inhost
mode using the image you createdwing924/logstash-exporter:v0.0.1
.Recently, we noticed the following errors every 30 seconds coming out of one
logstash-exporter
instanceOur
prometheus
instance is configured to scrape the the exporter every 15 seconds, so it seems out of every 2 scrapes, 1 times out immediately. Tried to talk tohttp://hostname:9600/_node/stats
directly inside the exporter container withwget
, they all succeeded and timeouts were found. Wondering if you may have any idea why could cause this?Here are the args we pass to
logstash-exporter
:which means we use the default
--logstash.timeout=5s
.The text was updated successfully, but these errors were encountered: