Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

metrics: check performance of trace collector #262

Open
Arqu opened this issue May 24, 2022 · 1 comment
Open

metrics: check performance of trace collector #262

Arqu opened this issue May 24, 2022 · 1 comment

Comments

@Arqu
Copy link
Collaborator

Arqu commented May 24, 2022

We're starting to see OpenTelemetry trace error occurred. cannot send span to the batch span processor because the channel is full which is usually the result of performance limitations on the collector side.

@Arqu Arqu assigned Arqu and unassigned Arqu May 24, 2022
@Arqu
Copy link
Collaborator Author

Arqu commented Jun 1, 2022

This is one we're going to punt. The performance of the pipe itself should be fine for now and once we want to scale up, we should move to a more mature setup.
The reason this was popping up is that we hammered requests programmatically, our batching is minimal, the DB behind it fell over a couple times.

@dignifiedquire dignifiedquire transferred this issue from n0-computer/iroh Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant