awsemf exporter won't create any log group, nor generating any metrics

[stevemao]

---

name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

Describe the bug
A clear and concise description of what the bug is.

I was able to patch the instrument and generate metrics with logging exporter. I can see the metrics in cloudwatch console. Now I change the exporter to awsemf but I do no see the new log group being created.

Steps to reproduce
If possible, provide a recipe for reproducing the error.

Change the default exporter to awsemf

What did you expect to see?
A clear and concise description of what you expected to see.

A new log group about metrics should be created, and emf formatted logs should be populated. Then the metrics should show it

What did you see instead?
A clear and concise description of what you saw instead.

No new log group is created

What version of collector/language SDK version did you use?
Version: (e.g., v0.58.0, v1.11.0, etc)

latest

What language layer did you use?
Config: (e.g., Java, Python, etc)

nodejs

Additional context
Add any other context about the problem here.

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "localhost:4317"
      http:
        endpoint: "localhost:4318"

exporters:
  logging:
  awsxray:
  awsemf:

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [awsxray]
    metrics:
      receivers: [otlp]
      exporters: [awsemf]
  telemetry:
    metrics:
      address: localhost:8888

[stevemao]

To prove that it is using the exporter, i see these logs in my lambda

{
    "level": "info",
    "ts": 1706941601.1228578,
    "logger": "NewCollector",
    "msg": "Using config URI from environment",
    "uri": "/var/task/collector.yaml"
}

{
    "level": "warn",
    "ts": 1706941601.145583,
    "caller": "[email protected]/emf_exporter.go:74",
    "msg": "the default value for DimensionRollupOption will be changing to NoDimensionRollupin a future release. See https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23997 for moreinformation",
    "kind": "exporter",
    "data_type": "metrics",
    "name": "awsemf"
}

[github-actions]

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

[stevemao]

Not stale

[Tameem-623]

Hi @stevemao, were you able to find any solution for your issue? I am also facing the same issue. I am getting the same logs but no metrics are generated. I have also tested my code locally and it is working perfectly.

To prove that it is using the exporter, i see these logs in my lambda

{
    "level": "info",
    "ts": 1706941601.1228578,
    "logger": "NewCollector",
    "msg": "Using config URI from environment",
    "uri": "/var/task/collector.yaml"
}

{
    "level": "warn",
    "ts": 1706941601.145583,
    "caller": "[email protected]/emf_exporter.go:74",
    "msg": "the default value for DimensionRollupOption will be changing to NoDimensionRollupin a future release. See https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23997 for moreinformation",
    "kind": "exporter",
    "data_type": "metrics",
    "name": "awsemf"
}

[github-actions]

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

[stevemao]

@Tameem-623 No i haven't...

[codemedian]

There seems to be a fix that supposedly addresses this in the plain otel variant, see this PR which is included in the latest release version 0.11.0

From what I can tell this change hasn't yet made it into the aws-otel-lambda version but I could be wrong. Are there any updates/workarounds on this?