Add factories and component types to support logs data type #959
Conversation
This file contains hidden or 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
tigrannajaryan
requested review from
bogdandrutu,
dmitryax,
flands,
owais,
pjanotti,
rghetia and
songy23
as code owners
tigrannajaryan
force-pushed
the
feature/tigran/log-datatype
branch
from
89e48d6 to
efe4df6
Compare
Codecov Report
@@ Coverage Diff @@
## master #959 +/- ##
==========================================
- Coverage 85.68% 85.45% -0.23%
==========================================
Files 184 185 +1
Lines 13061 13181 +120
==========================================
+ Hits 11191 11264 +73
- Misses 1419 1461 +42
- Partials 451 456 +5
Continue to review full report at Codecov.
|
tigrannajaryan
force-pushed
the
feature/tigran/log-datatype
branch
2 times, most recently
from
ef5cf19 to
2504e50
Compare
tigrannajaryan
changed the title
bogdandrutu
approved these changes
May 13, 2020
We are planning on experimenting with logs data type in the Collector. This commit introduces factories and components types for logs and implements pipeline building for logs. The data.Log struct is for now empty. We need to wait for OTLP protocol to define the log data format and we will use it in data.Log. data.Log is in internal package since logs support is experimental and is not intended for public usage yet. Resolves open-telemetry#957
tigrannajaryan
force-pushed
the
feature/tigran/log-datatype
branch
from
2504e50 to
5d21d46
Compare
dmitryax
approved these changes
May 13, 2020
wyTrivail
pushed a commit
to mxiamxia/opentelemetry-collector
that referenced
this pull request
Jul 13, 2020
…emetry#959) We are planning on experimenting with logs data type in the Collector. This commit introduces factories and components types for logs and implements pipeline building for logs. The data.Log struct is for now empty. We need to wait for OTLP protocol to define the log data format and we will use it in data.Log. data.Log is in internal package since logs support is experimental and is not intended for public usage yet. Resolves open-telemetry#957
hughesjj
pushed a commit
to hughesjj/opentelemetry-collector
that referenced
this pull request
Apr 27, 2023
Troels51
pushed a commit
to Troels51/opentelemetry-collector
that referenced
this pull request
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We are planning on experimenting with logs data type in the Collector.
This commit introduces factories and components types for logs and
implements pipeline building for logs.
The data.Log struct is for now empty. We need to wait for OTLP protocol
to define the log data format and we will use it in data.Log.
data.Log is in internal package since logs support is experimental
and is not intended for public usage.
Resolves #957