Find the problem
Find recurring failures, changes in behavior and the release context around an Issue.
Observability
Ask your agent about a failure. It reads errors, traces, logs, metrics and service health, and follows person-linked signals into the customer experience around it.
Begin with a service, Issue, request, log or alert.
Your agent moves between traces, logs, errors and service health.
Customer-linked signals lead to the experience around the failure.
01Error to evidence
Your agent groups failures into Issues, checks the affected release and reads the trace and logs around the request. You open the Issue or the trace as a read-only page to check what it found.
02Customer impact
The request explains the system. When its signals carry customer identity, the person timeline and the replay show the experience around it. Your agent keeps both in the same investigation.
The workflow, connected
Start from the view that suits the question. Your agent inspects the connected evidence around it.
Open an Issue, alert, service view or telemetry search for the relevant environment.
Follow trace spans, related logs and recorded release context.
Follow person-linked evidence into customer stories, or attach the findings to an incident.
The capabilities behind it
Errors, request detail, operational measurements and service context give your agent several ways to understand a problem.
Find recurring failures, changes in behavior and the release context around an Issue.
Inspect requests and service activity, and turn useful log signals into measurements.
Understand service health and follow customer impact when identity is recorded.
Put it to work
Inspect grouped errors and the trace spans and logs around the affected requests.
Explore this workflowCompare recorded release context and inspect the Issues around the rollout.
Explore this workflowFollow person-linked errors and requests into their captured product journeys.
Explore this workflowYour first useful workflow
Use a supported SDK or OpenTelemetry, then verify the request path and identity you want to investigate.
Use OpenTelemetry for instrumented service and request evidence.
Read the guideA few useful answers
No. Begin with a service, log, trace, Issue or alert. The person dimension appears when the captured signals connect to one.
Yes. Supported SDKs and OpenTelemetry carry telemetry into Anectico. The integration guide helps choose the appropriate capture path.
An incident case file can bring attached Issues, alerts, customer context and the response timeline into an owned investigation.
Yes. Services, logs, metrics, traces and Issues remain useful entry points. Customer identity adds another way to follow recorded impact when it is present.
Yes. The CLI works from any terminal as well as from a coding agent. It reads the same telemetry with the same keys.
Anectico / Private preview
Explore connected technical and customer investigation with your agent in private preview.