Creating effective alert descriptions is essential for clarity, quick understanding, and proper response. Using prompt patterns helps standardize and streamline the generation of alert descriptions across different scenarios. Below are various prompt patterns to guide the creation of alert descriptions, adaptable for systems like monitoring tools, security alerts, incident reports, and more.
1. Basic Incident Alert Pattern
Pattern:
[Alert Type]: [Component/Service] is experiencing [Issue]. Current status: [Status]. Immediate action required: [Action].
Example:
CPU Usage Alert: Server-12 is experiencing high CPU utilization. Current status: 95% usage. Immediate action required: Investigate running processes.
2. Threshold Breach Alert Pattern
Pattern:
[Metric] has crossed the threshold of [Threshold Value] on [Component]. Current value: [Current Value]. Impact: [Impact Description].
Example:
Memory usage has crossed the threshold of 80% on Database Server. Current value: 92%. Impact: Potential slow query performance.
3. Security Alert Pattern
Pattern:
[Security Event]: Detected [Event Type] on [Asset]. Source IP: [IP Address]. Severity: [Level]. Recommended action: [Action].
Example:
Intrusion Detection Alert: Detected multiple failed login attempts on Web Server. Source IP: 192.168.1.45. Severity: High. Recommended action: Block IP and review logs.
4. Performance Degradation Alert Pattern
Pattern:
Performance degradation detected on [Service/Component]. Metric affected: [Metric Name]. Degradation level: [Level]. Possible cause: [Cause].
Example:
Performance degradation detected on API Gateway. Metric affected: Response Time. Degradation level: Moderate. Possible cause: Increased request load.
5. Availability Alert Pattern
Pattern:
[Service/Component] is currently [Availability Status]. Detected at [Time]. Duration: [Duration]. Impact: [Impact].
Example:
Payment Gateway is currently unreachable. Detected at 14:23 UTC. Duration: 5 minutes. Impact: Transactions are failing.
6. Configuration Change Alert Pattern
Pattern:
Configuration change detected on [Component]. Changed parameter: [Parameter Name]. Previous value: [Old Value]. New value: [New Value]. Changed by: [User/Process].
Example:
Configuration change detected on Firewall. Changed parameter: Allowed Ports. Previous value: 80, 443. New value: 80, 443, 22. Changed by: AdminUser.
7. Log Anomaly Alert Pattern
Pattern:
Anomaly detected in logs of [Component]. Type: [Anomaly Type]. First detected: [Time]. Frequency: [Count/Timeframe].
Example:
Anomaly detected in logs of App Server. Type: Repeated error code 500. First detected: 10:00 AM. Frequency: 50 errors in 10 minutes.
8. Resource Exhaustion Alert Pattern
Pattern:
Resource exhaustion detected on [Resource] in [Component]. Current usage: [Value] of [Total]. Action recommended: [Action].
Example:
Disk space exhaustion detected on /var partition in Server-7. Current usage: 95% of total. Action recommended: Clean up unused files.
9. Scheduled Maintenance Alert Pattern
Pattern:
Scheduled maintenance for [Service/Component] from [Start Time] to [End Time]. Expected impact: [Impact Description].
Example:
Scheduled maintenance for Database Server from 22:00 to 23:00 UTC. Expected impact: Temporary downtime.
10. Recovery/Resolved Alert Pattern
Pattern:
[Alert Type] resolved on [Component]. Issue: [Issue Description]. Resolution time: [Time].
Example:
CPU Usage Alert resolved on Server-12. Issue: High CPU utilization normalized. Resolution time: 15:45 UTC.
These prompt patterns can be tailored to fit specific monitoring tools, alerting platforms, or operational needs. By keeping the structure consistent, alerts become easier to parse, act upon, and audit.
If you want, I can also create sample alert descriptions based on a specific domain or tool.
Leave a Reply