feat: add libp2p tracing metrics and server-timing headers #166 #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
feat: add libp2p tracing metrics and expose via server-timing headers
Description
This PR integrates libp2p tracing metrics into the project and exposes these metrics via server-timing headers. It addresses the need for improved observability and performance monitoring. The changes include:
Adding @libp2p/opentelemetry-metrics to dependencies.
Initializing tracing metrics in libp2p-defaults.ts and libp2p-defaults.browser.ts.
Creating a new server.ts file to handle HTTP requests and expose server-timing headers.
Fixes [https://github.com//issues/166]
Notes & open questions
Ensure that the new tracing metrics do not introduce significant overhead.
Verify that the server-timing headers are correctly exposed in all relevant responses.
Change checklist
I have performed a self-review of my own code
I have made corresponding changes to the documentation if necessary (this includes comments as well)
I have added tests that prove my fix is effective or that my feature works