fix(nuxt): Detect Azure Function runtime for flushing with timeout#15288
Merged
s1gr1d merged 1 commit intodevelopgetsentry/sentry-javascript:developfrom Feb 5, 2025
sig/nuxt-azure-serverlessgetsentry/sentry-javascript:sig/nuxt-azure-serverlessCopy head branch name to clipboard
Merged
fix(nuxt): Detect Azure Function runtime for flushing with timeout#15288s1gr1d merged 1 commit intodevelopgetsentry/sentry-javascript:developfrom sig/nuxt-azure-serverlessgetsentry/sentry-javascript:sig/nuxt-azure-serverlessCopy head branch name to clipboard
s1gr1d merged 1 commit intodevelopgetsentry/sentry-javascript:developfrom
sig/nuxt-azure-serverlessgetsentry/sentry-javascript:sig/nuxt-azure-serverlessCopy head branch name to clipboard
Conversation
andreiborza
approved these changes
Feb 4, 2025
s1gr1d
added a commit
that referenced
this pull request
Feb 5, 2025
Zen-cronic
pushed a commit
to Zen-cronic/sentry-javascript
that referenced
this pull request
Feb 5, 2025
…etsentry#15288) The debugging ability for Azure Functions when using Azure Static Web Apps is very limited. But as I could see some Sentry-related logs I **think** Sentry is generally initialized. However, server-related logs don't show up in Sentry. This is **probably** because the Azure Function finishes before the error can be sent to Sentry. By adding the Azure environment variable to check whether we should flush with a timeout, this should possibly fix the issue. Logs in Application Insights: 
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.
The debugging ability for Azure Functions when using Azure Static Web Apps is very limited. But as I could see some Sentry-related logs I think Sentry is generally initialized.
However, server-related logs don't show up in Sentry. This is probably because the Azure Function finishes before the error can be sent to Sentry.
By adding the Azure environment variable to check whether we should flush with a timeout, this should possibly fix the issue.
Logs in Application Insights:
