You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't have much visibility into why most of the offline/online messages don't have interface-used (or webpa-interfaced-used) messages. It could be that we just aren't getting that information from RDK but it's not 100 percent. Talaria is pulling that data from the convey header as it's supposed to. The easiest thing to do might be to print out the exact messages we are getting from RDK into a debug log on a canary.
As a side, it seems like all online/offline messages are translating webpa-interface-used -> /interface-used. The "webpa-interface-used" messages are most likely other event types such as firmware upgrade, operational, manageable, etc.. since they are pass-thru messages.
The text was updated successfully, but these errors were encountered:
We don't have much visibility into why most of the offline/online messages don't have interface-used (or webpa-interfaced-used) messages. It could be that we just aren't getting that information from RDK but it's not 100 percent. Talaria is pulling that data from the convey header as it's supposed to. The easiest thing to do might be to print out the exact messages we are getting from RDK into a debug log on a canary.
As a side, it seems like all online/offline messages are translating webpa-interface-used -> /interface-used. The "webpa-interface-used" messages are most likely other event types such as firmware upgrade, operational, manageable, etc.. since they are pass-thru messages.
The text was updated successfully, but these errors were encountered: