Fixed Timestamp not being set for otel log signals

[Chris18230]

When using the otel logging, the log messages where displayed wrong in the Elastic Stack because the Timestamp was not set to the Log Signal. The Reason for this is that APM-Server is using the Timestamp and not the ObservedTimestamp for displaying the Message. For this reason they where display in the year 1970 in Elastic Stack.

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[quarkus-bot]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[geoand]

Thanks for the contribution!

Please rebase the PR onto main so it does not include merge commits.

[gsmet]

git config --global pull.rebase true might be helpful

[gsmet]

I just rebased it with the GitHub UI.

[geoand]

Seems reasonable to me, but let's let @brunobat decide

[brunobat]

Actually, it needs to be current time.

[brunobat]

Please check comments above.

[brunobat]

Thanks!

[gsmet]

The history is problematic, I will fix it.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 3c19050.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[gsmet]

Thanks for the fix! It will be included in the next 3.16.