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

Ability to customize lambda layer logs format #1032

Open
oleksii-yurchenko-easypark opened this issue Dec 5, 2023 · 1 comment
Open

Ability to customize lambda layer logs format #1032

oleksii-yurchenko-easypark opened this issue Dec 5, 2023 · 1 comment

Comments

@oleksii-yurchenko-easypark

https://github.com/open-telemetry/opentelemetry-lambda/blob/e901a5f769c985ab78ca372bb4997156422f58d6/collector/main.go#L67C43-L67C43

Hello :) Our team have AWS Lambdas on .NET and we have our own logging standart, however I see it is a bit different for your collector which uses zap logger. I am wondering if you could add some mechanism to customize it, so we can unify our logs. For example:

The one from collector:

{
    "level": "info",
    "ts": 1701769065.3820539,
    "caller": "[email protected]/otlp.go:94",
    "msg": "Starting GRPC server",
    "kind": "receiver",
    "name": "otlp",
    "data_type": "traces",
    "endpoint": "localhost:4317"
}

We want it to look like:

{
    "Timestamp": "2023-12-05T09:37:46.4796704Z",
    "Level": "Info",
    "RenderedMessage": "Starting GRPC server",
    "Properties": {
        "ApplicationName": "app-name",
        "Subsystem": "subsystem",
        "ApplicationVersion": "1.0.0",
        "Environment": "test",
        "MachineName": "Lambda",
        "TripId": "trip-id"
    }
}

Thank you for reading

@oleksii-yurchenko-easypark
Copy link
Author

👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant