doubletaya.blogg.se

The Scan Result Topic receives the scan results from the Scanner Function and publishes them to the subscribers. For details of monitoring the Scan Result Topic, see Be notified of scan results through Azure Service Bus Topic. The Scanner Function consumes the messages in the Scanner Queue's dead-letter queue and publishes the scan result with a -4 and "unsuccessful scanner invocation" status to the Scan Result Topic. If the Scanner Function cannot successfully process a message in the Scanner Queue a certain number of times, the message is sent to the Scanner Queue's dead-letter queue. The Scanner Queue stores the messages sent from the Blob Listener and is consumed by the Scanner Function. You can follow the steps in Reacting to Blob storage events to monitor the dead-letter events. You can find the resource ID of the blob container in the blobSystemTopicDeadLetterStorageID field on the storage stack's deployment Outputs page. If the Blob Listener cannot successfully process an event a certain number of times, the blob event grid system topic dead-letters the event by sending it to the specified blob container. When a file is uploaded to the protecting blob storage, the blob event grid system topic publishes a event to the Blob Listener. Blob event grid system topic dead lettering

You can monitor the file events that failed to be processed by File Storage Security components in the following places.