aLTeReGo ✭✭✭✭✭

What you describe sounds very similar to the "All Alerts this Object can trigger" resource.

From the screenshot you provided above it appears as though you are using the Basic Alert Manager. I recommend using the Advanced Alert Manager instead, as it's far more flexible and powerful.

This field supports type ahead, so simply start typing the name of the application as it appears in the "All Applications" resource and it should begin filtering the results as you type. I should note however that it may take a moment or two for the results to begin filtering. 

How does the Agent appear under Manage Agents? Is it in a healthy state? How is availability configured on the node? Are you using the Agent for availability calculations or ICMP? What happens when you change it? The behavior you're describing is very unusual, and perhaps a bit too complex to delve into on a forum such as…

I'm in agreement with . The issue is likely with your Trigger Condition or any alert suppression rules you have defined within the alert. If you post screenshots for those alert tabs along with an explanation of how you expect the alert to work, we may be able to more accurately pinpoint the problem.

The two options function essentially identically. Agent status will report ‘down’ when a AMS message goes unreplied to by the Agent. The ICMP option reports a node being down when the node fails to reply to an ICMP echo request. The ‘faster’ in this case is really about payload size. ICMP packets are super tiny, where as…

There are no parameters you need to pass to the 'swiagentaid.sh init' command. If you are wanting to configure the Agent as part of the provisioning process in an automated fashion, you will want to create an answer file and pipe it through with the swiagentaid.sh init' command. For example. Create a file called…

Can you post a screenshot of what you're seeing? Are you able to do a 'List Resources' on the Agent Managed node that's appearing as 'Unknown'?

You can absolutely use systems like Red Hat Satellite for deploying the Agent en masse. Below is a similar example using Chef and Puppet. Deploy agents with Chef or Puppet

No two Linux appliances are alike, so I can't say definitively. I will say that I've had successes installing the Linux ARM agent on some embedded devices as well as the Linux Agent on virtual appliances where I was able to SSH into the device and 'su' to root with either a bash or korn shell. Some Linux appliances when…

You lose Hardware Health if it's a physical Dell, HP, or IBM server. You would also lose SAM's Asset Inventory feature, the ability to apply SAM SNMP Component Monitors against the node, and the Location and Contact fields on the Node Details view will not populate with information configured in the SNMP settings of the…

pratikmehta003 wrote: 1. If we poll through agent for the Linux flavors then we will still be able to get the hardware information? Server Hardware Health Monitoring is fully supported by both the Windows and Linux Agent. pratikmehta003 wrote: 2. Secondly how is the calculation of memory parameter done when we poll via…

Is your Orion website configured to use HTTPS?

fredrikolausson​. the cron job is a function of beta 2 as a sort of temporary watchdog in the event the agent service stopped running for any reason. This has been addressed in beta 3, which should be available in the next few weeks.

It may take a moment for the plugins to deploy and the agent to be fully operational. If the agent is still not operating normally please gather a Diagnostic from the Orion server and zip the contents of '/opt/SolarWinds/Agent/bin/appdata/Logs' on the machine where the agent is installed. Then reply to the Beta email you…

Beta 3 should include the ability to push the Linux Agent to Cloud instances through the Orion web interface, as well as download the RPMs for manual installation virtual anywhere. 

No sir. The Linux Agent will not work with SAM 6.2 and should make no attempt to communicate with your production Orion instance.

While certainly not as detailed, you could use the "Machine Type" property in the Report Writer, as seen in the out-of-the-box "Device Type" report.

Bronx is correct. The information normally included in the PDF documents can be found in the body of the template post. This "Expert Knowledge" is also included in the template itself under the description fields of the application and component monitors themselves when opening the template for editing. This information…

Glad to hear you got things straightened out! Thanks for following up.

orioncrack‌, have you provided your feedback in the following thread? Are you interested in improved support for log file monitoring?

Shooting in the dark, but have you tried something like the following? ${SQL: SELECT cast((${N=SwisEntity;M=DatabaseCopyAlert.LogUsedTotalPercentage}) as decimal(16,2))} Taking the macro out of the equation it seems to work for me.

How do you handle Antivirus in your PVS environment? Most enterprise antivirus products these days register to a centralized management console, so I would imagine you would encounter the same or similar issues there as you do with the Orion Agent.

[Settings - Customize Menu Bars] and click "Edit" above the menu bar you wish to modify, then simply drag and drop items from the right panel to the left to remove items from the menu bar. To add new items to the menu bar, drag items from the left column of "Available Items" to the "Selected Items" column.

Correct. Hotfixes are cumulative. Meaning that all you need to do is install HF2 and you also receive all fixes from HF1.

The new Agent included in SAM 6.2 (Currently in Release Candidate) should eliminate the need to double hop.

Thank you rschroeder for such a detailed analysis. I can't say for certain what was locking that file, but if it occurs again in the future open Resource Monitor on the machine, go to the "CPU' tab and enter in the name of the file under 'Associated Handles'. This should tell you the process that is locking that file. As…

I believe you downloaded applied hotfix 1 for SAM 5.2 and .NET 4.0 doesn't trust this file. It's necessary to manually mark this file as trusted. Right click on the 'SolarWinds.APM.Probes.dll' and select properties. Then click on 'Unblock' button at the bottom (see screenshot below). This will mark the library as trusted.…

Sounds like you're well on your way then. Report back if you encounter any other roadblocks. Oh, and yes. is pretty damn amazing!

Agreed. Web Performance Monitor would be my recommendation as well. You can also use SAM's HTTP or HTTPS User Experience Monitors for more simplistic web page response time monitoring.