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

Add diagnostic events for scenarios that prevent a function app from starting #9597

Merged
merged 19 commits into from Nov 3, 2023

Conversation

Francisco-Gamino
Copy link
Contributor

@Francisco-Gamino Francisco-Gamino commented Oct 10, 2023

Issue describing the changes in this PR

This PR resolve the following issues:

  1. HostIdCollisionErrorCode should be AZFD0004 instead of AZFD004 #9214

  2. Diagnostic event for when the function app has 10 non-decryptable secrets backups #9430. In this scenario, the Functions Host generates a diagnostic event when the app is unable to start due to the presence of 10 non-decryptable secrets backups. The event documentation will provide guidance to help the user delete the backups, as well as instructions on how to prevent the function app from reaching this state. The screenshot below shows the diagnostic event in the Portal.

image
  1. Diagnostic event for when the secrets blob access tier is set to archived #9431. In this scenario, the Functions Host generates a diagnostic event when attempting to read secrets from blob storage. If the operation fails with a RequestFailedException, Status 409, and Error code BlobArchived, the event is triggered.

image

  1. Diagnostic event for when the Functions Host cannot start due to parsing errors in the host configuration file #9595. In this scenario, the Functions Host generates a diagnostic event when the function app is unable to start due to parsing errors in the host configuration file. The screenshot below shows the diagnostic event in the Portal.
image

/cc @eamonoreilly @mattchenderson @fabiocav

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

@Francisco-Gamino Francisco-Gamino marked this pull request as ready for review October 10, 2023 19:51
@Francisco-Gamino Francisco-Gamino requested a review from a team as a code owner October 10, 2023 19:51
Copy link
Member

@soninaren soninaren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments, looks good otherwise.

Copy link
Contributor

@aishwaryabh aishwaryabh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just left a small comment :)

@Francisco-Gamino Francisco-Gamino force-pushed the Francisco-Gamino/add-diagnostic-events branch from 92c961b to 8ff8fa9 Compare November 3, 2023 20:57
@Francisco-Gamino Francisco-Gamino merged commit d248676 into dev Nov 3, 2023
9 checks passed
@Francisco-Gamino Francisco-Gamino deleted the Francisco-Gamino/add-diagnostic-events branch November 3, 2023 21:44
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 this pull request may close these issues.

None yet

6 participants