Forum Discussion
Extend the period of storing telemetry of all services of my subscription.
I have had now 4 support cases in which i see strange behavior of my services in the Azure cloud. For this i created support cases. We are a software company building solution on the Microsoft stack. In case of an incident we first look to our solution and will do an RCA. Sometimes the root cause is not related to our solution but to the Azure services. When seeing this we create a MS support case. It will take some time for MS to understand the case. A lot of time the case, is moved to different engineers. Because of this we run out of the 30 days for which telemetry of our services are available for the MS engineers. So we loose all interesting data to find the Root cause. Please extend the 30 days. This is really too short for analyzing situations. In our company we store telemetry information for 1 year. It is not acceptable for our customers that we do not know the root cause of the incident.
6 Replies
Hi Andre,
I understand that backend infrastructure telemetry data exists, but it's not visible for customers/partners, or is it? In case it is, just out of curiosity, where can I find this or only visible for MSFT engineers working on cases and only data of the last 30 days?
Pete
Hi Pete, It is not available for us. It is only available for MS. After 30 days it is gone. For MS support cases mostly the 30 days is too short. This is so frustrating to hear this already for the 4th time.
I'm not aware of Microsoft providing overall Azure backend telemetry data to customers/partners since a lot of the services are running on shared infrastructure but I can be wrong.
Hi Pete, yes and that telemetry data is necessary for these support cases. I have had 4 support cases now for which i think something went wrong in the shared infra structure of Azure. That telemetry is gone after 30 days. I do not have access to this information, so i can't store it. This shared infrastructure ('backend') telemetry data is needed for these support cases.
Hi Pete,
thanks for your reply but that will only the telemetry of we as a customer, can see.
I'm talking about the telemetry of MS itself. I can 't access telemetry data of their back-end processes. Like moving of databases to other instances if local disks are running out of diskspaces.Gr. André
If you're referring to the Activity Log, you can export it to a Log Analytics workspace, where it can be retained for up to 2 years.
To do this, navigate to the Monitor service in the Azure portal and select Export Activity Logs. On the next screen, choose the specific logs you want to export and the destination. Configure your preferences and save the settings.
For Log Analytics, you can extend the default retention period from 30 days to a maximum of 730 days for the entire workspace or adjust retention settings at the individual table level. Refer to the screenshots below for more details.
Keep in mind that storing this data in Log Analytics will incur costs based on the volume of data ingested daily.
