Skip to content

Improve error handling when DiagnosticEventsTableRepository cannot flush logs to table storage #10757

@cjaliaga

Description

@cjaliaga

When the Function App cannot access the table service (due to missing permissions, firewall/private endpoint restrictions, invalid SAS, etc.), attempts to flush logs in DiagnosticEventsTableRepository fail repeatedly. This generates excessive log entries and does not resolve itself without manual intervention.

We need to enhance error handling so that if table access remains unavailable, we can disable the service and stop flushing logs as we have done in #10539, reducing log noise and preventing endless retries.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions