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

Unable to parse event from cloud watch-log #108

Closed
jmilushe opened this issue Apr 20, 2022 · 2 comments
Closed

Unable to parse event from cloud watch-log #108

jmilushe opened this issue Apr 20, 2022 · 2 comments
Assignees

Comments

@jmilushe
Copy link

Please include configurations and logs if available.

For confirmed bugs, please report:

  • Version: 0.27.0
  • Setup trigger for cloud watch logs created by RDS database, i.e. - logStream:group=/aws/rds/cluster/database-1/error)
  • Add an instance to the database, which will generate log entries

The lambda function executes and logs an error:
[ERROR] TriggerTypeException: Not supported trigger
Traceback (most recent call last):
  File "/var/task/main_aws.py", line 17, in handler
    return lambda_handler(lambda_event, lambda_context)
  File "/var/task/elasticapm/contrib/serverless/aws.py", line 116, in decorated
    self.response = func(*args, **kwds)
  File "/var/task/handlers/aws/utils.py", line 109, in wrapper
    raise e
  File "/var/task/handlers/aws/utils.py", line 99, in wrapper
    return func(lambda_event, lambda_context)
  File "/var/task/handlers/aws/handler.py", line 61, in lambda_handler
    raise TriggerTypeException(e)

lambda_log.csv
log-events-viewer-result-showing-event.csv

@aspacca
Copy link
Contributor

aspacca commented Apr 21, 2022

@jmilushe thanks for reporting the issue.
could you add the environment variable LOG_LEVEL=DEBUG to the lambda and share the debug log?
please, amend any sensible information before sharing.

and if you can share the content of the S3_CONFIG_FILE (always with sensible information amended).

what version of the lambda are you running?

@aspacca aspacca self-assigned this Apr 21, 2022
@aspacca
Copy link
Contributor

aspacca commented Apr 21, 2022

hello @jmilushe , I've identified the problem, I've fixed in #107
once it will be merged I will release a new version

@aspacca aspacca closed this as completed Apr 21, 2022
aspacca referenced this issue in aspacca/elastic-serverless-forwarder Apr 21, 2022
aspacca pushed a commit that referenced this issue Apr 21, 2022
* coverage increased catching bugs and recuding complexity refactoring

* changelog

* fix test in docker

* fix test in docker

* more verbose error for config input and output type

* refactor boilerplate setup code for integration tests

* fix refactoring

* mock handlers.aws.handler.get_sqs_client in TestLambdaHandlerFailure

* refactor integration tests to improve readability

* fix #108

* fix changelog
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

2 participants