In Azure I have a table storage account and there is a table WADLogsTable. It is being written too in surprisingly high volumes given the sites it is currently hosting. This website is doing it's own logging and not using any Trace.* or anything like that. I have to believe there is something automated populating the log tables. I checked all the app services and each one has all the "Diagnostics logs" turned off.
How do I figure out what is populating the logs table and kill it?
UPDATE: Thanks @Gaurav Mantri So I know what resource it is coming from and it appears to be webjob related. Not sure if it is required or optional. Here is some sample redacted output:
- Executing: 'Function_Name' - Reason: 'New queue message detected on 'queue_name'.'
- SnapshotHelper::RestoreSnapshotInternal SUCCESS - process
- Job host started
- SnapshotHelper::TakeSnapshotTimerCallback
- Executed: 'Function_Name' (Succeeded)