aLTeReGo ✭✭✭✭✭

Thanks for the update . I'll see about getting your case escalated.

If the issue is solely with the events generated automatically by the application going down you could rely solely on the events written from the alerts themselves and disable the events automatically generated by SAM. The process requires modifying the database so I recommend making a backup before proceeding. In the…

Are you running 1.5.1? Are you using X,Y mode in this recording? Does this occur for all your transactions or just this one?

Are you using Syslog via the Windows Event Log Forwarder or are you using SAM's Event Log Monitor?

Negative. The syslog/traps would not be duplicated unless you configured devices to send to both the real/physical IP address of the server, as well as the VIP. If you configured your devices to send to both physical/real IP addresses of each member of the pool then duplication is not possible.

In that case I'll assume your web server is NAT'd behind the firewall and that it's currently managed in Orion using it's RFC address. If that's the case then add a new external node using the NAT'd IP address of the web server instead of the FQDN.

That is not in the immediate roadmap. Currently we are focusing on more tightly integrating Virtualization Manager into the Orion platform.

I've seen this occur when maintenance runs or backups are running on the SQL server. Anything that causes extremely high I/O on the SQL server database (tempDB or NetPerfmon database). If this is a shared SQL server other applications using the database server could be having a negative effect on the performance of the SQL…

It all really depends on the number of nodes being monitored across those slow links, how many applications, and what the polling method being used is. What kind of link is this that you're running, a 56k? How many hosts on the other side of that link are you wanting to monitor?

By default, Orion only stores seven days of detailed data which is required for accurate baselining. If you increase your detailed statistics retention period to 30 days, then 30 days of data will be used to calculate the baseline.

"Total" implies some specified time frame. The counters listed above display the number of messages sent/received per-second rather than what it sounds like what you're trying to achieve; which is likely total number of messages sent received this week/month/etc.. Is that correct? If that's correct, this could be achieved…

Specifically what information are you having difficulty adding to the alert that you would find valuable. Please be as specific and descriptive as possible.

That is correct. The SQL User Experience Monitor must be assigned to the node hosting the SQL database, so these metrics will always appear to be coming from the Orion SQL server in your case. A fairly simple solution if that's untenable would be to use the ODBC User Experience Monitor instead, since you can assign it to…

Each out-of-the-box default AppInsight for Exchange Alert has at least one pre-configured alert action which provides a basic example of many of the macros uses.

The hard URL is saved as part of the recording, but this is only one of many components used in the fuzzy match. SeUM was designed from the ground up to work with dynamic content. The link location in the DOM tree for example, is also saved in the recording. All of these elements are then used to make a fuzzy match of what…

The short answer is no... But Network Guru will probably come along and whip out some custom code that will do it ;)

If I'm reading this query correctly, it appears to be the Database Performance Analyzer integration into Orion itself that is causing this issue.

The Finger application template included in APM consists of a single TCP Port Monitor pre-configured for port 79 (the default finger port). So they're essentially one in the same.

CPU is listed when you "Edit" the node since it's a part of the node itself rather than a subcomponent like a volume or interface.

We've done plenty of research and many of the counters included in this template aren't available in DB2 9.5. You can however create your own template for monitoring DB2 9.5 using ODBC queries.

Yes. This can be done using the "Custom Table" resource.

LGentile, would my suggestion work for your needs until a Syslog alert action is incorporated into the SNMP Trap Viewer?

Much agreed. Agentless is normally much prefered for most systems, but there is the occasional instance where agents are beneficial. A hybrid approach is typically best.

You can alternatively disable history for a specific individual user account.

This sounds like it could be a bug. Please open a case with support so we can track this properly.

Have you verified that the credentials you are using to monitor the service in SAM are in domain\username format?

This thread may be of interest. Especially the following excerpt. Verify OMSA SNMP Settings If OMSA was installed after SNMP, these changes should have already been made by the OMSA installer. The changes setup OMSA communication with the SNMP agent and give read-only access to the entire MIB tree to the public community.…

All previously released versions are available for download through your Customer Portal, and can be selected when you click the "Choose Download" link. Below is an example download showing all previous versions of the Orion Additional Poller.

Orion Core is included within the installer of each module. There's no separate installer for Orion Core. It will be updated to the latest version as you upgrade your modules (SAM, NPM, etc.)

This is NetBIOS over TCP/IP traffic. 137 is name services and 139 are session services. These ports should not be required unless you are using short NetBIOS names rather than a RAW IP address or Fully Qualified Domain Name to access the remote computer. You can certainly open them if you would like, but TCP Port 445 and…