Consider a `Timestamp()` or similar Converter in OTTL

[bixu]

Component(s)

pkg/ottl

Is your feature request related to a problem? Please describe.

Consider a use-case where we want to normalize too-old timestamps on incoming telemetry. For debugging purposes, we might want to keep a copy of the original timestamp. Since the original timestamp data is in nanoseconds since the epoch, the raw value can be hard for humans to interpret.

Describe the solution you'd like

We could consider adding a Converter to translate the nanosecond epoch back to a human-readable timestamp. Timestamp(), for example.

Usage could be something like

Timestamp(target, format)

where target is something like time_unix_nano and format is a string templating the timestamp. A syntax similar to that of Time() would be preferable.

Describe alternatives you've considered

I attempted to use existing functions with the Transform processor, but the experience was...messy and would be difficult to debug:

- set(attributes["timestamp"], Format("%04d-%02d-%02d %02d:%02d", [Year(UnixNano(time_unix_nano)), Month(UnixNano(time_unix_nano)), Day(UnixNano(time_unix_nano)), Hour(UnixNano(time_unix_nano)), Minute(UnixNano(time_unix_nano))]))

Additional context

See CNCF Slack discussion here.

[github-actions]

Pinging code owners:

• pkg/ottl: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[TylerHelmuth]

We likely need a FormatTime function that uses https://pkg.go.dev/time#Time.Format, but instead of Go's time format string uses that same formatting as our Time function.

[odubajDT]

I would like to take this issue if possible

[odubajDT]

Just to clarify: The the first parameter in input should be an int64/string (Potentially IntLikeGetter) or time (TimeGetter)?

Thanks.

[TylerHelmuth]

A time.