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.

Sign up for GitHub

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

Jump to bottom

Support independent queued-retry per Exporter #55

Closed
pjanotti opened this issue Jun 25, 2019 · 3 comments
Closed

Support independent queued-retry per Exporter #55

pjanotti opened this issue Jun 25, 2019 · 3 comments

Comments

@pjanotti
Copy link
Contributor

We need to have such capability on configV2.
pjanotti referenced this issue in pjanotti/opentelemetry-service Jun 27, 2019
@songy23
README: Add more specification on the first message. (#55)
8897b9f 
* README: Add more specification on the first message.

* Update wording.

* Fix typos
pjanotti referenced this issue in pjanotti/opentelemetry-service Jun 27, 2019
Make perf testbed OS agnostic (#55)
68da5d0 
Leveraging GOOS to make the tests run seamless in multiple OSes. There will be separate work to establish different baselines for different platforms, this first change is just to make it runs without manual adaptations on multiple OSes.
pjanotti pushed a commit that referenced this issue Jun 27, 2019
Make perf testbed OS agnostic (#55) (#64)
0a643a7 
Leveraging GOOS to make the tests run seamless in multiple OSes. There will be separate work to establish different baselines for different platforms, this first change is just to make it runs without manual adaptations on multiple OSes.
@flands flands added this to the 0.1.0 milestone Jun 28, 2019
@bogdandrutu
Copy link
Member

bogdandrutu commented Jul 3, 2019 •
edited
Loading

hmm, why is that not possible via configuring the piepline accordingly?

Receivers -> MultiProcessor -> Queue1 -> Exporter1
                            -> Queue2 -> Exporter2

@tigrannajaryan tigrannajaryan removed this from the 0.1.0 milestone Jul 10, 2019
@tigrannajaryan
Copy link
Member

tigrannajaryan commented Jul 10, 2019 •
edited
Loading

This is already implemented unless I misunderstand something and you refer to some other capability.

All you need to do is list the same receiver in multiple pipelines.

See implementation: https://github.com/open-telemetry/opentelemetry-service/blob/34ca12fa6144be70d4892b8429141ac753e2e78a/cmd/occollector/app/builder/receivers_builder.go#L246-L274

@flands
Copy link
Contributor

flands commented Mar 5, 2020

This is supported -- closing.

@flands flands closed this as completed Mar 5, 2020
MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this issue Nov 11, 2021
@jmacd @rghetia
Restore the experimental/streaming SDK implementation (open-telemetry#55
b26d667 
)

* Fix streaming - part 1

* Eliminate span{} state

* Eliminate trace/ dir

* Avoid missing AddEvent helpers
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this issue Apr 27, 2023
@rmfitzpatrick
smartagentreceiver: monitor creation (open-telemetry#55)
52b356c
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this issue Jul 5, 2024
Add interfaces for exporter, processor and span data (open-telemetry#55)
9e2418b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@flands @bogdandrutu @tigrannajaryan @pjanotti