byrsapty
b0e4095cae
8 new rules (vendor=a10) wired into Network Equipment Parsing: LSN TCP/Session/ICMP per-user quota exceeded (critical - real service impact, drops new connections for that subscriber), BGP-4-MAXPFX prefix-limit warning, and admin session open/close/timeout/auth-success (aXAPI and CLI both covered by one pattern each). Unlike the CSV-report-derived rules, these are built directly from real captured A10 log output the user provided, so confidence is higher - closer to the accel-ppp rules' provenance. Multi-entry LSN lines (several 'ip(count)' pairs in one quota-exceeded message) only have their first pair extracted into fields; the full list stays in the raw message. Not live-verified - the user is bringing the target system up themselves this time rather than through the test container used earlier in this branch of work.
5 lines
821 B
JSON
5 lines
821 B
JSON
{
|
|
"title": "a10_session_opened",
|
|
"description": "A10: admin session opened (covers both 'aXAPI session' and 'cli session' wording - same event, different access method). Built from real captured A10 syslog output.",
|
|
"source": "rule \"a10_session_opened\"\nwhen\n contains(to_string($message.message), \"session for user\") && contains(to_string($message.message), \"has been opened\")\nthen\n set_field(\"vendor\", \"a10\");\n set_field(\"event_type\", \"session_opened\");\n let m = regex(\"session for user \\\\\"(\\\\S+)\\\\\" from (\\\\S+) has been opened\\\\. Session ID assigned is (\\\\d+)\", to_string($message.message), [\"user\",\"src_ip\",\"session_id\"]);\n set_field(\"a10_user\", m[\"user\"]);\n set_field(\"src_ip\", m[\"src_ip\"]);\n set_field(\"a10_session_id\", m[\"session_id\"]);\nend"
|
|
}
|