Skip to content

Commit 61f7a9f

Browse files
scooby87lexfrei
authored andcommitted
docs(platform): match the tracing rate row to what the render accepts
The 3 MiB request cap answers with a 400 only over OTLP/HTTP; over gRPC the same cap is max_recv_msg_size_mib, and grpc-go refuses an oversized message with RESOURCE_EXHAUSTED. The platform render also accepts any whole unquoted number, such as 1e6, and requires plain decimal digits only when the value is a string. Assisted-by: LLM Signed-off-by: Alexey Artamonov <[email protected]>
1 parent b495307 commit 61f7a9f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎content/en/docs/next/operations/configuration/platform-package.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ gateway:
163163
| Value | Default | Description |
164164
| --- | --- | --- |
165165
| `monitoring.rootEnabled` | `true` | Whether the root tenant hosts the platform metrics and logs stack, that is, whether `Tenant/root` has `spec.monitoring: true`. When `true`, the platform creates the `ExternalName` Services in `cozy-monitoring` that redirect metrics and logs into `tenant-root`. Nothing sets `spec.monitoring` on the root Tenant from this value: set it to match the root Tenant. With `true` while the root tenant has monitoring disabled, the redirects lead nowhere and fluent-bit silently drops logs. The default `true` keeps the earlier behaviour of always creating them; the slim variants (`isp-slim`, `isp-slim-generic`, `isp-hosted-slim`) default to `false`. |
166-
| `monitoring.tracingCentralTenantBytesPerSecond` | `0` | The rate, in bytes per second counted uncompressed and before sampling, at which each tenant using shared-central tracing may write into the traces store that `tenant-root` hosts. Each tenant's collector refuses data above it: an OTLP/HTTP sender gets a `429` and retries, while an OTLP/gRPC sender gets `RESOURCE_EXHAUSTED` and drops the spans, so central tenants should export over HTTP. A request larger than 3 MiB gets a `400` and is not retried. `0` keeps the default of about 97 KiB/s, at which one tenant alone cannot fill the disk cap of a default 10Gi store within the two days VictoriaTraces always keeps, so a larger store needs the rate raised with it. The value must be a whole number of bytes per second written in plain decimal digits, up to `1099511627776` (1 TiB/s); anything else, such as `"1Mi"` or `1.5`, fails the platform render. Each collector pod starts with a full bucket, so a pod start lets through up to 5 MiB above the rate, or one second of the pod's share of the rate when that is larger. The rate bounds each tenant, not the sum of all tenants. A change upgrades every release in every tenant once, since it travels in the `cozystack-values` Secret they all read. |
166+
| `monitoring.tracingCentralTenantBytesPerSecond` | `0` | The rate, in bytes per second counted uncompressed and before sampling, at which each tenant using shared-central tracing may write into the traces store that `tenant-root` hosts. Each tenant's collector refuses data above it: an OTLP/HTTP sender gets a `429` and retries, while an OTLP/gRPC sender gets `RESOURCE_EXHAUSTED` and drops the spans, so central tenants should export over HTTP. An OTLP/HTTP request larger than 3 MiB gets a `400` and is not retried. `0` keeps the default of about 97 KiB/s, at which one tenant alone cannot fill the disk cap of a default 10Gi store within the two days VictoriaTraces always keeps, so a larger store needs the rate raised with it. The value must be a whole number of bytes per second, or a string of plain decimal digits, up to `1099511627776` (1 TiB/s); anything else, such as `"1Mi"` or `1.5`, fails the platform render. Each collector pod starts with a full bucket, so a pod start lets through up to 5 MiB above the rate, or one second of the pod's share of the rate when that is larger. The rate bounds each tenant, not the sum of all tenants. A change upgrades every release in every tenant once, since it travels in the `cozystack-values` Secret they all read. |
167167

168168
#### Backup storage
169169

0 commit comments

Comments
 (0)