diff --git a/code-of-conduct.md b/code-of-conduct.md index 6070ae1cd..4c0c00abc 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -90,6 +90,6 @@ harassment or threats to anyone's safety, we may take action without notice. ## Attribution -This Code of Conduct is adapted from the Contributor Covenant, version 1.4, +This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at -https://www.contributor-covenant.org/version/1/4/code-of-conduct/ +https://www.contributor-covenant.org/version/2/1/code_of_conduct/ diff --git a/docs/dev/best-practices/tracing.md b/docs/dev/best-practices/tracing.md index 9b72b56d1..e62f1b874 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 bbf013c0b..8ed75e92d 100644 --- a/docs/observability.md +++ b/docs/observability.md @@ -72,14 +72,14 @@ 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_id"="test" ``` #### 2. Template-Centric View To monitor or debug all actor instances created from a specific template (e.g., analyzing the collective behavior or error rates of all counter actors): ```text -labels.actor_template="counter" +labels."ate.dev/actor_template_name"="counter" ``` #### 3. Pod-Centric View