Comments
-
I think you can turn off a few things like the Service monitoring, SQL Agent stuff, and the Top Index monitoring but that's about it. But broadly, the AppInsight templates are fairly rigid. If you're after the basics, make a new custom template.
-
The Event Log component monitor functions by only looking at events within a specific time frame based on your polling interval and a multiplier. It is detecting your event and after a period of time, that event no longer appears in that time frame therefore the component goes back up. It needs to function this way…
-
"Is it possible to apply a template to the whole group while at the same time make it such that a component is not applied if not applicable?" The issue with this is depending on your template, SAM has no way of knowing what components are applicable or not. Is the software/component missing because it's not installed on…
-
There is also a time of day section inside each Trigger Action. You could try having 1 alert with 2 actions - action 1 with the business hours, action 2 with the out of hours.
-
I found similar a while ago but haven't tried it recently. Messages from an individual node (e.g. on a Node Details view) seemed to work OK. However when trying to get summary data (e.g. counts of received messages) it was very different. Running a SQL query for Syslog data from the OLV database would take seconds. Running…
-
Yes, you can have a domain account in the local Administrators group on the server and it should have full WMI access.
-
1. Unfortunately not in 2020.2.6. In the newer versions 2022.3+, you can but not in the older platform versions. 2. If you have not evaluated SAM before, you can run the offline 2020.2.6 installer and there will be an option to install/evaluate additional modules - you can expand that option and select SAM. This will…
-
Yep, that was the custom SWQL option I suggested. Nice query!
-
I don't think there is an easy count method but there a few workarounds. You say you want an alert if running on less than 2 but then say you want component down on less than 2... so I'm not 100% sure of the requirements but I'm going with you want to know if the component is stopped on more than 2 servers (i.e. 3 or 4 are…
-
Check the node isn't set to Mute Alerts. I know it seems obvious but I've had instances where people have questioned why their alerts weren't firing for specific nodes and those nodes were muted. Also check the alert trigger logic. You can reverse the logic, e.g. show up instead of down, and confirm on the Summary tab of…
-
Unless I'm missing something, you could use the "Time of Day" controls in the alert configuration. Add 2 schedules that will disable the alert during the Wed/Fri windows. If the service/process is still stopped following the maintenance window, then the alert should trigger. E.g. * Add alert Time of Day schedule to disable…
-
I'd add another action like "Write to local text file" or tag/colour the incoming messages. This confirms if it's a problem with the filtering/matching or with the email configuration. If the incoming messages don't write to the log file / get tagged / get a colour, then you need to check your filter configuration. If the…
-
If you have the older AL component based licensing, you will be limited by number of monitored components. The licensing page will have something like "Allowed number of component monitors" and your total/licensed component monitors. You can review your applications/component monitor counts in the Manage Assigned…
-
I'm not sure what the Node Downtime History fields you're referencing are but I've been meaning to play around with this report by @"stevenstadel" at some point.Maybe it might point you to what you're after. thwack.solarwinds.com/.../298845
-
A workaround could potentially be to use your Custom SWQL in a Custom Table without CONCAT'ing the data units, and have the table autoformat the data. Downside is you'll have the extra header etc.
-
If you don't want the count, then you could list the nodes in a table by just using the inner query (drop all the COUNT part). SELECT [Nodes].Caption , [Nodes].IPAddress , AVG([Nodes].ResponseTimeHistory.Availability) AS [Availability] FROM Orion.Nodes AS [Nodes] WHERE [Nodes].ResponseTimeHistory.DateTime BETWEEN GETDATE()…
-
You can use Manage Custom Properties to bulk export/import the custom property values via CSV/XLS. You'll need an identifier in the CSV/XLS to match against your nodes (the NodeID, IP address, or Caption, etc). * Go to Settings -> All Settings * Under Node & Group Management -> Manage Custom Properties * If you already…
-
Some data in the database is stored in UTC time. Some data in the database is stored in the local database time. I can't recall offhand which is which but I recommend confirming via the raw data in the database. E.g. testing an event at 2:23pm for this reply, the EventTime is stored in UTC but I can use TOLOCAL(EventTime)…
-
A couple of things. * You're missing the WHERE after the FROM line (it goes straight into the AND) * Missing a ) to close off the second SELECT Try this: SELECT COUNT(*) AS [Sub 99.9% Available] FROM ( SELECT [Nodes].Caption , AVG([Nodes].ResponseTimeHistory.Availability) AS [Availability] FROM Orion.Nodes AS [Nodes] WHERE…
-
If you are using a Component alert, you should be able to use the WindowsEventMessages variable to show the detected events for an Event Log component monitor. ${N=SwisEntity;M=ComponentAlert.WindowsEventMessages}
-
You should be able to use the Manage Pollers page to do this. * Settings -> All Settings * Under the NODE & GROUP MANAGEMENT section -> Manage Pollers * Search for 'wireless' or locate the "Wireless Controller" poller * Select the checkbox next to the Wireless Controller poller and click Assign * Change the Group By…
-
I think it's more the way Log Viewer/Analyzer handles traps. If all the traps come in under the same filter, each time it matches it makes an "event" against the node and the alert triggers off the event. So when you have a bunch of different traps come in, it will reopen the same SNOW incident because they match the…
-
If you edit the table in the report, you should be able to expand the Advanced section for that column and remove the Data Unit in Display Setting. Click the trash can icon to remove it. With and without that setting.
-
If you're talking about the SAM SQL User Experience Monitor, then it only supports 2 values and won't do what you're asking: * Statistic - the first cell (first row/column of data) returned by the query - this must be a number * Message - the cell in the second column / first row returned by the query - optional, can be…
-
You could try something like below. I have the BETWEEN 0 and 300 as down/unmanaged nodes have a ResponseTime field of -1 and External nodes are -2. I'm not sure you can change the colours of the widget as the thresholds are looking for numerical values, not text. SELECT CASE WHEN ResponseTime BETWEEN 0 AND 300 THEN 'OK'…
-
At the template level? If using SQL, it's in APM_ComponentTemplateSetting. If using SWQL, it's in Orion.APM.ComponentTemplateSetting. You'll need to join off the ComponentID from the application template and also filter off the Key column = 'FullPath'.
-
Can confirm fixed in Orion 2020.2.6 HF5. My lab instance was on HF4 and had this issue. Upgraded to HF5 and can now set compact datetime field. Next request is to have it abide by the browser datetime format! Shows up as MM/DD/YY instead of DD/MM/YY I'll put in a bug report. Edit: This is just for the Compact format issue.
-
By default, the web server is installed on the main Orion server. Pre-HCO licensing, you could install the Additional Web Server on another server and it would register as a 30 day evaluation and you could purchase an individual web server license. With HCO, I think you can deploy a web server as part of the evaluation.…
-
Remove the unique identifier columns and you will have the cumulative availabilty. So remove the Node Name and IP Address - just leave the Location and Availability columns.
-
I don't think you can using the out-of-the-box service component monitor. You could potentially do it using the PowerShell component monitor. A PowerShell script that looks for all the services starting with ApplicationService* and finding any with a stopped status would return the down or critical code. You wouldn't get…
