Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Azure Diagnostic creates many tables, apparently containing the same performance counters but for different days. Why does it create so many tables, and how can I delete them?
When Azure application is build you can enable or disable diagnostics in role configuration file:
When diagnostics is enabled, all Verbose monitoring data (logs) will be periodically copied over to Azure tables (bear in mind that in production system you will have to provision storage account separately as it does not happen automatically).
For each cloud service deployment, six tables are created for the role. Two tables are created for each: 5 minutes, 1 hour, and 12 hours. One of these tables stores role-level aggregations; the other table stores aggregations for role instances.
The table names have the following format:
where:
Examples:
WAD8b7c4233802442b494d0cc9eb9d8dd9fPT1HRTable– hourly aggregations for the roleWAD8b7c4233802442b494d0cc9eb9d8dd9fPT1HRITable– hourly aggregations for role instances