From 94e5613da538c7d58e83e9cbbcc810536431744a Mon Sep 17 00:00:00 2001 From: Michi Hoffmann Date: Mon, 17 Nov 2025 21:17:39 +0100 Subject: [PATCH] Document backend SDKs metrics requirements Added documentation for backend SDKs and their metrics. --- develop-docs/sdk/telemetry/metrics.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/develop-docs/sdk/telemetry/metrics.mdx b/develop-docs/sdk/telemetry/metrics.mdx index e08db2597af772..c22862a38893de 100644 --- a/develop-docs/sdk/telemetry/metrics.mdx +++ b/develop-docs/sdk/telemetry/metrics.mdx @@ -425,6 +425,18 @@ By default, Relay should parse the user agent attached to an incoming metric env } ``` +#### Backend SDKs + +For backend SDKs (Node.js, Python, PHP, etc.), the SDKs should attach the following: + +1. `server.address`: The address of the server that sent the log. Equivalent to [`server_name`](sdk/data-model/event-payloads/#optional-attributes) we attach to errors and transactions. + +```json +{ + "server.address": "foo.example.com" +} +``` + #### Future Default Attributes The SDKs should aim to minimize the number of default attributes attached to a metric. Metrics cardinality can explode quickly with too many attributes, and we want to keep metrics lightweight and cost-effective.