You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the appender in our projects. As log tables can get very large we would like to create a daily log table, e.g. AzureTable20170113, AzureTable20170114...
We could then delete old logs by droping the table, which is faster then deleting individual rows.
My understanding is that this can be accomplished by using extending the classes, but it would be great to have a property which will handle it natively, [TableNamePattern] = "AzureTable%date{yyyyMMdd}".
In our situation, the connection string needs to be injected from external resources (Azure DocumentDB, App Configuration Settings, Azure KeyVault). The idea is to remove AccountKeys from the source code.
Our first idea was to not provide the Connection string in the config and to call ActiveOptions() only if there is a connection string.
We created our own classes, but would prefer a native solution. Let me know if I can provide samples
The text was updated successfully, but these errors were encountered:
I'm using the appender in our projects. As log tables can get very large we would like to create a daily log table, e.g. AzureTable20170113, AzureTable20170114...
We could then delete old logs by droping the table, which is faster then deleting individual rows.
My understanding is that this can be accomplished by using extending the classes, but it would be great to have a property which will handle it natively, [TableNamePattern] = "AzureTable%date{yyyyMMdd}".
In our situation, the connection string needs to be injected from external resources (Azure DocumentDB, App Configuration Settings, Azure KeyVault). The idea is to remove AccountKeys from the source code.
Our first idea was to not provide the Connection string in the config and to call ActiveOptions() only if there is a connection string.
We created our own classes, but would prefer a native solution. Let me know if I can provide samples
The text was updated successfully, but these errors were encountered: