Request compression Unable to submit

[bearfishops]

I run this shell command。
echo "some_metric 3.14" | gzip | curl --data-binary @- http://xxx.xxx.xxx.xxx:59091/metrics/job/xy_influxdb_exporter/instance/test1

Unable to submit normally. The following information is returned。
text format parsing error in line 1: invalid metric name

[1skt0]

i have the same problem

[beorn7]

You have to add the Content-Encoding: gzip header, as mentioned in the example:

echo "some_metric 3.14" | gzip | curl -H 'Content-Encoding: gzip' --data-binary @- http://pushgateway.example.org:9091/metrics/job/some_job

[gaoyanyu]

problem exists even "Content-Encoding: gzip" added to header, like this:

[beorn7]

In this case, I assume you are using one of the released binaries, while the feature is not yet in any release (just in the master branch).

I do plan to cut a release very soon.

[beorn7]

The new release is out: https://github.com/prometheus/pushgateway/releases/tag/v1.5.0

[bearfishops]

Thank you. After I switch the release to v1.5.0, it can be submitted successfully

[tgeo-cambrian]

@beorn7 Hello, does it need an extra flag or something when launching the container to accept the gzip output?

i.e. I face the below issue in version 1.5.0

I am pushing some metrics from a windows ephemeral VM
first getting the metrics from wmi exporter

curl http://localhost:9182/metrics

gziping them

tar -czvf metricscmd.gz metricscmd

*   Trying <redacted>:9091...
* Connected to <redacted> port 9091 (#0)
> POST /metrics/job/test-job/instance/test-curl-cmd HTTP/1.1
> Host: <redacted>:9091
> User-Agent: curl/7.83.1
> Accept: */*
> Content-Encoding:gzip
> Content-Length: 68950
> Content-Type: application/x-www-form-urlencoded
>
* We are completely uploaded and fine
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 Bad Request
< Date: Tue, 29 Nov 2022 15:07:20 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 435
< Connection: keep-alive
< X-Content-Type-Options: nosniff
<
text format parsing error in line 1: expected float as value, got "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00000666"
* Connection #0 to host <redacted> left intact```

[beorn7]

I would assume that taring the payload adds additional data to it that cannot be read by the Pushgateway.

You have to just gzip the metrics.

In different news, the Pushgateway is not designed to receive the metrics from a regular Prometheus endpoint. You should scrape that endpoint directly, maybe using something like https://github.com/prometheus-community/PushProx if you cannot reach it directly.

[tgeo-cambrian]

@beorn7 I know, the design decision is not mine. You are right tar does some funky stuff, and it needs gzip or 7z gzip implementation which is clear. I can confirm it works, just need to work around windows issues. Thanks alot.