Why some log category ID's are missing
Last modified on 23 May, 2022. Revision 2
Why are some log category ID's missing? As an example we have category 1, 2, 3 and 5. Why is number 4 missing?
| Up to date for | cOS Core 14.00.04 |
| Supported since | cOS Core 9.xx |
| Status | OK |
| Author | Peter Nilsson |
Missing log category ID
If we go to the log receiver and look at the list of log exception category list we see that some of the category ID’s seem to be skipped.
In the above picture, category ID #4 is missing.
Reason
The reason for this is basically changes in the code. The firewall is constantly updated/changed and sometimes some features/functions are added/removed or even merged with other categories. That is the main reason why there are gaps in the ID sequence as we also do not want to re-use old/existing category ID’s.
Related articles
HA: disallowed_on_sync_iface log events with rule=HA_RestrictSyncIf for Reverse ARP, RARP, and IGMP
8 Sep, 2020 vmware log ha rarp arp core
8 Sep, 2020 vmware log ha rarp arp core
Problems getting the Log Receiver / ILA to function properly
6 Apr, 2021 incontrol ila logreceiver
6 Apr, 2021 incontrol ila logreceiver
The meaning of the "Default_Access_Rule" log entry
25 Jan, 2021 brokenlink core arp log routing
25 Jan, 2021 brokenlink core arp log routing
How to optimize InControl Log File storage
17 Feb, 2021 incontrol log
17 Feb, 2021 incontrol log
Erroneous bandwidth output when making Log Analyzer queries with set time interval
5 Feb, 2021 incontrol log
5 Feb, 2021 incontrol log