Comments
-
@"KMSigma.SWI" - The "My Orion Deployment" -> "High Availability Deployment Summary" screen does not provide anything like the level of detail for monitoring of specific, critical Orion services and metrics as those seen in the Orion 2020.2 application templates provided by the SAM team. I even recently used one of these…
-
@"tony.johnson" Hi Tony, here's a screenshot:
-
@"li-migration" Where is this implemented in 2020.2.1? Having trouble finding it.
-
Hi jew, Can you provide the English schema translations for the following columns in your query? B.endk_devicetype, B.endk_ELnetområde, B.endk_fysiskplacering Thanks!
-
@"jan.rachwalik" I'll give you two examples of existing API Poller templates included with 2020.2.1 that provide incomplete results due to this limitation. The Microsoft 365 Exchange Mailboxes template provides an inaccurate count for "All Mailboxes Count" because it is only considering the first page of results. The…
-
@"jan.rachwalik" This goes back to the static vs dynamic nature of the API Poller feature. You don't know how many incidents there will be (in my case Microsoft 365 service incidents), so unless the API Poller can dynamically add the array members as children of the monitored parent array, this approach is infeasible. What…
-
@"jan.rachwalik" This actually won't work as you don't know how many pages there are for the return. So what we need in the API Poller feature is that supports looping until that next page link is no longer part of the response. That's the way the Microsoft API's have worked for many years now.
-
@"adam.hert" No, I'm not running PowerShell 2.0. This template had various counters that simply don't exist on an Exchange Server 2016 Edge Transport server. So I just removed this template and manually created my own. Thanks.
-
@"bshopp" Also, the vast majority of the performance counters in the template are showing a status of: Performance counter not found. HResult: The specified object is not found on the system.
-
@"bshopp" Thank you for this template. Is the following a known issue on the Details View - Summary under Multi-Component Statistics - Statistics Data? The "Incoming Connections" resource is missing. The file ~/Orion/APM/Resources/Node/IncomingConnections.ascx is not found. FYI, I'm running SAM 2020.2.1.
-
@"cmazko" Thank you for checking on this. I appreciate your time and assistance.
-
@"cmazko" Forgive the additional questions, but I want to ensure that I understand this correctly. Are you saying *not* to use the original Main Poller and Additional Polling Engine 2020.2 templates from the blog post but *instead* use these standby templates on each node in the pools? If so, are we losing any monitoring…
-
@"cmazko" I wasn't asking about 2019.4. We're running 2020.2. I was asking about the nature of the "standby" templates when using HA. As either node in the pool may assume the role of active or standby, if these templates are only for the poller currently serving as standby, that would mean that every time you failover…
-
@"cmazko" Are you able to answer the question above from last Thursday? Sorry about forgetting to tag you in that reply.
-
Thanks! As either node in the main pool or the APE pool could be standby or active at any time based on failovers, do these templates account for that? I ask because the name of the templates sounds as though they would only be applied to the node that is currently in standby which, as previously stated, could be either…