utilize log drain on vercel functions #185
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
schehata
force-pushed
the
console-transport-on-vercel
branch
from
944db87
to
10de2dd
Compare
schehata
force-pushed
the
console-transport-on-vercel
branch
from
0d7564b
to
289b2b8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that our vercel integration parses JSON we can utilize the log drain to send structured data. This will allow our users to send logs without having to do
console.log(stringify({message: '...'}).next-axiom will keep populating the events and attaching context/request meta as always.
some improvements we could do:
note: this could be improved later on using the transports logic mentioned in the linked issue.