Sometimes when auditing to CosmosDB a CosmosException occurs about audit.net

[thepirat000]

Looks like you're getting a timeout from cosmosDB when trying to save the audit event.

Is your audit event too large?

Have you seen Diagnose and troubleshoot Azure Cosmos DB .NET SDK request timeout exceptions? Maybe you need to customize the timeout.

[wouter-b]

You could be right about the audit event size. I'll dive into that.
Is there any way I could catch the Exception? So, I can log the exception and continue.

[thepirat000]

Also, you could implement your own data provider, by inheriting from AzureCosmosDataProvider and adding your custom try/catch mechanism in the Insert Audit Event logic.

For example:

public class AzureCosmosCustomProvider : AzureCosmosDataProvider
{
    public AzureCosmosCustomProvider() : base() { }
    public AzureCosmosCustomProvider(Action<IAzureCosmosProviderConfigurator> config) : base(config) { }

    public override object InsertEvent(AuditEvent auditEvent)
    {
        try
        {
            return base.InsertEvent(auditEvent);
        }
        catch (CosmosException ex) when (ex.StatusCode == HttpStatusCode.RequestTimeout)
        {
            // timed out
            return null;
        }
    }

    public override async Task<object> InsertEventAsync(AuditEvent auditEvent, CancellationToken cancellationToken = default)
    {
        try
        {
            return await base.InsertEventAsync(auditEvent, cancellationToken);
        }
        catch (CosmosException ex) when (ex.StatusCode == HttpStatusCode.RequestTimeout)
        {
            // timed out
            return null;
        }
    }
}

Then you can set up the data provider like this:

Audit.Core.Configuration.Setup()
    .Use(new AzureCosmosCustomProvider(_ => _
        .Endpoint(...)
        .Database(...)
        .Container(...)
        .AuthKey(...)));

[thepirat000]

If you're looking for a retry mechanism. check this: #372 (comment)

[wouter-b]

A big thanks, your suggestions will solve my issue 👍