Concepts & Reference
Filters And Time Ranges
Use filters deliberately so Vight narrows evidence without hiding the signal you are trying to prove.
Concept
Use filters deliberately so Vight narrows evidence without hiding the signal you are trying to prove.
The time range controls the evidence window for dashboards, lists, charts, traces, logs, errors, runtime signals, and releases.
Service and environment filters define which application slice you are investigating.
Status, severity, text, version, deployment, and route filters narrow the evidence after the broad symptom is confirmed.
Examples
- Setup validation
- Use a broad time range and minimal filters when confirming a new service is sending data.
- Incident window
- Use the reported customer-impact window when comparing services, traces, logs, and errors.
- Release comparison
- Compare before and after windows with the same service, environment, endpoint, and version filters.
How Vight uses it
Start broad when validating setup or looking for an unknown owner. Narrow by service and environment once you know where the symptom lives. Use status or error filters after confirming the service has traffic in the selected window. Use text filters in Logs after setting time range and service, not before. If a page looks empty, widen time range and remove filters before assuming data is missing.
Usage guidance
Change one filter at a time when a page becomes empty. Reset status, severity, and text filters before concluding data is missing. Keep the same time range when moving from a chart to a detail page. Use short windows for precise incidents and broad windows for discovery.