Sep 18 2017 10:30 PM - last edited on Sep 19 2017 08:45 AM by EricStarker
Sep 18 2017 10:30 PM - last edited on Sep 19 2017 08:45 AM by EricStarker
I am based in Sydney and this is at 2AM so needless to say I will be hitting the ZZZ at this time. I have only just made a couple of machines report into OMS to see what info it can provide. I may get the answers after getting some data in my testing but I have a couple of questions anyway. 1 - when is Device Health likely to move out of public preview? 2 - Will device health be able to provide details from BSOD dump files so techs can see what caused the blue screens without having to get physical access to the device? 3 - Is the logging of these events done in near real-time or is it uploaded on a schedule? 4 - Will device health just be on crash analytics or will it start to move into performance type monitoring and alerting at some point as well? Thanks
Sep 19 2017 09:05 AM
Hi Brett. I'm going to break up the answers by post.
"1 - when is Device Health likely to move out of public preview?"
In our current Public Preview state the solution is available to all OMS workspaces. We are integrating feedback and testing additional functionality. At some point soonish-ish (not sharing any dates today) we will declare "General Availability" for the v1 round of features, and then start previewing new features.
As a cloud service our expectation is to iterate continually, so expect ongoing Preview states for new features as they arrive.
Sep 19 2017 09:10 AM
Sep 19 2017 09:13 AM
Sep 19 2017 09:19 AM
Sep 24 2017 07:36 PM
Thanks Matthew. I can definately understand the privacy requirements for something like this. Also I probably should have made my original question around data provided for the "AbnormalShutdownCount" instead of the BSOD kernal crashes. I just imported a couple of devices into my workspace and can see that one has some unexpected shutdowns but I cannot seem to find any info on what caused them. Am I missing a configuration to pull in that data or is this just supposed to provide a count that could indicate an issue on the device?
Sep 30 2017 09:49 PM
Oct 02 2017 05:55 PM
Thanks for that reply Matthew. I guess its difficult to provide any further details for an abnormal shutdown other than the count since there is no real diagnotic details available on what causes them. I think the count is probably as best that we can expect. ANd now that I have devices actually showing with BSOD crash details in my console, I can see the differentiation more clearly as previously I had no devices with kernal crashes. Great for the environment but not great for understanding the product entirely.
Thanks