byrsapty
510ca37e48
- Two flood-detection alerts (per-source message volume, calibrated live against real traffic) grouped by gl2_remote_ip - Session correlation: accelppp_interface fallback tagging plus radius_session_id/calling_station_id/radius_username extraction, so a subscriber's full session lifecycle is searchable by one key - Replace the single combined dashboard with three focused ones (Overview & Alerts, Network Equipment, Servers & Sessions) - Propagate GRAYLOG_ROOT_TIMEZONE and IP-in-alerts fixes into the reusable install script and templates - Add a Forgejo Actions workflow (manual trigger) that re-runs install-graylog.sh on a self-hosted runner living in the container, automating the deploy step this project has done by hand all along Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
21 lines
776 B
JSON
21 lines
776 B
JSON
{
|
|
"title": "Discord - Critical Alerts",
|
|
"description": "Discord webhook via Slack-compatible endpoint",
|
|
"config": {
|
|
"type": "slack-notification-v1",
|
|
"color": "#FF0000",
|
|
"webhook_url": "__DISCORD_WEBHOOK_URL_SLACK__",
|
|
"channel": "#alerts",
|
|
"custom_message": "*${event_definition_title}*\n${event_definition_description}\n${event.message}\n${if backlog}${foreach backlog message}• `${message.source}` (IP: ${message.fields.gl2_remote_ip}): ${message.message}\n${end}${end}",
|
|
"user_name": "Graylog",
|
|
"notify_channel": false,
|
|
"notify_here": false,
|
|
"link_names": false,
|
|
"icon_url": "",
|
|
"icon_emoji": "",
|
|
"include_title": true,
|
|
"include_event_procedure": false,
|
|
"time_zone": "Europe/Kyiv",
|
|
"backlog_size": 5
|
|
}
|
|
}
|