You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
loghttp.PushRequest.Streams: []loghttp.LogProtoStream: unmarshalerDecoder: Value looks like Number/Boolean/None, but can't find its end: ',' or '}' symbol, error found in #10 byte of ...|]
]
}
]
}|..., bigger context ...|fo\",\"message\":\"Hello world!\"}"
]
]
}
]
}|...
The text was updated successfully, but these errors were encountered:
The timestamp, as mentioned in the document you referenced, needs to be in nanoseconds, so something along the lines of 1715165546164724000 for 2024-05-08T18:52:26.164724+08:00.
As such, I was able to issue your command using my local install after making this adjustment:
The timestamp, as mentioned in the document you referenced, needs to be in nanoseconds, so something along the lines of 1715165546164724000 for 2024-05-08T18:52:26.164724+08:00.
As such, I was able to issue your command using my local install after making this adjustment:
Describe the bug
When sending logs with direct http request to loki in grafana cloud, it seems that loki didn't parse data correctly.
To Reproduce
The endpoint looks like
https://123:glc_eyJ@logs-prod-020.grafana.net/loki/api/v1/push
The http header
Content-Type
is setapplication/json
The request body is below, it is directly copied from official documents
There is a curl version:
The response is:
The text was updated successfully, but these errors were encountered: