The logs displayed on the signoz-frontend page are out of order

[cyxinda]

Bug description

Please describe.
The logs displayed on the signoz-frontend page are out of order. It cannot display logs in strict time order. I think this occurs because the sorting time is milliseconds instead of nanoseconds.

If this affects the front-end, screenshots would be of great help.
This pictrue show the log order in signoz front-end: But actually,the log collected by otel client in the k8s node should be :

Expected behavior

The logs displayed on the signoz-frontend page should be sorting in nanoseconds.

How to reproduce

1. 2. 3.

Version information

• Signoz version:

  cyxinda@oldsix [~/download] ➜  helm search repo signoz                                                                                                                                            [10:02:56]
  NAME                            CHART VERSION   APP VERSION     DESCRIPTION                                       
  signoz/signoz                   0.56.0          0.58.0          SigNoz Observability Platform Helm Chart          
  signoz/signoz-otel-gateway      0.0.1           v0.0.16         A Helm chart for deploying SigNoz Opentelemetry...
  signoz/alertmanager             0.5.2           0.5.0           The Alertmanager handles alerts for SigNoz.       
  signoz/clickhouse               24.1.9          24.1.2          A Helm chart for ClickHouse                       
  signoz/k8s-infra                0.11.18         0.109.0         Helm chart for collecting metrics and logs in K8s 

• Browser version: Google Chrome 版本 131.0.6778.69（正式版本） （64 位）
• Your OS and version:

  root@sc-master-1 [~/signoz/infra/k8s-infra] ➜  uname -a                                                                                                                                           [13:40:36]
  Linux sc-master-1 6.6.2-1.el9.elrepo.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 12:18:26 EST 2023 x86_64 x86_64 x86_64 GNU/Linux

• Your CPU Architecture(ARM/Intel): Intel

  Additional context

Thank you for your bug report – we love squashing them!

[welcome[bot]]

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.