Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an optional telemetry component #6

Open
arthuraraujo-msft opened this issue Jan 9, 2024 · 0 comments
Open

Add an optional telemetry component #6

arthuraraujo-msft opened this issue Jan 9, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@arthuraraujo-msft
Copy link
Contributor

Add an optional telemetry component to the library.
One idea is to allow users to set a telemetry callback class that implements an interface. This interface will be invoked with the telemetry data at certain points of the flow, and the user will handle the telemetry appropriately.
We can also provide an example implementation using some kind of library.

The interface could be something like:

class TelemetryInterface
{
   virtual void HTTPRequestSucceeded(const std::string& timeStamp, const std::string& correlationVector, const std::string& url) = 0;
   virtual void HTTPRequestFailed(const std::string& timeStamp, const std::string& correlationVector, const std::string& url) = 0;
   virtual void UnexpectedError(const std::string& message) = 0;
};
@arthuraraujo-msft arthuraraujo-msft added the enhancement New feature or request label Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant