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

Where to find logs related to the InControl server, client, ILA or Log receiver
14 Dec, 2022 incontrol ida log
HA: disallowed_on_sync_iface log events with rule=HA_RestrictSyncIf for Reverse ARP, RARP, and IGMP
23 Aug, 2022 vmware log ha rarp arp core
Where to find logs to the OneConnect client for MacOS
27 Oct, 2022 oneconnect log
Problems getting the Log Receiver / ILA to function properly
6 Apr, 2021 incontrol ila logreceiver
The TCP Window Scale Log Event
15 Nov, 2022 tcp log core
Details about the WebUI memory log (memlog)
20 Jan, 2023 core log webui memlog
Automatically stop active PCAPdump or Logsnoop in the CLI
7 Dec, 2022 pcapdump log cli core logsnoop
The meaning of the Default_Access_Rule log entry
7 Nov, 2022 core arp log routing
How to optimize InControl Log File storage
17 Feb, 2021 incontrol log
Erroneous bandwidth output when making Log Analyzer queries with set time interval
5 Feb, 2021 incontrol log




Tagscoreloglogreceiver