-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
support dissect feature to convert plain text to structured data #11533
Comments
Hey @newly12 , what data you want to process with this? traces, metrics, logs or some attributes? |
@dmitryax in my use case, it's log line. |
@TylerHelmuth this is something that will be possible to do with transform processor, right? |
If we implement an in house processor that does dissect or something similar in a processor, a typical use case is that we want to parse the "log"(event) timestamp from a "dissected" field and set it as the log record's time, similar to what's currently in filelog receiver, the |
Hi @TylerHelmuth any comment on this? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
IDK how I missed this for so long but thanks Stale Bot for the last ditch effort haha I think this is definitely appropriate for the transformprocessor. There are some open issues for improving how OTTL/transformprocessor interact with time: #16067 and we just made a |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
Pinging code owners for pkg/ottl: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Is your feature request related to a problem? Please describe.
In elastic ecosystem, filebeat, logstash, elasticsearch all support dissect processor to convert plain text to structured data, which is pretty useful, given already exists filelogreceiver for log file ingestion, it seems to make sense to support this in otel collector as well.
Describe the solution you'd like
Support dissect processer.
Describe alternatives you've considered
Dissect operator in filelogreceiver
Additional context
The text was updated successfully, but these errors were encountered: