Add EMF Exporter to Default Configuration
Is your feature request related to a problem? Please describe.
The current default configuration for the Lambda layer provides out-of-the-box support for tracing but not for metrics. Since the EMF exporter is already available and users often need a quick solution for telemetry, it would be very useful to include the EMF exporter in the default configuration. This will simplify the process for users by removing the need to add a configuration file only to support metrics. By default, outputting EMF logs to stdout would be enough. It’s frustrating that the current layer doesn’t support the awsemfexporter for metrics.
Describe the solution you'd like I would like the default configuration to include the EMF exporter for metrics. This would allow users to have immediate access to CloudWatch metrics without additional setup. The configuration should output metrics to stdout by default, which simplifies the user experience.
Describe alternatives you've considered Creating a new config file.
Additional context I can create a PR for this change if needed, as the fix is fairly simple.
I think this would be a good addition.
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled
This issue was closed because it has been marked as stale for 30 days with no activity.
@msailes Do you think this issue can be re-opened? There's the workaround of using OPENTELEMETRY_COLLECTOR_CONFIG_URI to set awsemf metrics exporter, but I believe this should be the default configuration.
Let me know, happy to raise a PR
I noticed that #987 uses the default parameters for log destination. This isn't ideal for performance in AWS Lambda environments. I've specifically asked for the log destination to stdout instead of the default PutLogEvents API as it adds unnecessary latency.
@msailes Is there any reason we can’t make this change and use stdout as the default?