Skip to content

Support improvements week 12#587

Closed
manototh wants to merge 3 commits intomainfrom
support/improvements-2026-03-16
Closed

Support improvements week 12#587
manototh wants to merge 3 commits intomainfrom
support/improvements-2026-03-16

Conversation

@manototh
Copy link
Copy Markdown
Collaborator

No description provided.

The monitor examples page lacked guidance on how to create an alert that
fires only when a metric stays above a threshold for a sustained period,
rather than triggering on a brief spike. Support received a question from
a user who wanted to alert when a metric remained above a threshold for
30 minutes continuously.

The solution is to use min() as the aggregation in the threshold monitor
query and set the range to the desired sustained duration. Because min()
returns the lowest value in the window, the result only exceeds the
threshold if every data point in the window was above the threshold.

Related support ticket:
- https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01KKCMZH3WXQEN91GSG24ZG89E/

Made-with: Cursor
Users receiving a "No activity detected by monitor" notification were
confused about what it meant and whether there was a bug in their setup.
The previous description of the Alert on no data setting did not explain
what the notification message would say, nor did it mention a common use
case for this feature.

Updated the description to include the exact notification message text
and a concrete example of when to use this option (detecting when a
data source stops sending events, e.g. an agent going offline).

Related support ticket:
- https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01KJGD96179A445SH8TTE8CM3S/

Made-with: Cursor
New users iterating quickly on their event schema during prototyping
were confused when they hit the once-per-day vacuum limit and had no
documented path forward. The vacuum fields section mentioned the limit
but gave no practical guidance on what to do when it blocks progress.

Added a list of alternatives: using a dedicated development dataset,
deleting and recreating the dataset, and trimming before vacuuming.

Related support ticket:
- https://app.plain.com/workspace/w_01HA1Z15QQY1X6QR29KFMBMYTH/thread/th_01KKBV0YBPA8KB1REX75Y9SZ4M/

Made-with: Cursor
@manototh manototh marked this pull request as draft March 16, 2026 09:25
@manototh manototh self-assigned this Mar 16, 2026
@manototh manototh closed this Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant