-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
collector processors generated for Log pipelines should not be async #4444
Labels
Comments
We would appreciate it if you could provide us with more info about this issue/pr! |
This was referenced Apr 9, 2024
raj-k-singh
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Sep 13, 2024
…gs pipelines (#386) contributes to SigNoz/signoz#5894 and SigNoz/signoz#4444
raj-k-singh
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Sep 19, 2024
Brings in copies of stanza pieces relevant to logs pipelines from opentelemetry-collector-config at processor/signozlogspipelineprocessor/stanza/ Bringing over pieces of stanza will give us the ability to modify anything and everything as needed to achieve our goals with logs pipelines Almost all of the files in this PR have been brought in as is with no/minimal modifications and have a comment stating the same in their 1st line contributes to SigNoz/signoz#5894 and SigNoz/signoz#4444
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logs pipelines in the UI get translated to logstransform processors right now.
logstransform processors are async and do their own internal batching. This makes the entire collector pipeline async - consumeLogs at the receiver returns before it is guaranteed that the exporter has finished exporting logs.
Having sync collector pipelines makes it simpler to provide persistence guarantees for logs collected by receivers.
The text was updated successfully, but these errors were encountered: