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
feat(pyroscope.receive_http): Support pushv1.Push in receive_http (#2431)
* feat(pyroscope.receive_http): Support pushv1.Push in receive_http
/push.v1.PusherService/Push which is a connect API used by profilecli
and pyroscope.write with pyroscope.ebpf and pyroscope.alloy.
This is in addtion to the /ingest API the component already supports.
* Update changelog and docs
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,8 @@ Main (unreleased)
36
36
37
37
- Bump snmp_exporter and embedded modules to 0.27.0. Add support for multi-module handling by comma separation and expose argument to increase SNMP polling concurrency for `prometheus.exporter.snmp`. (@v-zhuravlev)
38
38
39
+
- Add support for pushv1.PusherService Connect API in `pyroscope.receive_http`. (@simonswine)
Copy file name to clipboardExpand all lines: docs/sources/reference/components/pyroscope/pyroscope.receive_http.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ title: pyroscope.receive_http
12
12
13
13
`pyroscope.receive_http` receives profiles over HTTP and forwards them to `pyroscope.*` components capable of receiving profiles.
14
14
15
-
The HTTP API exposed is compatible with the Pyroscope [HTTP ingest API](https://grafana.com/docs/pyroscope/latest/configure-server/about-server-api/).
15
+
The HTTP API exposed is compatible with both the Pyroscope [HTTP ingest API](https://grafana.com/docs/pyroscope/latest/configure-server/about-server-api/) and the [pushv1.PusherService](https://github.com/grafana/pyroscope/blob/main/api/push/v1/push.proto) Connect API.
16
16
This allows `pyroscope.receive_http` to act as a proxy for Pyroscope profiles, enabling flexible routing and distribution of profile data.
The component will start an HTTP server supporting the following endpoint.
31
31
32
32
*`POST /ingest` - send profiles to the component, which will be forwarded to the receivers as configured in the `forward_to argument`. The request format must match the format of the Pyroscope ingest API.
33
+
*`POST /push.v1.PusherService/Push` - send profiles to the component, which will be forwarded to the receivers as configured in the `forward_to argument`. The request format must match the format of the Pyroscope pushv1.PusherService Connect API.
0 commit comments