OPTION_LOG_TRACE is not working on the Azure Sphere

Question

OPTION_LOG_TRACE is not working on the Azure Sphere

Hi,

I'm trying to debug the device connection to the IoTHub.
Found an OPTION_LOG_TRACE in iothub_client_options.h that I'm passing to IoTHubDeviceClient_LL_SetOption and Prov_Device_LL_SetOption right after handles creation. But I don't see any new logs after enabling those options. Is there any additional code or options need to be set for the project, to see the connection log trace?

AshokPeddakotla-MSFT 11,061 Reputation points

2022-08-23T06:45:01.013+00:00

@Dmytro Seliverstov Welcome to Microsoft Q&A forum!

Similar issue has been discussed here, I suggest you please go through the solution and let us know if you are still blocked.
Dmytro Seliverstov 41 Reputation points

2022-08-23T08:34:38.383+00:00
Thank you for the reply.

There is a broken link in that ticket, but I think you referring to this article and this constrained-devices.

So, according to "constrained devices" you are propossing to me to build Azure IoT C SDK for Azure Sphere with settled options to enable log trace, aren't you?

What is the point of adding not working (and that's why confusing) OPTION_LOG_TRACE into Azure Sphere SDK headers?
Dmytro Seliverstov 41 Reputation points

2022-09-13T11:20:56.273+00:00

Hi, still waiting for your help
SatishBoddu-MSFT 14,616 Reputation points

2022-09-15T03:53:47.103+00:00

Hi @Dmytro Seliverstov ,

Could you please let us know what is your device configuration, model and used SDK?

Is the device sample working fine on your side?

azure-sphere-samples

We are checking internally on this/
Dmytro Seliverstov 41 Reputation points

2022-09-15T08:55:54.637+00:00

Hi, @SatishBoddu-MSFT

I'm using Azure Sphere on q200 concentrator. Related info:
* Azure Sphere SDK 22.07.4.18989
* Azure Sphere OS version 22.07
* device is working fine
* Configuration:

AshokPeddakotla-MSFT 11,061 Reputation points

2022-08-23T06:45:01.013+00:00

@Dmytro Seliverstov Welcome to Microsoft Q&A forum!

Similar issue has been discussed here, I suggest you please go through the solution and let us know if you are still blocked.
Dmytro Seliverstov 41 Reputation points

2022-08-23T08:34:38.383+00:00

Thank you for the reply.

There is a broken link in that ticket, but I think you referring to this article and this constrained-devices.

So, according to "constrained devices" you are propossing to me to build Azure IoT C SDK for Azure Sphere with settled options to enable log trace, aren't you?

What is the point of adding not working (and that's why confusing) OPTION_LOG_TRACE into Azure Sphere SDK headers?
Dmytro Seliverstov 41 Reputation points

2022-09-13T11:20:56.273+00:00

Hi, still waiting for your help
SatishBoddu-MSFT 14,616 Reputation points

2022-09-15T03:53:47.103+00:00

Hi @Dmytro Seliverstov ,

Could you please let us know what is your device configuration, model and used SDK?

Is the device sample working fine on your side?

azure-sphere-samples

We are checking internally on this/
Dmytro Seliverstov 41 Reputation points

2022-09-15T08:55:54.637+00:00

Hi, @SatishBoddu-MSFT

I'm using Azure Sphere on q200 concentrator. Related info:
* Azure Sphere SDK 22.07.4.18989
* Azure Sphere OS version 22.07
* device is working fine
* Configuration:

Answer 1

Alistair Lowe 181 Microsoft Employee

Hello @Dmytro Seliverstov ,

Unfortunately, to reduce resource usage and ensure long-lasting API/ABI compliance, the IoT Hub C SDK embedded within the Azure Sphere OS is compiled with the flag NO_LOGGING set.
You will be able to see from mqtt_client_set_trace in mqtt_client.c (which is called as part of OPTION_LOG_TRACE) that this functionality is disabled when NO_LOGGING is set.

Many thanks

Dmytro Seliverstov 41 Reputation points

2022-09-29T07:41:51.757+00:00

Hi,

What is the point of adding not working (and that's why confusing) OPTION_LOG_TRACE into Azure Sphere SDK headers?
Alistair Lowe 181 Reputation points Microsoft Employee

2022-10-05T17:20:00.557+00:00

Hello @Dmytro Seliverstov ,

I have spoken within the team responsible for this library, the reason this option is still present is to reduce patch surface area, simplifying the process of keeping this library in-sync with the mainline release. We acknowledge that without visibility of the NO_LOGGING compile flag this is ambiguous and will explore whether there is anything we can do in a future release to lessen this ambiguity.

I hope that this answers your question.

Many thanks

OPTION_LOG_TRACE is not working on the Azure Sphere

0 additional answers

Activity