Workflow: Create an Alert

Alerts are most useful when they represent a specific operational question.

1. Define the objective

Examples:

• notify me about high-importance events for COIN;
• notify me when a monitored wallet produces a significant event;
• notify me about high-confidence events in a sector;
• notify me when global event sentiment crosses a chosen threshold.

2. Select the scope

Choose ticker, sector, wallet, or global. Enter the canonical scope key when required.

Prefer a specific scope unless the objective is genuinely global.

3. Select the metric

• Importance: attention priority.
• Confidence: evidence strength.
• Sentiment: textual direction.

Do not use confidence as a substitute for importance. A highly reliable minor event can have high confidence and low importance.

4. Select operator and threshold

Use the comparison that matches the objective. Review historical events or current page values before choosing a threshold.

5. Set a cooldown

A cluster can generate several matching events. Use a cooldown to avoid receiving the same development repeatedly.

6. Test the rule

Use the test action when available. Confirm that the summary, scope, and condition are correct.

7. Review delivery history

Inspect delivered, acknowledged, pending, or failed entries. A failed delivery is not evidence that no matching event occurred.

8. Tune

• too many alerts: narrow scope, raise threshold, or increase cooldown;
• missed material events: inspect their scores and source gates before lowering thresholds;
• repeated alerts for one situation: use cluster-aware monitoring or a longer cooldown.

Alerts should improve response time without replacing investigation.