Forum Discussion
Missing custom logs in Log Analytics schema pane
- Dec 28, 2018
My experience with PowerShell is it only takes a few seconds for data to show with the data collector API, after the initial setup delay. The code I used can be found at the bottom of this link.
http://www.ciraltos.com/azure-oms-log-analytics-step-by-step-data-collector-api/
This article goes deeper into ingestion time that may help with troubleshooting.
http://contoso.se/blog/?p=4493
I've see it take over an hour, but 8 seems longer than normal. Below is a link that goes over ingestion time. In my testing, I also noticed that refreshing the browser will help if data is not showing up after about an hour.
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/data-ingestion-time
Thanks for the link. I checked back every 30 mins or so but it literally did take that long. (and i did refresh my browser from time to time)
It's improved since but still takes around 1 - 2 hours for new tables to show up...
Adding data to existing tables takes around 30 mins to process.
This is very disappointing given how robust the features are compared to other competitor products.
I guess I'll just have to live with the limitations and come up with a cleaver solution ;p
- Dec 28, 2018
My experience with PowerShell is it only takes a few seconds for data to show with the data collector API, after the initial setup delay. The code I used can be found at the bottom of this link.
http://www.ciraltos.com/azure-oms-log-analytics-step-by-step-data-collector-api/
This article goes deeper into ingestion time that may help with troubleshooting.
http://contoso.se/blog/?p=4493
- daichiDec 30, 2018Copper Contributor
Thank you very much for the follow up. These links really help!
I'll give PS a try and see if there's any difference. Thanks again!
- Noa KuperbergDec 30, 2018
Microsoft
Hi Daichi,
8 hours for the initial ingestion and 1 hour for appended data are indeed much higher than expected.
Are you still experiencing that delay?