Observability

Find the failure.Follow the impact.

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.

Example: an agent session and its proofErrors and traces / Logs and metrics / Service health
  • Start from the system

    Begin with a service, Issue, request, log or alert.

  • Inspect the signals

    Your agent moves between traces, logs, errors and service health.

  • Understand the impact

    Customer-linked signals lead to the experience around the failure.

01Error to evidence

An Issue is a starting point. The request tells you more.

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.

  • Triage grouped errors and inspect recorded regressions.
  • Read the distributed request path and its failed spans.
  • Search logs or live-tail the relevant service activity.
Explore technical evidence

02Customer impact

Know more than which service failed.

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.

  • Follow the affected people from person-linked evidence.
  • Open the recorded journey around a failing request.
  • Use the same context in an owned incident.
Follow the customer story

The workflow, connected

Follow the failure across the signals.

Start from the view that suits the question. Your agent inspects the connected evidence around it.

  1. Find the symptom

    Open an Issue, alert, service view or telemetry search for the relevant environment.

  2. Inspect the request

    Follow trace spans, related logs and recorded release context.

  3. Understand the reach

    Follow person-linked evidence into customer stories, or attach the findings to an incident.

The capabilities behind it

The system signals your investigation needs.

Errors, request detail, operational measurements and service context give your agent several ways to understand a problem.

Put it to work

For the questions behind the alert.

Which request path is failing?

Inspect grouped errors and the trace spans and logs around the affected requests.

Explore this workflow

Did the release change error behavior?

Compare recorded release context and inspect the Issues around the rollout.

Explore this workflow

Which customers experienced the failure?

Follow person-linked errors and requests into their captured product journeys.

Explore this workflow

Your first useful workflow

Bring the signals your system already produces.

Use a supported SDK or OpenTelemetry, then verify the request path and identity you want to investigate.

  1. Choose the integration

    Select capture for your language, platform and telemetry path.

    Read the guide
  2. Connect request tracing

    Use OpenTelemetry for instrumented service and request evidence.

    Read the guide
  3. Verify captured evidence

    Check the project, environment and first recorded signals.

    Read the guide

A few useful answers

A few useful details.

Do I have to start from a person?

No. Begin with a service, log, trace, Issue or alert. The person dimension appears when the captured signals connect to one.

Can I bring OpenTelemetry?

Yes. Supported SDKs and OpenTelemetry carry telemetry into Anectico. The integration guide helps choose the appropriate capture path.

How does this connect to incidents?

An incident case file can bring attached Issues, alerts, customer context and the response timeline into an owned investigation.

Can I keep ordinary service-based 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.

Can I use the CLI myself?

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

Bring the failure.Follow what it affected.

Explore connected technical and customer investigation with your agent in private preview.