Skip to content

Conversation

@rayluo
Copy link
Contributor

@rayluo rayluo commented Mar 18, 2021

This PR will close #137 and also close #175

Implement Telemetry's app-wide state

Test cases for telemetry id on most public methods

Test telemetry buffer for offline states
@rayluo
Copy link
Contributor Author

rayluo commented Mar 19, 2021

@sangonzal FYI, this PR contains some test cases that demonstrate the actual outcome on the wire, such as 4|84,4|, 4|84,2|, ..., and 4|1|||, 4|1|622,id_1,622,id_2|error_1,error_2|, ..., etc.. Let me know if you find anything that does not feel right. :-)

By the way, have you seen any MSAL utilize that "platform-specific telemetry", i.e. appending more info at the end of the strings above? Pondering to add some platform-specific content here, wondering whether some telemetry consuming scripts would break because of that... UPDATE: Talked with Santiago during e-standup. Platform-specific values are indeed used by some other MSALs too.

@rayluo rayluo merged commit 5ccf410 into dev Mar 29, 2021
self._client_capabilities, claims_challenge)),
nonce=nonce,
**kwargs))
telemetry_context.update_telemetry(resposne)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A typo sneaked in. It will be fixed in PR #345

This was referenced Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Support Telemetry v2 protocol Server Side Telemetry

2 participants