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
If customers are emitting similar properties from a different LogGroup, it can be cumbersome to correlate them. For example, if the customer is using Lambda Insights (which uses snake case), they would have to query data like:
filter requestId = "X" or request_id = "X"
# OR
fields coalesce(requestId, request_id) as req
| filter req = "X"
Instead, we could offer a configuration parameter that defines the convention this library uses. For example:
AWS_EMF_CASE_CONVENTION=snake
The text was updated successfully, but these errors were encountered:
jaredcnance
changed the title
Allow configuration of property casing convention for automatically added properties
Allow configuration of property casing convention for automatic properties
Oct 13, 2020
We automatically add some properties for each environment:
aws-embedded-metrics-java/src/main/java/software/amazon/cloudwatchlogs/emf/environment/LambdaEnvironment.java
Lines 60 to 65 in 9875fed
If customers are emitting similar properties from a different LogGroup, it can be cumbersome to correlate them. For example, if the customer is using Lambda Insights (which uses snake case), they would have to query data like:
Instead, we could offer a configuration parameter that defines the convention this library uses. For example:
The text was updated successfully, but these errors were encountered: