Forum Discussion
Machines availability on specific period of time
- Jan 11, 2021
Maybe this?
Heartbeat // last month | where TimeGenerated between ( startofmonth(now(),-1).. endofmonth(now(),-1) ) | where Computer contains "JBOX00" // find 4th week which is week "3" | extend maintSaturday_ = endofweek(startofmonth(now(),-1),3) -1d, maintSunday_ = endofweek(startofmonth(now(),-1),3) + 1d // exclude 4th week from data set | where TimeGenerated !between ( maintSaturday_ .. maintSunday_ ) | summarize heartbeat_per_hour=count() by bin(TimeGenerated, 1h), Computer | extend available_per_hour=iff(heartbeat_per_hour>0, true, false) | serialize | summarize total_available_hours=countif(available_per_hour==true), total_number_of_buckets = max(row_number()) by Computer, bin(TimeGenerated, 1d) | extend availability_rate=(total_available_hours-48)*100/total_number_of_buckets | project TimeGenerated, availability_rate | order by availability_rate desc | render timechart
CliveWatson It is ok now. the problem was related to Data Retention which was set to 30 days. Therefore I didn't see more than 30 days ago and it was showing the value of (today-30days)
I think I just need to wait for next month to collect the full data 🙂
Thank you again.
Thanks for the update, good luck next month - maybe try it in our demo data set? Access for free here
- Oleg__DJan 20, 2021Copper Contributor
It looks perfect in demo data set 🙂
However when I pin it do dashboard I still see results for the last 30 days, despite the custom date set. Is there a way to bypass this override option?- CliveWatsonJan 20, 2021Microsoft
30days is the max (as far as I know), a custom range is for values between 0-30days.
Azure Monitor Workbooks don't have this restriction, that may be an alterative for you?- Oleg__DJan 26, 2021Copper Contributor
CliveWatson To be honest, that looks much better 🙂
Thank you!