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

Supporting single vs. multiple exporters per processor for Logs #417

Closed
kxyr opened this issue Dec 3, 2020 · 1 comment
Closed

Supporting single vs. multiple exporters per processor for Logs #417

kxyr opened this issue Dec 3, 2020 · 1 comment
Labels
priority:p2 Issues that are not blocking

Comments

@kxyr
Copy link
Contributor

kxyr commented Dec 3, 2020

I think the approach most are leaning towards for logs, following the traces implementation, is attaching only 1 exporter to a processor. However, another consideration is to support multiple exporters per processor.

Advantages of attaching multiple exporters to a processor:

  • Could reduce number of times batching is done

Disadvantages:

  • Could also increase the time it takes to complete the export to all destinations, since each batch export would only take as little of time as the slowest exporter takes to finish its export.

Unknown:

  • What would be the return status from the processor from ForceFlush() or Shutdown() not all the exporters succeed/fail at the same time?
  • Would user interact directly with processor or exporter to shutdown or forceflush a certainexporter?

Opening up this issue for discussion

cc @alolita @MarkSeufert

@kxyr kxyr changed the title Supporting Multiple Exporters per Processor for Logs Supporting single vs. multiple exporters per processor for Logs Dec 3, 2020
@lalitb lalitb added the priority:p2 Issues that are not blocking label Dec 16, 2020
@lalitb
Copy link
Member

lalitb commented Apr 19, 2021

There is a separate issue to support multiple span processors ( #664). No plan is to support multiple exporters per processor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:p2 Issues that are not blocking
Projects
None yet
Development

No branches or pull requests

2 participants