Description field in the Orion.APM.ApplicationTemplate entity is currently not exposed via SWQL and it appears as NULL. this behavior has been noted by other due to the Description field not being exposed in the SWIS schema.
For Windows service monitors, collect the startup type. This value should be available for reporting and alert triggers (where "startup type" is not equal to "automatic").
I would suggest collecting startup type for Windows service component monitors. Use Case: That status could then be used in multiple ways in an alert trigger condition. It could be used to prevent alerts when a service is down intentionally (say for maintenance). Yes, I know we can mute alerts in Orion, but not all of our…
Currently, we are able to monitor a Windows service and alert if the service is not running. However, it does not differentiate between a service startup types. It would be handy if we could send an alert if a service was not running, but only if the startup type is not disabled.
It would be good if the "Down" status could be supported. Sometimes returning a response of "Critical" isn't good enough when we want to show the application as Down and alert on that. There is conflicting information on the documentation for this too... per the screenshot…
The Down code appends a block like so to the errormessage column and the UI: This is hard to read and people dont know what the error actually is. "The return code is different than expected" could just be removed if the user has supplied a message, it is very much expected! Note you can see the intended message underneath…
Something I ran into when we added our Orion SQL instance to SAM: The "AppInsight for SQL: Alert me when my database file is running low on space" alert fired on the file "SolarWindsFlowStorage_NTAFLOWMEMORYSTORAGE" in the "SolarWindsFlowStorage" database. That file is a "FILESTREAM Data" file, and thus the file…
What is the SolarWinds server and application monitor? SolarWinds Server & Application Monitor (SAM) is designed to monitor your applications and their supporting infrastructure, whether running on-premises, in the cloud, or in a hybrid environment. ... Comprehensive monitoring for Microsoft applications, systems,…
AverageMemoryWorkingSet memory can only be monitored in an API poller via bytes instead of gigabytes due to Microsoft allowing a more granular look of memory usage. SolarWinds cannot be used to monitor AverageMemoryWorkingSet of API pollers due to the following error being received, when one tries to configure gigabyte…
Currently, only POST and GET are supported. It would be good if PUT and DELETE are also supported so all remits of an API may be tested.
It looks like you're new here. Sign in or register to get started.