History vs Trend Charts

TriggerDeck opens numeric charts from supported rows in Problem Details, Items, and chart-backed dashboard widgets. The same range logic applies across those entry points.

Short ranges show more detail

When you focus on recent activity, charts show more granular changes. This helps when you need to see spikes, quick drops, and recovery moments around an alert.

Typical examples:

• recent incident analysis
• validating whether a value just recovered
• comparing raw points around an alert

Long ranges show the bigger picture

For longer windows, charts are intentionally smoother. This keeps the view readable on mobile and helps you spot broader patterns without visual noise.

Typical examples:

• looking at longer uptime or saturation patterns
• checking whether a problem is isolated or recurring
• understanding whether a current alert sits inside a broader trend

Why this matters on iPhone

Mobile charts have tighter screen and performance constraints than desktop dashboards. Showing too much raw detail on every long range would slow navigation and make charts harder to read.

This behavior gives TriggerDeck two things at once:

• detail when recent precision matters
• cleaner long-range views when you mainly need trend direction

What operators should expect

Short and long ranges may not look identical for the same metric. That is expected. Long windows prioritize readability and trend shape, while short windows prioritize precision.

Troubleshooting chart differences

If a long-range chart looks smoother or less detailed than a short-range chart for the same item:

1. Confirm the selected time window.
2. Compare the same metric in both short and long ranges.
3. If values still look inconsistent, refresh the view and verify server time settings.