Open ChrsMark opened 3 months ago
Pinging code owners:
pkg/stanza: @djaglowski
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Since https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33946 was merged with the feature gate, let's keep this issue open to track the graduation of this feature gate. I will take care of it.
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 @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
pkg/stanza
Is your feature request related to a problem? Please describe.
This issue keeps track of what was suggested at https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33353#discussion_r1626018076.
At the moment when the
container
parser parses the logs, it parses the time field moving the result to theTimestamp
. However the originaltime
field is preserved in theAttributes
. Example:Describe the solution you'd like
As mentioned at https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33353#discussion_r1626018076, it be would reasonable to remove the original field once its parsed.
One thing to consider here is the possibility of this field being used by some users today. This could happen for users that use the existing Helm preset. Since the
container
parser will be a replacement for this preset we need to take this into account. Maybe we can do this removal through a setting/feature-flag to not aggressively break any users that might use the original time field.Describe alternatives you've considered
No response
Additional context
No response