hasura / hasura/graphql-engine
`event_id` is not included in the event trigger logs when the level is error
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Version Information
Server Version: v2.0.10
CLI Version (for CLI related issue):
### Environment
### What is the expected behaviour?
Event trigger error logs should contain the `event_id` wherever applicable. This will help to debug issues more easily.
### Keywords
### What is the current behaviour?
### How to reproduce the issue?
1.
2.
3.
### Screenshots or Screencast
### Please provide any traces or logs that could help here.
### Any possible solutions?
### Can you identify the location in the source code where the problem exists?
### If the bug is confirmed, would you be willing to submit a PR?
Contributor guide
Research direction
The issue does not name a source file, entry point, or test. Start by tracing event trigger error-level logging in the graphql-engine repository and identify cases where event_id is available; done means applicable error logs include that event_id. No reproduction steps or sample logs are provided, so compare existing event trigger logging behavior while investigating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100