Ask Autohand Code to add logs, metrics, or traces that match the repo patterns and avoid leaking customer or secret data.
Log, measure, and trace the behavior that matters
Observability Delivery and operations Operate Workflow
autohand -p "Add observability for this workflow using the repo logging and metrics patterns"
Logs, metrics, or traces tied to the workflow with validation and privacy notes.
Add observability instrumentation with Autohand Code is an operations workflow that adds logs, metrics, or traces for a specific behavior while following repo conventions and privacy constraints. ### At a glance | Question | Answer | | --- | --- | | Best for | missing production signals, incident follow-up actions, support-heavy workflows, and release gates that need measurable behavior | | Primary inputs | The workflow, event, endpoint, or background job to observe; Existing logging, metrics, tracing, and dashboard conventions; Privacy rules, sampling rules, and fields that must never be emitted | | Autohand Code returns | Logs, metrics, or traces tied to the workflow with validation and privacy notes. | | Avoid when | the team has not decided what question the signal should answer | ### How Autohand Code handles this workflow 1. Finds existing instrumentation helpers and naming conventions. 2. Adds the smallest useful signal for the operational question. 3. Avoids secrets, customer data, and high-cardinality fields unless the repo has an approved pattern. 4. Adds or updates tests, docs, or dashboard notes so the signal can be used after deployment. ### Best inputs - The workflow, event, endpoint, or background job to observe - Existing logging, metrics, tracing, and dashboard conventions - Privacy rules, sampling rules, and fields that must never be emitted ### Strong prompt autohand -p "Add observability for this workflow using the repo logging and metrics patterns" ### Autohand Code CLI options - Run `autohand -p "Add observability for this workflow using the repo logging and metrics patterns"` with the operator question. - Use `/plan` when instrumentation touches backend code, dashboards, and alert rules. - Use `/mcp` for approved telemetry or dashboard tools, and keep credentials in `/settings` or config-managed secrets. ### Review before accepting A strong patch names the operational question, emitted fields, privacy checks, and the command or test used to verify the signal. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Add observability instrumentation with Autohand Code? Add observability instrumentation with Autohand Code is an operations workflow that adds logs, metrics, or traces for a specific behavior while following repo conventions and privacy constraints. ### When should a team use Add observability instrumentation? Use it when operators or support teams cannot answer a specific production question from existing signals. ### What evidence should reviewers check for Add observability instrumentation? A strong patch names the operational question, emitted fields, privacy checks, and the command or test used to verify the signal.
Guide Observability Add operational signals that answer specific production questions. /docs/guides/sre/observability.html Reference Telemetry Review telemetry behavior and configuration in Autohand Code. /docs/working-with-autohand-code/telemetry.html Reference Observability Permissions Control the permissions and data exposure around operational signals. /docs/agent-sdk/observability/permissions.html