Product Guides
Product Overview
Use Vight as an investigation workspace: start from health, narrow to a service, and pivot into traces, logs, errors, runtime, alerts, issues, and releases.
Overview
Use this page to understand how Vight expects an investigation to move. It is the map of the product itself: begin with service health, narrow the owner, prove the behavior with traces and logs, then use errors, issues, alerts, releases, runtime, and infrastructure as supporting context.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Start in Dashboard or Services to find the affected service and time range. Open service detail when you need endpoint, dependency, runtime, log, trace, and error evidence in one place. Use Releases, Alerts, and Issues as context for what changed and what Vight already flagged.
- Starting point
- Dashboard and Services tell you where to begin. They are for triage, not final proof.
- Evidence path
- Service detail, traces, logs, and errors turn a broad symptom into request-level evidence.
- Change context
- Releases, runtime, infrastructure, alerts, and issues explain why the symptom may have started.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
A latency issue appears on the dashboard. Open Services and identify the service with the clearest latency change.
- 2
Open that service, inspect endpoints, then open traces for the slow route.
- 3
Use logs, releases, runtime, and issues only after the slow request path is clear.
Interpretation note
Do not treat a top-level card as proof of cause. Use it to choose the next page. Do not compare pages with different environments or time ranges. Do not jump to release rollback until traces or logs support the timing.
Related pages
Services
Find the unhealthy service before opening deeper evidence.
Traces
Inspect slow or failed requests at span level.
Logs
Read timestamped events with service and trace context.
Alerts
Understand rule status and response workflow.
Slow API after deploy
Follow the release-to-service investigation path.
Error rate rising
Move from error groups to trace and log evidence.
Core concepts
Learn the nouns Vight uses across investigations.
Filters and time ranges
Understand how page filters change the evidence you see.