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

Create common code for HTTP receivers and exporters #505

Closed
pjanotti opened this issue Jan 16, 2020 · 1 comment
Closed

Create common code for HTTP receivers and exporters #505

pjanotti opened this issue Jan 16, 2020 · 1 comment

Comments

@pjanotti
Copy link
Contributor

Currently there are receivers and exporters, in the core and contrib repo, that are just variations of data formats sent/received over HTTP (eg.: Zipkin, SignalFx, collectd, etc). This creates inconsistencies between very similar components. We should design HTTP receivers and exporters that can be extended to support different formats, handle requests and responses as needed but have a consistent core set of configuration options and observability. This will simplify configurations and will make easier to understand issues with these components.
@pjanotti pjanotti mentioned this issue Jan 16, 2020
Merged
@bogdandrutu
Copy link
Member

This is almost done with the new helpers and the new configs.

MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this issue Nov 11, 2021
@MikeGoldsmith @jmacd @rghetia
Update README with import instructions and how to build / test (open-…
2ccddfe 
…telemetry#505)

* update README with import instructions and how to build / test

* fix typo

* remove building the code section from README.md

* add clone instructions to CONTRIBUTING.md

Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
Co-authored-by: Rahul Patel <rahulpa@google.com>
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this issue Apr 27, 2023
@jeffreyc-splunk @pjanotti
Release v0.29.0 (open-telemetry#505)
960ca93 
* Release v0.29.0

* fixes

* Change the map type in expandStringValues (open-telemetry#507)

* fix smartagent receiver/extension config

* Update CHANGELOG.md

Co-authored-by: Jay Camp <jcamp@splunk.com>
Co-authored-by: Paulo Janotti <pjanotti@splunk.com>
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this issue Jul 5, 2024
@bogdandrutu
Add cache for bazel to prove why bazel rocks (open-telemetry#505)
ff797b5
swiatekm pushed a commit to swiatekm/opentelemetry-collector that referenced this issue Oct 9, 2024
@tglanz
[demo] Feat/scheduling rules for jaeger (open-telemetry#505)
b7f9e2a 
* adjust schema so jaeger will have schedulingRules property

* create a template that renders yaml based on scheduling rules and default values

* modify _objects to use schedulingRules template

* add scheduling rules to jaeger

* fix whitespaces; generate examples

* Revert "modify _objects to use schedulingRules template"

This reverts commit c48b38920c5ea86c56e8c86490df58aa8416af3b.

* Revert "create a template that renders yaml based on scheduling rules and default values"

This reverts commit 58ba714b3dc5d2c2a9e56a5f9ee6f25e73676d4a.

* implement scheudlinRules templating for jaeger; generate examples

* bump patch
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
2 participants
@bogdandrutu @pjanotti