SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

Captura de Tela 2023-12-07 às 18.32.49.png

Captura de Tela 2023-12-07 às 18.34.08.png

Captura de Tela 2023-12-07 às 18.32.32.png

Captura de Tela 2023-12-07 às 18.33.45.png

<@U03BTNACHNX> I believe Joao also reached out cloud support email about this.

image.png

The timestamp you provided seems to be odd `March 4, 2508`

Hi <@U03BTNACHNX> thanks u contact, I’m implementing signoz as a POC for my company, currently I modified the payload according to your answer:
```[
  {
    "timestamp": 1641413853000,
    "trace_id": "abcdef1234567890",
    "span_id": "0123456789abcdef",
    "trace_flags": 1,
    "severity_text": "INFO",
    "severity_number": 200,
    "attributes": {
      "key1": "value1",
      "key2": "value2"
    },
    "resources": {
      "cpu": "30%",
      "memory": "512MB"
    },
    "body": "Example log message"
  }
]```
but it’s still not showing and I’m getting 200 as success

Investigating docker-compose up I found that the container something in the signoz-logspout log container | 2023/12/08 13:08:53!! dial tcp x.x.x.x.x:2255: connect: connection refused

you can ignore logspout as it is for collecting docker container logs.

can you send a request removing the timestamp key ?