Shared Filters
Keep the same project, environment, user, and time range as you move between errors, logs, and performance data.
Choose an investigation scope
Use the project selector to choose one or more projects, then select an environment and time range in the investigation bar. The user selector narrows supported views to an application user.
The rolling ranges are 1h, 24h, 7d, 30d, and 90d. A fresh session starts at 24h unless a saved selection or link supplies another range. All is also available on the issues list and searches retained occurrences without a lower time bound. Selecting 90d does not extend your instance's retention policy.
Selections follow you between investigation pages and are reflected in the address bar. Browser Back and Forward restore the filters in those links. Clear a selected user with the cross on their chip, or choose All in the project or environment selector to broaden the results. Opening a page without filter parameters can reuse the current session's selections.
What the filters apply to
| View | What changes with the selection |
|---|---|
| Issues | Matching occurrences, counts, affected users, first/last seen, and sparklines. Issue status remains its current status. |
| Logs | Entries matching project, environment, user, and SDK event time, plus the local level and message filters. |
| Transactions and Browser | Metrics within the selected scope. Selecting a user switches these views to individual traces and page loads. |
| Queries, Caches, and Jobs | Span summaries within the scope, with user matching taken from the containing transaction. |
| Dashboard | Transaction metrics follow the filters. Open issues, alerts, releases, and monitors show current state across environments and users. Transaction density keeps its labeled seven-day window. |
| Releases | Deployments and release-wide metrics. Investigation time and environment filters do not apply. |
| Monitors | Current state, latest checks, and explicitly labeled uptime windows. Investigation time and environment filters do not apply. |
| Individual issues, events, and transactions | The selected record has its own project and event time. Investigation context is preserved for returning to a list. |
Release and monitor pages retain your investigation context for navigation; they do not become a history of one user's activity. Open Data freshness and scope in the investigation bar when comparing a view's numbers with another page.
For issues, selecting last week means “occurrences from last week with the issue's current status.” It does not recreate which issues were open at that point in time.
Share a link
Copy the URL from your browser after setting the filters. The recipient still needs access to the instance and selected projects. A rolling link such as range=24h means the latest 24 hours when opened, so the results can change over time.
For a fixed interval, use range=custom with from and to timestamps in the URL. The dropdown displays Custom for these links; it does not provide a date picker. For example, on your Tindra instance:
/logs?project_id=all&environment=production&user=customer-42&range=custom&from=2026-09-09T08:00:00Z&to=2026-09-09T09:00:00Z
Bounds must include a timezone, with the start before the end and a maximum interval of 90 days. Tindra queries UTC instants, including the start and excluding the end. Use Z for UTC, or URL-encode the plus sign in a positive offset as %2B.
Use a project's UUID for project_id, repeating the parameter to select several projects. project_id=all and environment=all explicitly clear those selections; user= clears the user. Keep these explicit when sharing an unfiltered view so the recipient's session does not supply a selection. Invalid ranges or project selections show an error that asks you to choose valid filters.
A fixed interval keeps the time bounds stable, but late arrivals, retention, and changes to issue status can still change the results.
Refresh and browsing history
Logs refresh automatically every five seconds, other telemetry views every 30 seconds, and release and monitor lists every 60 seconds. The freshness indicator shows when the displayed data was last updated; an error can leave the previous results visible.
Use Pause to stop automatic updates and Resume to enable them again. Automatic refresh also stops for fixed custom intervals, while browsing older results, when the tab is hidden, or when the browser is offline. Resuming does not override those conditions.
Manual refresh reloads the view and returns paginated lists to their newest results. It is unavailable while offline. The issue detail page has its own event navigation and does not show the shared refresh bar.