redpanda-data / redpanda-data/redpanda
Logs are being sent to `stderr` when viewing in GCP Logs Explorer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
It looks like all Redpanda logs are shown as ERROR when viewing them in GCP Logs Explorer. The reason seems to be that the logs are using an unstructured textPayload and Google doesn't know how to parse this (and defaults to ERROR).
Below is an example of another log event that uses jsonPayload and has not issue since the payload can be parsed:
More details:
https://cloud.google.com/logging/docs/structured-logging
https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs#best_practices
JIRA Link: CORE-1228
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Redpanda emits its logs and compare the output with Google Cloud's structured-logging guidance linked in the issue. Confirm the result in GCP Logs Explorer: log entries should use a parseable structured payload and no longer all appear as ERROR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, google-cloud
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100