topic Re: Logging Trap in Network Security

Logging Trap

Tristan Apostol — Tue, 03 Jan 2023 06:07:59 GMT

Hi Guys,

Can i know if i use the Logging trap Debugging all the other severity are included? or can i use multiple severity?

Thank you.

Have a wonderful day ahead.

Re: Logging Trap

Mark Elsen — Tue, 03 Jan 2023 08:44:17 GMT

- Yes , all severity levels will be included (and or not possible to specify multiple severity levels)

Re: Logging Trap

Marius Gunnerud — Tue, 03 Jan 2023 09:34:55 GMT

All severities are included when debugging is enabled.

Re: Logging Trap

Tristan Apostol — Tue, 03 Jan 2023 10:53:17 GMT

Thank you guys for the answer 😊😊

Re: Logging Trap

Marius Gunnerud — Tue, 03 Jan 2023 10:56:42 GMT

Thanks you for the rating, please remember to also select a correct answer as this helps contributors in achieving badges and other recognition within the support forum. So please both rate and select correct answers 🙂

Re: Logging Trap

balaji.bandi — Tue, 03 Jan 2023 11:05:07 GMT

Logging trap Debugging all the other severity are included?

As others mentioned agreed with them and choosing the right option always is the best option. ( also make sure when you enable debugging message on console on high traffic will freeze the console access - that is the only draw back we see on console)

If you look at the below table 7 is debugging, so that covers everything what you need, but we debug logs are huge and we only run when there is an issue occationally, so choose the appropriate option required when you configuring syslog config.

0	Emergencies	System shutting down due to missing fan tray
1	Alerts	Temperature limit exceeded
2	Critical	Memory allocation failures
3	Errors	Interface Up/Down messages
4	Warnings	Configuration file written to server, via SNMP request
5	Notifications	Line protocol Up/Down
6	Information	Access-list violation logging
7	Debugging	Debug messages