Observability
Update a telemetry export
Change an export: its name, endpoint, signals and whether it is enabled.
PATCH
/workspaces/{workspace}/projects/{project}/observability/exports/{id}Only what you give changes. Headers given are set; a header given as “” is removed; those not given are kept. Needs the Admin role.
Only what is given changes. A header given is set, a header given as "" is removed, and the rest are kept. Needs the Admin role.
- Authentication: Required. Send an access token as
Authorization: Bearer. - MCP tool: None. Signing in is on the REST API only.
Path parameters
Section titled “Path parameters”| Name | Type | Required | Description |
|---|---|---|---|
workspace |
string | Yes | The workspace’s slug, e.g. “flagon-io”. |
project |
string | Yes | The project’s slug, as in g1t.sh/{workspace}/{project}. |
id |
string | Yes | The export’s id. |
Body parameters
Section titled “Body parameters”Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.
| Name | Type | Required | Description |
|---|---|---|---|
name |
string | No | Its name, for people. |
endpoint |
string | No | The OTLP/HTTP base address, such as https://otlp.example.com; /v1/traces and the rest are added. |
signals |
array of strings | No | What it sends: traces, logs and metrics. All three unless you say. One of traces, logs, metrics. |
headers |
object | No | Headers sent with each request, such as an API key. Written, never read back; “” removes one. |
enabled |
boolean | No | Whether it sends. True unless you say. |
Example request
Section titled “Example request”curl -X PATCH https://api.g1t.sh/workspaces/flagon-io/projects/g1t/observability/exports/x7d2k9m4 \ -H "Authorization: Bearer $G1T_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "enabled": false }'Example response
Section titled “Example response”A successful request answers 200 with:
{ "id": "x7d2k9m4", "name": "Honeycomb", "endpoint": "https://api.honeycomb.io", "signals": [ "traces", "logs" ], "header_names": [ "x-honeycomb-team" ], "enabled": false, "last_error": null, "last_sent_us": 1791813809000000}Errors
Section titled “Errors”A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.
| Status | Code | When |
|---|---|---|
| 401 | unauthenticated |
A token is required, or the one sent is not valid. |
| 403 | forbidden |
The token is valid but not allowed to do this, such as a member-only change, or a token without the scope it needs. |
| 404 | not_found |
It does not exist, or you cannot see it. |
| 409 | conflict |
The request conflicts with the current state. |
| 422 | invalid |
The input is not valid. message says which field and why. |