We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When running the Lambda indexer, the cloudwatch logging is actually more expensive than the execution time.
Steps to reproduce (if applicable) Run the mock data stack for a few days. Inspect the AWS cost explorer. You should get something like this:
Expected behavior Cloudwatch logs should represent at most 20% of the Lambda compute cost.
The text was updated successfully, but these errors were encountered:
rdettai
Successfully merging a pull request may close this issue.
Describe the bug
When running the Lambda indexer, the cloudwatch logging is actually more expensive than the execution time.
Steps to reproduce (if applicable)
Run the mock data stack for a few days. Inspect the AWS cost explorer. You should get something like this:
Expected behavior
Cloudwatch logs should represent at most 20% of the Lambda compute cost.
The text was updated successfully, but these errors were encountered: