search

CiscoDevNet / bigmuddy-network-telemetry-stacks

A batteries-included docker-based collection of demo stacks adapting network streaming telemetry to common consumer formats.
Apache License 2.0
49 stars 19 forks source link

Incompatibility with docker image: prom/pushgateway:v0.4.0 #9

Open michaelbonnettjr opened 7 years ago

michaelbonnettjr commented 7 years ago

Hi,

I'm unable to get Pipeline to work with v0.4.0 of the prom/pushgateway Docker image. (Pipeline works fine with the older v0.3.1 image.)

When running prom/pushgateway v0.4.0, my pipelinle.log file is filled with the following:

`time="2017-06-15 21:34:54.519836" level=error msg="http reply" error="unexpected status code 400 while pushing to http://localhost:9091/metrics/job/telemetry/instance/pipeline_11823492967441504429" instance=pipeline jobName=telemetry pushGWAddress="http://localhost:9091" pushURL="http://localhost:9091/metrics/job/telemetry/instance/pipeline" tag=pipeline

time="2017-06-15 21:34:54.533393" level=error msg="http reply" error="unexpected status code 400 while pushing to http://localhost:9091/metrics/job/telemetry/instance/pipeline_17704715107158349698" instance=pipeline jobName=telemetry pushGWAddress="http://localhost:9091" pushURL="http://localhost:9091/metrics/job/telemetry/instance/pipeline" tag=pipeline `

Regards,

Michael

cchance27 commented 6 years ago

same issue rolled back to 0.3.1 and it worked, still no one knows why 0.4.0 is 400 erroring?

attiss commented 6 years ago

It's still a problem with prom/pushgateway v0.5.2.

Probably there was a message format change between v0.3.1 and v0.4.0, that is not updated in Pipeline.

I'll look after it.

kaminek commented 5 years ago

👋 same issue here even with v0.8

aroramanish2009 commented 4 years ago

fails on v1.2.0 as well.