Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistent log keys across all runtimes #752

Open
pankajagrawal16 opened this issue Feb 16, 2022 · 2 comments
Open

Consistent log keys across all runtimes #752

pankajagrawal16 opened this issue Feb 16, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request v2 Version 2
Milestone

Comments

@pankajagrawal16
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Python and Typescript use snake_case for all outputs. Java uses a mix of snake_case and camel_case.

Customers will use the same tool (CloudWatch Logs, Loggly, Datadog, etc.) to search data across logs, and if main keys are different they will find half of the information when using multiple runtimes.

At the sametime, if we break language consistency and the other application(not using powertools but standard logging libs) loose that tracking on single visibility.

Considering both the above rationale, for now, we should standardize on the same key name (snake_case) for logging output - we, Golang will also using snake_case albeit in the early phase. As it’s a breaking change for Java, let’s strive for making it configurable but a v2 should standardize it on snake_case.

Describe the solution you'd like
Ability to configure if customers want consistent logging keys same as used in powertools logging for other runtimes.

Describe alternatives you've considered

None

Additional context

@pankajagrawal16 pankajagrawal16 added the enhancement New feature or request label Feb 18, 2022
@jeromevdl
Copy link
Contributor

@pankajagrawal16 We can certainly do this one in the context of #965.

@heitorlessa, do we have a page somewhere to find the log keys used in the different languages? Or should I go in the code (ex: here and potentially elsewhere)

@scottgerring
Copy link
Contributor

#1435

@scottgerring scottgerring added this to the v2 milestone Dec 21, 2023
@jeromevdl jeromevdl moved this from Backlog to Coming soon in Powertools for AWS Lambda (Java) Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v2 Version 2
Projects
Status: Coming soon
Development

No branches or pull requests

4 participants