Skip to content
Uplinkr

Evaluate Alert Trigger Decisions

Command

Section titled “Command”
Terminal window
php artisan uplinkr:project:alert:decision

Description

Section titled “Description”

Decides whether an alert should be triggered for a project based on probe results and alert configuration. This command analyzes probe failures and slow responses to determine if notification thresholds have been met.

Options

Section titled “Options”
OptionTypeRequiredDescription
--projectstringNoName of the project to check for alerts (if omitted, checks all projects)

Usage Examples

Section titled “Usage Examples”

Check alerts for a specific project

Section titled “Check alerts for a specific project”
Terminal window
php artisan uplinkr:project:alert:decision --project=my-project

Check alerts for all projects

Section titled “Check alerts for all projects”
Terminal window
php artisan uplinkr:project:alert:decision

Output Format

Section titled “Output Format”

The command displays alert decisions with details:

Found 2 alert decision(s) for project: my-project
my-project | https://example.com | Too many failures | Count: 5
my-project | https://api.example.com | Too many slow responses | Count: 3

Each line shows:

  • Project name (magenta)
  • Probe URL (cyan)
  • Reason for alert (yellow)
  • Failure/slow response count (red)

Behavior

Section titled “Behavior”
  • Analyzes probe results against configured alert thresholds
  • Checks for:
    • Consecutive failures exceeding trigger_after_failures
    • Slow responses exceeding trigger_after_slow
  • Considers cooldown periods to prevent alert spam
  • Logs results to the application log
  • Sends notifications grouped by project and alert configuration

Return Codes

Section titled “Return Codes”
  • 0 (SUCCESS): Command completed successfully (regardless of whether alerts were found)