Invalid event timestamps

[vrutkovs]

Describe the bug

Event timestamps in Grafana are shown as 20292093d, which is uhm 53 centuries BCE (did proto-indoeuropeans created it? :) )

To Reproduce

Not sure, see screenshot

and trace

Trace-073310-2025-08-12 11_44_50.json

Version

victoria-traces-20250728-022931-tags-v0.1.0-0-g578722156

Logs

No response

Screenshots

No response

Used command-line flags

No response

Additional information

No response

[jiekun]

Hi. Sorry for the late reply, and thanks for reporting the issue. AFAIK @JayiceZ is investigating this issue and will provide update if he finds something.

[jiekun]

Hello. @vrutkovs I tried to reproduce it with otel demo but no luck. May I ask if you have any context how the original data looks like:

• How it looks like in VictoriaTraces? You can search for this span in VMUI (http://127.0.0.1:10428) by span_id:=xxxxxx.
• How it looks like in the ingest request? You can try the debug exporter in OTel Collector and it will log your data.

[vrutkovs]

Ah, I realized I used v0.1.0 image instead of latest. Let me reproduce that on latest code and come back to you with more information

[jiekun]

The v0.1.0 image is the latest one. I was just back from vacation and looking into this. Please let me know if you have more detail about this potential bug. Thank you!

[samrg472]

I've came across the same issue with Grafana. I'm using VictoriaTraces v0.1.0 and Grafana 12.1.1. The VMUI correctly displays the time converted to my local time zone and the raw _time field displayed is in UTC. Using an official Jaeger instance (with the OTel collector, if that makes any difference) also has the same problematic behavior in Grafana.

[jiekun]

Thank you @samrg472 for the feedback. If same issue was presented in Jaeger, I doubt it may related to Grafana visualization.
If you could provide the original data by debug exporter or in any other format, that would be great!

[JayiceZ]

I found from the uploaded trace.json that the timestamp of the Logs is nanosecond, which should be microseconds.

I checked the relevant code but found that the conversion isn't missed in VictoriaTraces

[samrg472]

Trace data: trace.json

My trace was created by exporting from my app directly to the Jaeger instance. Then I used the Jaeger data source provided by the Grafana core which replicates the issue. VMUI and Jaeger display the event timestamps correctly, Grafana is the only problematic case.

[samrg472]

After further exploring, if I export the trace and then import again it as a file, it displays the time correctly in Grafana.

Edit: Testing Grafana v12.0.4 does not have this issue.

[jiekun]

Thank @samrg472 and @JayiceZ for the efforts of investigation. I also subscribed to the issue in Grafana.