Investigate service health and dashboards

Use service-level views when a symptom affects many customers or does not yet have a customer or Issue to start from.

Find the affected service

Open Explore → Dashboards for the current operational picture; Overview is the built-in default dashboard. Then use Services to compare exact entry-span count, activity rate, error rate, p50, p95, and server-derived health. Filter by service name or health, and sort any metric column. Open a service to inspect those signals over time, jump to its filtered traces or Issues, or start an alert with that service preselected. A retained snapshot is labelled while a scope change loads, and a failed RED read stays explicit and retryable instead of becoming an empty chart. Activity includes inbound server spans, message-consumer spans, and root internal or producer spans from scheduled jobs. Child implementation spans and outbound client spans do not inflate the rate, so APIs, queue workers, and batch services share one useful catalog.

Use Service Map to see upstream and downstream dependencies from distributed traces. The map is incomplete when services do not propagate trace context or sampling removes the relevant calls; it is evidence from observed traces, not a configuration inventory. Parent relationships produce synchronous HTTP/gRPC/database edges. Retained span links preserve asynchronous producer-to-consumer edges and queue delay even when an asynchronous consumer starts a fresh trace. Explicit external peers and missing peers are labeled separately; Anectico does not invent a service name. Cycles, bottlenecks, and the service-level critical path are computed by the server so every client sees the same analysis. Select a directed edge in the keyboard-accessible Relationships list to inspect its call and error counts, average and p95 latency, protocol, dependency kind, and asynchronous queue wait. A truncation warning means the bounded server analysis reached its span limit and the graph covers an analyzed subset.

The RED values and health shown on an observed service node use exactly the same entry spans, environment, time window, counts, percentiles, and thresholds as Services. External and unknown boundary nodes have no health because Anectico has no service-entry telemetry for them.

Explain the symptom

1. Fix the project, environment, and time window.
2. Identify the service where rate, errors, or latency changed.
3. Open representative traces from that same window.
4. Follow the critical path and error spans into correlated logs. On asynchronous paths, the queue gap is shown separately from span work and is included in the server’s wall-time total. If the analysis request fails, retry it from the explicit critical-path error without losing the span timeline.
5. When a customer or Issue appears, switch to that connected story for impact and replay evidence.

Metrics show where and when behavior changed. Traces and logs explain why.

Save a dashboard

Open Explore → Dashboards, open the dashboard selector in the page heading, and choose New dashboard… for a question the team expects to ask again. Add and arrange widgets in the dashboard editor. Members with dashboard write access can create, clone, and change widgets or layout. The dashboard owner and organization admins can also change its name, description, tags, and variables; deletion additionally requires dashboard delete access. Viewers are read-only, including when they were previously recorded as the dashboard owner.

Share copies the current authenticated dashboard URL, including its selected variable filters. It does not make the dashboard public: the recipient must sign in to the same organization and have access to the dashboard. If Anectico reports that the dashboard changed in another session, it refreshes the latest version instead of overwriting it; review the refreshed dashboard before trying again. If your session expires while creating a dashboard and cannot be restored, the create form stays open with your name and description intact. Sign in again if prompted, then explicitly retry; Anectico does not report the dashboard as created until the save succeeds. If dashboard requests are temporarily rate limited, the page names that state explicitly and makes a small, bounded number of automatic retries after the server-requested delay. If the limit remains, use Retry now after waiting a moment; other service or connection failures remain separately labelled and manually retryable.

Use Manage dashboards in the same selector to clone or delete dashboards. Rename or delete a dashboard only after checking who relies on it.

Avoid dashboards that merely duplicate Customers, Issues, or a service detail page. Give each dashboard a question-oriented name such as “Checkout latency by environment,” and keep time and project assumptions visible.

• Search logs, traces, and metrics
• Explore and compare metrics
• Create alerts