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

create a flag to enblae/disable Vercel log drain usage for API routes #217

Open
dasfmi opened this issue Jul 30, 2024 · 0 comments
Open

Comments

@dasfmi
Copy link
Collaborator

dasfmi commented Jul 30, 2024

as Per the comment below:

In light of the recent, rather blatant, pricing changes at Vercel, wouldn't it make more sense to send as much as possible directly to Axiom and as little as possible via log drains?

from #184 (comment)

Current behavior:

next-axiom detected if Vercel integration is enabled. For API Routes, it will use console.log() to send logs to the Vercel log drain. This would improve performance and not wait for the logger to flush.

Expected behavior:

As Vercel log drain is not free anymore and getting expenseive, next-axiom should give the user an option to enable/disable usage of Vercel log drain in API routes and by-default send logs directly to Axiom.

@dasfmi dasfmi changed the title https://github.com/axiomhq/next-axiom/issues/184#issuecomment-2208784837 create a flag to enblae/disable Vercel log drain usage for API routes Jul 30, 2024
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

Successfully merging a pull request may close this issue.

1 participant