From a1de5464eb5f6e9af2ab00c99d6cb60ddfd0c212 Mon Sep 17 00:00:00 2001 From: mesutoezdil Date: Wed, 15 Jul 2026 22:41:17 +0200 Subject: [PATCH] fix: correct doc errors in observability queries, tracing YAML, and valkey command Actor-centric log query used ate.dev/actor_id, actual label is ate.dev/actor_name. --- docs/dev/best-practices/tracing.md | 2 +- docs/dev/valkey-direct-access.md | 3 +-- docs/observability.md | 6 +++--- 3 files changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/dev/best-practices/tracing.md b/docs/dev/best-practices/tracing.md index cbdb9fb62..531717da9 100644 --- a/docs/dev/best-practices/tracing.md +++ b/docs/dev/best-practices/tracing.md @@ -87,7 +87,7 @@ The YAML manifest for your server should include the `OTEL_EXPORTER_OTLP_ENDPOIN - name: ateapi image: ko://github.com/agent-substrate/substrate/cmd/ateapi ports: - - "443:443" + - containerPort: 443 env: # Tracing related environment variables - name: OTEL_EXPORTER_OTLP_ENDPOINT diff --git a/docs/dev/valkey-direct-access.md b/docs/dev/valkey-direct-access.md index 8bae8f359..1dbf508ae 100644 --- a/docs/dev/valkey-direct-access.md +++ b/docs/dev/valkey-direct-access.md @@ -6,5 +6,4 @@ Valkey is the state store used by `ate-api-server` to track actor and worker rec To open a `valkey-cli` session: -1. `kubectl exec -n=ate-system -it valkey-cluster-0 -- valkey-cli -h valkey-cluster-service -c --tls --cacert /etc/valkey-ca/ca.crt --cer -t /run/servicedns.podcert.ate.dev/credential-bundle.pem --key /run/servicedns.podcert.ate.dev/credential-bundle.pem` +1. `kubectl exec -n=ate-system -it valkey-cluster-0 -- valkey-cli -h valkey-cluster-service -c --tls --cacert /etc/valkey-ca/ca.crt --cert /run/servicedns.podcert.ate.dev/credential-bundle.pem --key /run/servicedns.podcert.ate.dev/credential-bundle.pem` diff --git a/docs/observability.md b/docs/observability.md index 0f00b4141..163686a85 100644 --- a/docs/observability.md +++ b/docs/observability.md @@ -73,21 +73,21 @@ Because the logging pipeline indexes the core metadata labels, you can query you To track the unified, continuous lifecycle of a single actor regardless of how many times it migrated across worker pods or was suspended/resumed: ```text -labels.actor_id="test" +labels."ate.dev/actor_name"="test" ``` #### 2. Atespace-Centric View To monitor or debug all actor instances in a specific atespace (e.g., analyzing the collective behavior or error rates of all actors belonging to one tenant): ```text -labels.actor_atespace="ate-demo-counter" +labels."ate.dev/actor_atespace"="ate-demo-counter" ``` #### 3. Template-Centric View To monitor or debug all actor instances created from a specific ActorTemplate (e.g., analyzing the collective behavior or error rates of all counter actors). One atespace can run actors from many templates, so this is a distinct dimension from the atespace view above: ```text -labels.actor_template_name="counter" +labels."ate.dev/actor_template_name"="counter" ``` #### 4. Pod-Centric View