The long awaited Service Map (formerly known as Application Dependency Monitor) has been released for public preview. Check out the blog link below for excellent details and a video further explaining the service and I’ll be following this up with more details of my own once I’m able to sleep for more than a few hours per night (newborn :)).
I was working with a customer recently and we realized that when using the “Schedule” functionality the most granular re-occurrence interval available is 1 hour. In this particular case, we needed to check service status every 5 minutes and send the data to OMS to alert and trigger a remediation runbook, so 1 hour would not suffice. I had recently spoken with a member of the product group around a custom OMS solution and specifically remembered him saying that his runbook was running every 5 minutes….so I was off to investigate!
After a few minutes of searching, I was able to find some good information here. Although the post referenced the Classic portal, the same basic process still applies and worked in my scenario. By using a Scheduler Collection we can schedule at a much more granular interval. I’ve outlined the process in the new portal below.
I was working with a customer today developing a custom solution with View Designer and noticed a new feature. We can now use thresholds for queries in the List section of View Designer blades which map to color indicators, which is very cool! The thresholds and colors are both editable, but the default colors are the standard red, yellow and green. This new feature makes identifying critical and warning values in OMS performance solutions much more simple, in addition to adding aesthetic value.
To access the Thresholds feature, simply click on your solution and select Edit. Once in edit, click on the blade where you would like to add thresholds, check the “Enable Thresholds” box, and configure your thresholds.
There is one limitation that I’ve seen so far, and that is the inability to use < in the threshold settings. For counters like % free, we need the ability to use < instead of the hard-coded > value.
Update: Until < is available in threshold settings, Stanislav Zhelyazkov points out a simple workaround using reverse logic here.
I was working with a customer today and I was asked the question: “Why aren’t computers automatically grouped by OS (Linux and Windows) in OMS? Further, if computers are not automatically grouped by OS, is there an easy way to create this grouping? Like SCOM, OMS is very flexible so my canned answer to questions like these is always “we can most likely make it happen”. That said, I had not looked at his particular scenario so I was anxious to dig in and discover the answers for myself.
After a bit of investigation, I was happy to see that the new Heartbeat data does include fields for OSType, OSMajorVersion, and OSMinorVersion. Using these fields we can very easily create computer groups based on OS and OS versions. Nice!
I was doing some development work in OMS this morning and noticed that there is a new SCOM Assessment solution in the gallery marked as “coming soon”. Nice! There were already a ton of reasons for companies using SCOM to roll out OMS, and this is certainly another one. I can’t count the number of SCOM environments that I’ve worked with that simply didn’t have the expertise and/or time to track down every issue with configuration, performance, administration, etc. This solution appears to be a great step towards resolving those issues.
From the solution description:
“The recommendations are based on the knowledge and experiences gained by Microsoft engineers across thousands of customer engagements.”
I was working with a customer today to create OMS alerts utilizing the recommendations provided by the OMS AD Assessment solution. During this working session, the customer requested a list of all AD Assessment recommendations so they could choose which individual workflows they wanted to configure for alerting. After a few minutes of query design, the following query will accomplish this task.
I recently opened the OMS Log Search page to demonstrate a few queries and noticed that the page has changed quite a bit. My first thought was, where did my saved queries go? However, after a few seconds of browsing around, I was able to display all of my previously created saved queries by simply selecting the Favorites icon at the top left corner of the Log Search page. Once you select this icon, the Saved Queries window will open on the right side of the search page.
A few notes about this new Log Search page layout: