nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Pascal Hdz — Tue, 22 Jul 2025 10:58:45 GMT

Hello Ruslan,

Sorry for my misunderstanding, I can see now the problem that you are pointing. This is indeed an issue and we will need to follow up internally. Unfortunately, I can't offer you a hot fix for now but should be fix on the next NCS releases.

Pascal.

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

ragruslan — Thu, 17 Jul 2025 07:32:41 GMT

Hello Pascal,

Thanks for your message. But it seems we still don't understand each other. We talk about a possible issue in the code, not about the shadow and configuration. And it's important to carefully look at the code by the links I provided in the previous messages. There were questions about the code.. But no answers so far.

I've run the Multi Service sample and the behavior I see confirms the issue described in this ticket.

To reproduce the issue I made the following steps:

1. I modified the overlay_nrfcloud_logging.conf to disable all "periodic business logic". This is the diff:

@@ -28,3 +28,7 @@ CONFIG_LOG_BACKEND_NRF_CLOUD_OUTPUT_TEXT=y
 CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096
 CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=30000
 CONFIG_TEMP_ALERT_LIMIT=24
+
+CONFIG_LOCATION_TRACKING=n
+CONFIG_TEMP_TRACKING=n
+

2. Ran the sample for 15 mins. Got the following logs in nRF Cloud:

No actions - no logs. This is the expected behavior. Right?

3. I made one more modification in the overlay_nrfcloud_logging.conf. Set CONFIG_LOG_RUNTIME_FILTERING=y (as I've written above - this option breaks the log filtering). This is the diff:

@@ -11,7 +11,7 @@ CONFIG_NRF_CLOUD_LOG_INCLUDE_LEVEL_0=y
 
 # If enabled, log levels for each log source can be set per log backend, and
 # can be changed dynamically.
-CONFIG_LOG_RUNTIME_FILTERING=n
+CONFIG_LOG_RUNTIME_FILTERING=y
 
 CONFIG_LOG_BUFFER_SIZE=4096
 
@@ -28,3 +28,7 @@ CONFIG_LOG_BACKEND_NRF_CLOUD_OUTPUT_TEXT=y
 CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096
 CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=30000
 CONFIG_TEMP_ALERT_LIMIT=24
+
+CONFIG_LOCATION_TRACKING=n
+CONFIG_TEMP_TRACKING=n
+

4. Ran the sample for 15 mins. Got the following logs in nRF Cloud:

Still no actions - but much logs (and they never end). Is this the expected behavior? I believe - not. And I see the code in nrf_cloud_log_backend.c that should prevent this behavior. But it actually doesn't work (see our explanations in the previous messages).

Thanks,
-Ruslan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Pascal Hdz — Tue, 15 Jul 2025 14:16:23 GMT

Hello Alexey,

This is a feature that leverage Zephyr's Logging subsystem. nRF Cloud received the logging and displays it in the Logs Card. This is also available for binary logging for a smaller memory footprint.

The Logs card's UI allows you to select which is the desired level of logging you would like to visualize in the cards but this is not something that is being filtered in the front end neither in the back end of nRF Cloud. When you select the desired log level, this will be changed in AWS shadow and wait for the device to connect to nRF Cloud to catch this new desired value (which is considered a delta) and execute in the application the desired configuration changes. Once this is done, the device reports back the current state, this is then visualized on the left side of the options to select in the Logs card. If you pass your mouse on top of it, it will describe what I'm mentioning.

As you can see in the picture above, I remarked on blue the "reported" by the device and in orange the "desired".

If you look at the Multi Service sample, you will notice there are a few files that controls the Shadow control on the device. There are some specific for CoAP and MQTT. If your project lacks of shadow support and has nRF Cloud logging enabled, the device will send the log to nRF Cloud but you will not be able to control the device.

My recommendation would be to compile the Multi Service sample with the overlay_nrfcloud_logging.conf and see how this changes.

So you are aware, this feature is not responsive. It takes ~120 seconds to be able to visualize the change on the reported sections I mentioned before.

Pascal.

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Alexey Kos — Mon, 14 Jul 2025 13:11:38 GMT

Hi Pascal,
Thanks for your email. We (Ruslan) has found it ;)
- The question is not critical for our current project but we would like to clarify it anyway.
- It is not related to the cloud logging configuration/filtering/etc. It is related to the source code.
- We use the SDK code (including the nrf_cloud_log_backend.c file) in our project, so we looked at that source code and have this question.
- It is formulated in the original post in this thread. Pls have a look at it.
- Just to repeat it briefly:
-- There is some code to prevent an endless sending of log messages.
-- It uses filtering of logs from some sources. The filtered_modules array defines these sources.
-- But there seems an issue in the code - in the logs_backend_enable() function - logger_init() sets the mentioned filtering, but right after that log_backend_enable() resets it. So, the needed filtering does not work.
- Can you please review that source code and either confirm there is the issue, or explain how it works if the code is correct.
- We will try to reproduce the issue on practice, but will need to find time for that.
Thank you!
-Alexey

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Pascal Hdz — Fri, 11 Jul 2025 14:15:18 GMT

Hello Alexey,

I sent you an email early this week, let me know if this is still an issue.

Regards,

Pascal.

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Wed, 02 Jul 2025 10:26:19 GMT

Hi Alexey,

It is still not quite clear why you think there might be a bug. Is this issue reproducible?
In order to confirm that this is a bug, can you provide a minimal sample (or use one of existing NCS samples such as multi_service sample) which demonstrates this issue and additional description of what is expected to happen and what actually happens?

Best regards,
Dejan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Alexey Kos — Tue, 01 Jul 2025 20:33:10 GMT

Unfortunately, it does not answer our question ;(

Is there a bug tracking system where we can submit a bug?

And/or is there a way to discuss the question directly with developer(s)?

Regards,
-Alexey

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Tue, 01 Jul 2025 08:50:43 GMT

Hi Alexey,

[quote user="Alexey Kos"]Did your developers review this piece of code?
Can they confirm there is the issue or explain if there no issue?[/quote]

Our developers have tested nrf_cloud_multi_service sample and confirmed that this feature works in the sample as expected. You can look at relevant implementation in the nrf_cloud_multi_service sample.

Best regards,
Dejan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

Alexey Kos — Mon, 30 Jun 2025 15:15:26 GMT

Hi Dejan,

Ruslan is talking about a possible bug in the code - in the nrf_cloud_log_backend.c file.
And in my opinion, he well described the issue in the very first message in this thread.
Briefly:
- There is some code to prevent an endless sending of log messages.
- It uses filtering of logs from some sources. The filtered_modules array defines these sources.
- But there seems an issue in the code - in the logs_backend_enable() function - logger_init() sets the mentioned filtering, but right after that log_backend_enable() resets it. So, the needed filtering does not work.
Did your developers review this piece of code?
Can they confirm there is the issue or explain if there no issue?

Again, the question is about the code (nrf_cloud_log_backend.c and related files). Pls return to the first message in this thread.
The question is not about using/configuring the logging, configuration settings, etc.

Thanks,
-Alexey

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Mon, 30 Jun 2025 14:27:55 GMT

Hi Ruslan,

CONFIG_LOG_RUNTIME_FILTERING is used for fine run-time control of log levels for each logging source. You can get more information in configuration documentation.

[quote user=""]

# This option leads to sending endless messages like this "Sent lines:516, bytes:70952"

CONFIG_NRF_CLOUD_LOG_LOG_LEVEL_INF=y

[/quote]

Is it correct that this endless stream of messages is sent from device and observed on nRF Cloud? Do you see these messages in the Logs tab for your device in nRF Cloud?

Can you provide more information about your application?

Is it correct that you want to filter the messages that you can see on nRF Cloud?

Which logging settings in your device shadow are there on the nRF Cloud?

You could try to set log level on nRF Cloud (see using device logs in nRF Cloud) and that should change current shadow, but you also need to have some logic on the device side to update its state based on existing shadow when the device connects to nRF Cloud next time.

Best regards,
Dejan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

ragruslan — Mon, 30 Jun 2025 09:45:30 GMT

Hi Dejan,

There seems to be a misunderstanding...

Did you open the links I provided in my messages? Can you please explain what this array/list is for?

Regards,
Ruslan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Thu, 12 Jun 2025 11:12:22 GMT

Hi Ruslan,

I have discussed your reported issue with our developers.
We have checked internally that nRF Cloud Multi Service sample using CoAP does allow to filter the information. However, it is not very responsive (as it takes around 120 seconds to change the filter value). The filtering happens on the device through device shadow. The cloud sends the filter state to the device (c2d) and the device aligns the cloud logging to that. You need to look at how this is implemented in multi_service sample and implement it in your project.

Best regards,
Dejan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Tue, 10 Jun 2025 09:07:14 GMT

Hi Ruslan,

We are investigating this issue. I will get back to you with status update by the end of the week.

Best regards,
Dejan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

ragruslan — Thu, 05 Jun 2025 08:45:06 GMT

The root of the issue is not in the high log level (this is actually the default log level). Please, look a bit deeper: there is a list of log sources which must be filtered out - regardless of their log levels. But they are not filtered out if CONFIG_LOG_RUNTIME_FILTERING=y.

Regards,
Ruslan

RE: nRF Cloud Log backend doesn't filter unwanted messages generated as a side effect of sending other log messages

dejans — Mon, 02 Jun 2025 17:59:15 GMT

Hi,

You have set quite high level for log messages. You can refer to logging configuration. You can try to reduce the level of logging for messages that are sent to nRF Cloud using CONFIG_NRF_CLOUD_LOG_OUTPUT_LEVEL. You can read more about nRF Cloud Logging in the documentation.

Best regards,
Dejan

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian