Question 1

What's the difference between an event and an incident?

Accepted Answer

Events are the raw signal — individual occurrences as they happen. Incidents are confirmed patterns that meet the threshold for an actual alert. Events are what feed into deciding whether something becomes an incident.

Question 2

Will I get overwhelmed with noise?

Accepted Answer

The event feed is built for browsing and pattern-spotting, not for individual alerts on every event — that's what the incident system is for.

Question 3

Can I filter by event type?

Accepted Answer

Yes — events can be filtered by type, page, and time range to spot patterns quickly.

Question 4

How long is event history kept?

Accepted Answer

Event data is retained long enough to correlate a current pattern against recent changes like a deploy or plugin update, which covers the most common real-world use case of investigating a regression shortly after it appears.

Question 5

Can I see which specific page or browser an error is happening on?

Accepted Answer

Yes — JavaScript errors are tracked with the specific page and context they occurred in, which is what makes it possible to narrow down a fix instead of just knowing 'an error happened somewhere.'

Question 6

Should I check the event feed even if nothing seems wrong?

Accepted Answer

It's most useful as a habit right after any change to a client site — checking for new error patterns immediately after a deploy catches regressions while they're still small, rather than waiting for them to become visible complaints.

Common questions

Ready to see it in action?