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

Logging to Date Specific Azure Table and defer activateOPtions until Connection string is set #56

Open
Jorgo56746 opened this issue Jan 20, 2017 · 1 comment

Comments

@Jorgo56746
Copy link

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

@stemarie
Copy link
Owner

If you have a solution in code and send a pull request I can include in the repo and update the nuget package

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

No branches or pull requests

2 participants