temporalio / temporalio/temporal
Create native support for ECS logging format
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Temporal currently does not support ECS logging format.
Describe the solution you'd like
I would like to get the Temporal server logs (history, frontend, matching and worker) in ECS format (ECS logging libraries | ECS logging libraries).
Describe alternatives you've considered
I am currently wrapping the temporal output with a parsing, which is currently not a good solution. My ECS fields are hard-coded in the wrapper mapping temporal fields into ECS fields. It is hard to maintain, we don't see immediately when there will be breaking changes that would make us to lose some fields on the custom parser.
Additional context
Conversation raised on slack https://temporalio.slack.com/archives/CTT84RS0P/p1781689264235479
And in the community: https://community.temporal.io/t/logging-format-in-ecs/19671/2
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 reviewing how Temporal server logs are produced for the history, frontend, matching, and worker services, then compare their fields with the Elastic ECS logging format. The work is done when those services emit ECS-formatted logs natively, without an external parsing wrapper, and the supported fields remain clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100