aLTeReGo ✭✭✭✭✭

This is effectively implemented as a result of the new optional agent included in the SAM 6.2 release currently in beta.

I spoke with one of our most senior developers to verify but the total job weight is not a useful metric for measuring poller capacity. In fact, think of it more as a random number generator than a capacity planning metric. The metrics that provide some insight into poller capacity are Polling Rates or Polling Completion.…

Each beta contains a different build of Orion Core that is not universally compatible with all beta releases. We did perform a coordinated beta release a month ago in which all products that participate in the AppStack were released with the same version of Orion Core. SInce that time however the release cadence for each…

Each case description is mapped to the respective case number above by its SuperScript letter.

Bronx‌ may be able to point you at some documentation, but in the meantime it's fairly easy to find on your own. SImply edit any currently monitored volume a click the "Override Orion Capacity Thresholds". Then you will be able to adjust the thresholds for this volume, separate from the global thresholds.

This method of migration will not allow you to bypass the OS limitations of the version you're running. In your case, Orion Platform 2015.1 did not support Windows Server 2019, so the installer is trying to protect you from configuring HA on a machine where it won't work. I would recommend upgrading to Orion Platform…

Have you tried using our SQL Server Analysis Services templates available in the Content Exchange? SQL Server 2012 Analysis Services SQL Server 2008 Analysis Services SQL Server 2005 Analysis Services

That could certainly be possible, but note this is just a file download of a '.RDP' file. It's not a point, click, launch experience. It's point, click, download, double click on downloaded file, launch.

greenpaddyirishman wrote: Great step by step approach but how would one go about this if I have my Orion and database server separated out on 2 different machines? I already have prepared 2 new 2016 servers, I've read that I should move over the database first and then focus on the application side. The instructions above…

If you're having an issue with the release candidate you would post your question to the Server & Applications Monitor Release Candidate​ forum. If you're trying to obtain a copy of the Release Candidate and are under active maintenance you can download it from the Customer Portal.

The main differences are that virtual memory information is only available as a volume, and physical memory reporting is significantly more accurate when it also monitored as a volume. How the memory portion of "CPU & Memory" is calculated is fairly crude as to be applicable to virtually any device. The memory volume…

Go to http://{your-Orion-Server-IP-Address}/Orion/Admin/AdvancedConfiguration/Global.aspx Scroll down to the 'PerfStack Settings' section and modify the 'MaxRealtimeMetricsPerPerfStackCount' value. Then click 'Save'.

Also note that it's currently possible to do this today using the Advanced Alert Manager.

Adjusting the display order components are listed in is already possible today at the Application or template level.

This is already possible today using the 'isServer' property in a Dynamic group, which you can then be coupled with additional properties you might want defined such as OS, location, etc. etc.. Once the group is created, simply assign your template to the group.

SAM 5.2 already includes support for monitoring Hardware Health of IBM Blade Servers.

SAM 6.0 included a whole host of new macros/variables for SAMs script monitors. * ${USER} * ${PASSWORD} * ${PORT} * ${Node.SysName} * ${Node.Caption} * ${Node.DNS} * ${Node.ID} * ${Component.ID} * ${Component.Name} * ${Application.Id} * ${Application.Name} * ${Application.TemplateId * ${Threshold.Warning} *…

This can be done using the Web Based Alert Manager included in SAM 6.2.

Agents in the latest 2019.4 release require .NET 4.8. The Agents self-satisfy their own system requirements when automatic updates are enabled (default behavior). Any update to the Windows operating system causes some initial delay to the startup. This note was added so that users were not caught off guard the next time…

Applications that are unmanaged never results in data loss, aside from historical data that's eventually purged out of the database as part of nightly maintenance. So if you unmanage an application (or a node for that matter) longer than your retention period, you'll end up with no historical data in the database. That…

Users will be able to upgrade from 1.x, 1.5, or 1.5.1 to the next version when it's released. The upgrade process will be as simple and straightforward as upgrading any Orion product. It will be essentially the same process as installing for the first time but all the answers are pre-populated for you. Simply clicking next…

If you're continuing to experience unusually higher than normal CPU utilization, please open a case with support. We'll need to look through your diagnostics to determine what's going on.

This was implemented in SAM 6.4

You can essentially disable these components already simply by removing the thresholds. Statistics will still be collected but they will no longer trigger/alert. Simply delete the warning and critical thresholds such that the fields are null.

Upon upgrading to SAM 6.0.x Asset Inventory should be enabled automatically for all nodes it's applicable to. The only exception being nodes assigned to additional pollers. If for any reason this was not enabled automatically for those nodes, or for nodes assigned to additional pollers you can run a one-time Network Sonar…

All SAM jobs are weighted equally. Can you provide details for the problem you're trying to solve?

If I was a betting man, I'd say probably sometime in the future. Unless of course you're reading this post after it's already been released. Then I'd say sometime in the past.

Does the file \\server2\share\filename.dat change often or at all?

The Events issue you are referring to is likely a bug that was very recently identified and tracked internally under FB357428. I would ask your support rep to verify if this is indeed the same issue. If it is not, then we need to dig in and determine what the cause of the issue is, because this should not be occurring.

SAM 6.0 (currently in beta) includes a feature called AppInsight for SQL which provides far greater depth in SQL server monitoring than previously possible in SAM. This includes information such as longest running/most expensive queries and much, much more. I recommend signing up for the beta and trying it out for…