How is TransmitProfile's timer array used?

[theta3]

Is your question about how to consume a C++ library? No

Is your question about specific 1DS SDK APIs or Features? Yes

This documentation states that the timer array has 3 values for EventLatency_Normal, EventLatency_CostDeferred, and EventLatency_RealTime. However, looking at the code

cpp_client_telemetry/lib/tpm/TransmitProfiles.cpp

Line 459 in 41840c3

void TransmitProfiles::getTimers(TimerArray& out) {

, I only see timers[0] and timers[2] used.

Could you please confirm what's the right logic and settings here?

[lalitb]

Yes only first and third timer values are used from the rule, and it is documented here too - https://github.com/microsoft/cpp_client_telemetry/blob/main/docs/custom-transmit-profile.md#timers

Each rule must include a timers array. The timers array should contain three values. The first value controls upload of EventLatency_Normal and EventLatency_CostDeferred events. The second value is not used and is retained for backwards compatibility. The third value controls and sets the cadence for EventLatency_RealTime events.

[theta3]

Oh that's right. I missed that middle sentence for some reason. I believe that back in the old SDK, there were also 3 timer values for EventPriority.LOW, NORMAL, and HIGH. When converting to this SDK, do we just use the same array values? It appears that the old SDK's second values should be moved to the first place in the new SDK?

I also see that here

cpp_client_telemetry/lib/tpm/TransmitProfiles.cpp

Line 377 in 41840c3

{ NetworkCost::NetworkCost_Metered, PowerSource::PowerSource_Battery, {-1, 24, 12} },

, 2nd and 1st values are different for default profile. But the documentation says 1st and 2nd values should be the same. Could you please clarify?