Unable to disable TRACE level logging for org.openhab.binding.ipcamera

I enabled log:set TRACE org.openhab.binding.ipcamera on the Openhab console to debug some issues I have with ipcamera binding. After 5-10 minutes, I set the logging level back to INFO log:set INFO org.openhab.binding.ipcamera. The TRACE messages are gone but I’m still getting trace logging for ipcamera state changes. I verified the logging level is set to INFO. Any suggestions?

2023-03-10 08:18:04.471 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SecCamFront_Last_Event_Data' changed from <EventNotificationAlert version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
<eventDescription>fielddetection alarm</eventDescription>

Logger                                             │ Level
ROOT                                               │ WARN
javax.jmdns                                        │ ERROR
javax.mail                                         │ ERROR
openhab.event                                      │ INFO
openhab.event.AddonEvent                           │ ERROR
openhab.event.ChannelDescriptionChangedEvent       │ ERROR
openhab.event.InboxUpdatedEvent                    │ ERROR
openhab.event.ItemAddedEvent                       │ ERROR
openhab.event.ItemChannelLinkAddedEvent            │ ERROR
openhab.event.ItemChannelLinkRemovedEvent          │ ERROR
openhab.event.ItemRemovedEvent                     │ ERROR
openhab.event.ItemStateEvent                       │ ERROR
openhab.event.RuleAddedEvent                       │ ERROR
openhab.event.RuleRemovedEvent                     │ ERROR
openhab.event.RuleStatusInfoEvent                  │ ERROR
openhab.event.StartlevelEvent                      │ ERROR
openhab.event.ThingAddedEvent                      │ ERROR
openhab.event.ThingRemovedEvent                    │ ERROR
openhab.event.ThingStatusInfoEvent                 │ ERROR
openhab.event.ThingUpdatedEvent                    │ ERROR
org.apache.cxf.jaxrs.sse.SseEventSinkImpl          │ ERROR
org.apache.karaf.jaas.modules.audit                │ INFO
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.ssh.SshUtils                │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.apache.sshd                                    │ ERROR
org.eclipse.lsp4j                                  │ OFF
org.jupnp                                          │ ERROR
org.openhab                                        │ INFO
org.openhab.binding.ipcamera                       │ ERROR
org.openhab.binding.wemo                           │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
su.litvak.chromecast.api.v2.Channel                │ ERROR

That is the event.log output which is DIFFERENT to the openhab.log file.

If you do not want the state changes going into the event.log you can:

  1. turn off event logging fully which is what I do as I use the developer sidebar to watch the events when I need to.

log:set WARN smarthome.event
2. Filter out the stuff you don’t want from going to the event.log you can filter just certain items or messages if you want to.
3. If your using frontail to watch the logs, you can change the config of frontail itself so you only watch the openhab.log file and to not include the event.log output.

Thanks. In the console, I set ItemStateChangedEvent to ERROR in the console to filter out those XML response payloads in frontail. However, it also filtered out the pool temperature changes. The ipcamera event messages weren’t being captured in the event logs before enabling the log:set TRACE org.openhab.binding.ipcamera so I wanted to understand what that command changed.

Eventually, I’ll insert a regex expression in log4j2.xml file to filter out only the ipcamera messages.

It does not change the state changes and does not touch the logging of the event bus. You can not pick and choose what gets logged from the event bus, you can only filter it or turn it off for every thing. As mentioned if you turn the log off completely you can still use the developers sidebar with filtering ability to see what is needed, I find this the way I like to work.