improve runtime detection - #38
Merged
Merged
Conversation
Detect process runtime once at module load instead of on every log event. Add Fly.io and Deno Deploy environment variables for host, serviceName, and region fields. Co-authored-by: Dan <daniel@frytg.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add Fly.io and Deno Deploy cloud environment context to log events, and detect runtime once at module load instead of on every log event.
Changes
detectProcessVersion()result at module load; log events reuse the cachedprocessRuntimevalueFLY_MACHINE_ID(host),FLY_APP_NAME(serviceName),FLY_REGION(region)DENO_DEPLOYMENT_ID(host),DENO_REGION(region),deno-deploy-*runtime prefix when on Deno Deploy@frytg/loggerto 0.0.4How to test
deno run check deno run test deno publish --dry-runReferences