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

Using @logtail/edge causes huge increase in GB-s footprint on cloudflare #117

Open
abhishiv opened this issue Jul 23, 2024 · 2 comments
Open

Comments

@abhishiv
Copy link

Hello, I'm using @logtail/edge in a cloudflare pages application with _worker.js. The web server is hono.

I recently added @logtail/edge to my app and my usage increased from around 60 GB-s to 2.3k GB-s

Screenshot 2024-07-23 at 12 51 15

For now I have removed logging and will update the thread with how the usage looks post removal.

@abhishiv
Copy link
Author

Update: the issue is gone after removing logtail.

FYKI The increase is around 6x which IMHO make logtail unusable in production on cloudflare.

Screenshot 2024-07-24 at 20 29 14

@versecafe
Copy link
Contributor

It's likely depending on your region the huge increase in usage is just awaiting the response from the server to confirm the logs have been written, is there anyway for you to check what percent of the runtime is spent idling? it might be that serverless logging could use a rework to just pop off log requests without batching and never await them as the loss of a few logs due to network issues is less important then the massive increase in cost

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