https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
s
@nitya-signoz I believe Joao also reached out cloud support email about this.
👍 1
n
The timestamp you provided seems to be odd 
March 4, 2508
j
Hi @nitya-signoz thanks u contact, I’m implementing signoz as a POC for my company, currently I modified the payload according to your answer:
Copy code
[
  {
    "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 130853!! dial tcp x.x.x.x.x2255 connect: connection refused
n
you can ignore logspout as it is for collecting docker container logs.
can you send a request removing the timestamp key ?
j
omg @nitya-signoz is work
what happened?
@nitya-signoz thanks u help
🙌 1
n
It should be a timestamp mismatch.
✅ 1
5 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

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

Powered by