aLTeReGo ✭✭✭✭✭

chadsikorra​, one of the big advantages of actively participating during the beta is that you are among the first to receive the Release Candidate. Those who participated in the SAM 6.3 beta have already received invitations to receive the Release Candidate as recently as Friday.

Only values that exist currently are shown in the drop down. You can type "Critical" into the field manually if you have no volumes that are currently critical.

Could you not achieve this using Custom Properties? With Custom Properties you can define exactly what information you want about the node, enter that information by hand, make that information required if you like as part of adding the node, or even programmatically populate these values as part of a script.

This feature was implemented as part of the SAM 5.2 release which is currently available for download through the customer portal.

Open Resource Monitor on the server and type in the name of one of the log files on the CPU tab in the Associated Handles field to see what process is holding the file open.

SAM's HTTP User Experience Monitor is not a full fledged web browser. As such, it does not support things such as cookies or javascript. For websites that require these I would recommend using Web Performance Monitor.

Windows Interface Monitoring and topology data (L2/L3) is also part of the SAM 5.5 Release, so you shouldn't need to make a choice between monitoring mount points or interfaces. You can have your cake and eat it too.

I believe the following reports may be what you're looking for. * Credentials Used By APM Component Monitors * Credentials Used By WMI Nodes‌ * AppInsight for SQL Credential Inheritance Report * APM Component Monitors Whose Credentials are not Inherited from the Original Template

That's a very astute observation jezmarsh​ Indeed there is a perception problem with versioning that's difficult to overcome because every software company versions differently. In far too many cases the version number is more or less arbitrary and does not accurately reflect the significance of each release. While many…

Out of curiosity, which version of the Orion Platform are you running?

SNMP can be added and configured on AIX using SMIT. No compiling should be required. However, NET-SNMP is prefered as IBM's SNMP daemon is highly proprietary and does not conform to certain SNMP standards such as MIB2.

process load broken out in 1, 5, 15 minute has been added in Orion Platform 2018.2 included with NPM 12.3 and SAM 6.6.1 currently in Release Candidate.

, after some investigation it would appear as though you've stumbled upon a bug. When a component is disabled in the template you should no longer be able to access the component details view through the webUI, though it will still exists in the database when performing a SQL query like the one you posted above. If you…

This is already possible today in Orion using the HTTP/S Get/Post alert action.

What modules and module versions do you have installed beyond NPM 12.1? Also, what operating system version are you running Orion on?

You are both welcome and encouraged to comment in any idea to more clearly define your specific use case. We try our best to close duplicate ideas to consolidate votes related to the same request. This helps elevate those ideas higher, rather than splitting the votes across multiple ideas.

This could be done today using SAM's SQL User Experience Monitor.

It means an option piece of software that can be installed on your Windows server/s as an alternative to SNMP or WMI.

This somewhat exists already in SAM's AppInsight for SQL as the screenshot below shows.

We have confirmed this is indeed a javscript bug. If you wish to be notified when this issue is resolved, please open a case with support and reference this thread.

Oracle is indeed supported in the latest release.

Didn't IBM end support for AIX 6.x on 04-30-2017?

The PID associated with these processes would change with each service restart or server reboot.

SAM 6.3 does include a new SWIS API called "StartDiscoveryProfile(int profileID)" which now allows you to kick off an existing defined discovery job without needing to wait for its next scheduled run, or manually kicking off a discovery that has no pre-defined schedule. You're welcome bluefunelemental‌

Could you further describe your use case? You can today define warning and critical thresholds for components of an application and add these to a group. Depending on how the group status is defined (worst/best/mixed) the status of the group will reflect the health of the components contained therein.

mnutter wrote: Where can I determine if I'm running Orion Platform 2017.1 or earlier. I found in settings all > Orion Platform Details > ?? But which line for sure? I believe I have ACCOUNTLIMITATIONBUILDER.EXE2017.03 I see the 2017.03 reference listed many times on the exes. Am I even close here in the logic or is their a…

That is simply a documentation error. It's difficult to maintain all these matrices as new versions are released. I'll see that this one gets updated. Thanks for pointing this out!

As the RTPE functions today users who have the RTPE permission, but do not also have the SAM "Admin" user role can not start monitoring processes. The "Assigned Application" column is designed to let users know which processes are already being monitored by which application template. If a user clicks "Start Monitoring"…

What you describe is exactly how application discovery works today.

Have you considered using the Schedule Unmanage utility to unmanage this application throughout the day and only allow it to run for a predefined 5-10min period of time once a day?