Skip to content
Laritor Documentation

Live Dashboards

Laritor dashboards can be configured for live monitoring displays using URL query parameters. This is useful for office monitors, ops rooms, or any always-on screen where the dashboard should keep itself up to date without manual interaction.

Auto refresh with refresh

Section titled “Auto refresh with refresh”

On any dashboard page, add the refresh query parameter to control how often the dashboard automatically refreshes.

The refresh parameter accepts a number of seconds:

  • Minimum value: 10
  • Example: ?refresh=30

This example refreshes the dashboard every 30 seconds:

https://your-laritor-dashboard-url?refresh=30

If a value lower than 10 is provided, dashboard will not auto refresh.

Tip: For wall displays, 30 to 60 seconds is usually a good balance between freshness and unnecessary reloads.

Default timeline with timeline

Section titled “Default timeline with timeline”

By default, dashboards open in a 24h view.

You can override the default timeline by adding the timeline query parameter to the dashboard URL.

Example:

https://your-laritor-dashboard-url?timeline=1h

This opens the dashboard with a 1 hour time range selected by default.

Accepted values:

  • 5m for the last 5 minutes
  • 15m for the last 15 minutes
  • 30m for the last 30 minutes
  • 1h for the last 1 hour
  • 3h for the last 3 hours
  • 6h for the last 6 hours
  • 12h for the last 12 hours
  • 24h for the last 24 hours
  • 3d for the last 3 days
  • 7d for the last 7 days
  • 14d for the last 14 days
  • 30d for the last 30 days

Combining refresh and timeline

Section titled “Combining refresh and timeline”

You can use both parameters together for a live operations view.

Example:

https://your-laritor-dashboard-url?refresh=30&timeline=1h

This configuration:

  • Refreshes the dashboard every 30 seconds
  • Opens the dashboard in the 1 hour view
Section titled “Recommended use cases”
  • NOC or operations wallboards
  • Office TV dashboards
  • Incident monitoring screens
  • Team-specific dashboards for queues, requests, or infrastructure health

For example, a support or ops team may want a dashboard that refreshes every 30 seconds with a 1h or 3h timeline so current spikes and failures stay visible throughout the day.