This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
Proposal: OTLP Exporters Support for Configurable Export Behavior #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends
Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends
jmacd
approved these changes
Aug 11, 2020
bogdandrutu
approved these changes
Aug 11, 2020
|
@huyan0 please fix markdown lint errors :) https://app.circleci.com/pipelines/github/open-telemetry/oteps/732/workflows/d88799f9-34eb-4763-ad4e-604ed3dd5197/jobs/927 |
And please remove the binary |
MrAlias
reviewed
Aug 11, 2020
|
Is this a subset of the features described in OTEP 126? https://github.com/open-telemetry/oteps/blob/master/text/metrics/0126-Configurable-Metric-Aggregations.md Or is this a requirement that OTLP exporters use the features in OTEP 126 and provide access via configuration? |
|
I think it is a mix of both. But most importantly it says that defaults should be cumulative |
|
@jkwatson I support the idea that the Views configuration should be able to set the export strategy for OTLP. I see the goal of this OTEP as simply stating that (1) it should be a configuration option, (2) it defaults to cumulative. I'd say that an API to configure this is the MVP, and that a more wholistic Views API should include this feature as a configuration. |
MrAlias
approved these changes
Aug 11, 2020
jkwatson
approved these changes
Aug 11, 2020
|
I have removed the extra binary files, thanks : -) |
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 23, 2024
…en-telemetry#131) * add otlp export otep * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * fix format to pass markdownlint * add sentence to highlight cumulative -> delta is also needed Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 23, 2024
…en-telemetry#131) * add otlp export otep * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * fix format to pass markdownlint * add sentence to highlight cumulative -> delta is also needed Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 30, 2024
…en-telemetry#131) * add otlp export otep * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * fix format to pass markdownlint * add sentence to highlight cumulative -> delta is also needed Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
carlosalberto
pushed a commit
to open-telemetry/opentelemetry-specification
that referenced
this pull request
Nov 8, 2024
…en-telemetry/oteps#131) * add otlp export otep * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * Make SDK OTLP exporters support configurable export behavior Based on discussions from the Metrics SIG meeting, configurable export behavior from the OTLP exporter is desired to support different mertic backends * fix format to pass markdownlint * add sentence to highlight cumulative -> delta is also needed Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This OTEP stems from discussions around spec #731 and partially resolves #725. The topic has been discussed at length in the Metrics SIG meeting, and the conclusion from those discussions is reflected here.
cc @huyan0 @alolita @jmacd @bogdandrutu