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

Support Datadog tracing #90

Closed
Kroisse opened this issue Dec 2, 2024 · 0 comments
Closed

Support Datadog tracing #90

Kroisse opened this issue Dec 2, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Kroisse
Copy link
Contributor

Kroisse commented Dec 2, 2024

There may be cases where server applications communicate with each other via TGrid while using dd-trace for Datadog APM, or where web applications in browsers use Datadog RUM while communicating with servers through TGrid.

In typical HTTP communication, Datadog libraries like dd-trace either polyfill major libraries, or HTTP framework supports Datadog to enable service-to-service tracing. However, it seems that TGrid does not inherently support this functionality. Therefore, enabling Datadog tracing for TGrid could help users already using Datadog consider TGrid as a viable option.

@samchon samchon self-assigned this Dec 2, 2024
@samchon samchon added enhancement New feature or request good first issue Good for newcomers labels Dec 2, 2024
@samchon samchon closed this as completed in ff34b03 Dec 2, 2024
samchon added a commit that referenced this issue Dec 2, 2024
Close #90: add `Communicator.on()` message with event types.
@github-project-automation github-project-automation bot moved this from To do to Done in TGrid v1.0 Update Dec 2, 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 good first issue Good for newcomers
Projects
Status: Done
Development

No branches or pull requests

2 participants