Simulate alerts

Route: /dash — Simulate button (admin only)

Simulate sends test alerts into the system using predefined templates or custom JSON. Use it for demos, filter validation, and workflow testing without waiting for real integrations.

See also: Overview · Alert sources

Task	Section
Open the dialog	Simulate an alert
Use templates	Templates
Send custom JSON	Custom JSON

Admin only

The Simulate button appears only for admin users. If you do not see it, contact your administrator.

Simulate an alert

1. On the dashboard (/dash), click Simulate in the top toolbar (next to Refresh).
2. In Simulate Alert, choose a template from the dropdown.
3. Review the generated JSON (or edit custom JSON).
4. Click Send Alert.
5. Click Refresh if the new alert does not appear immediately in the active view tab.

Successful submission shows a confirmation message. The alert is ingested like a normal alert (subject to views and filters).

Templates

Built-in templates generate realistic sample payloads:

Template	Scenario
HTTP Error	Web server HTTP status errors
High CPU Usage	Infrastructure CPU threshold
High Memory Usage	Memory pressure
Disk Space Low	Low disk on a mount point
Failed Login	Authentication failures
Network Latency Alert	High latency
Database Connection Failure	DB connectivity
Unauthorized Access Attempt	Security access attempt
Application Error	Application exception
Custom JSON	Your own payload

Template previews show randomized values (severity, resource, attributes) each time you select a template.

Copy JSON

Click Copy JSON to copy the current payload to the clipboard — useful for documentation or API testing outside the UI.

Custom JSON

1. Select Custom JSON in the template dropdown.
2. Edit the textarea — must be valid JSON for a single alert object or an array of alerts.
3. Optional: click Save custom template to store the JSON in your browser for the next session.
4. Click Send Alert.

Invalid JSON shows an inline error and blocks submission.

Simulated alerts use sourceId alert-simulator by default in templates.

Best practices

1. Simulate in a non-production view when possible — avoid noise in operator dashboards.
2. Match severity and environment in custom JSON to test sidebar filters and TQL.
3. Save custom JSON for repeatable test cases your team runs often.
4. Delete test alerts after validation using bulk Delete if policy allows.