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
621 B
JSON
5 lines
621 B
JSON
{
|
|
"title": "a10_auth_success",
|
|
"description": "A10: local authentication succeeded (fires alongside a10_session_opened for the same login - kept separate since it's a distinct audit line). Built from real captured A10 syslog output.",
|
|
"source": "rule \"a10_auth_success\"\nwhen\n contains(to_string($message.message), \"Local authentication successful\")\nthen\n set_field(\"vendor\", \"a10\");\n set_field(\"event_type\", \"auth_success\");\n let m = regex(\"Local authentication successful \\\\(user: (\\\\S+)\\\\)\", to_string($message.message), [\"user\"]);\n set_field(\"a10_user\", m[\"user\"]);\nend"
|
|
}
|