Quantcast
Channel: THWACK: Message List

Need Group Availability AVG option in report

0
0

All, I'm using the built in Group-Availability Last Month report, which works for me, but what I really need is a way to get an AVG of the availability of ALL groups listed. Can someone direct me please? Ideally, it would be nice to have that as an option within the report. Thanks! Dave B


Re: How do I run PowerShell scripts (in .ps1 format) on remote machines?

0
0

I've definitely done what you describe of just having my SAM monitors call local files.  As you said its kludgy but does the job.  The usual problem I run into here is that server admins write scripts for the purposes of things they need done, and almost never care to think about the format requirements I have in order for SW to interpret the results of their scripts or to collect monitoring-centric metrics in their scripts.

 

For me, when working in places with good script source control like a Git I have built automations where the latest version of the scripts is just inserted directly into the SAM DB.  Not sure how into the weeds you want to go with it, but all the necessary verbs do exist where you could automate the whole process of creating scripts in the repository, have that kick off a script that goes into SAM and creates a corresponding powershell component monitor with the script body being set from what's in your repo, or updating the existing component to reflect any script changes.  Within 1-2 polling cycles all the new version of the script will be in effect.

 

Getting it all to work requires a pretty strong understanding of the Orion API verbs and the SQL table relationships unfortunately, but it can be done.

Re: Monitoring drivers status for Desktops

0
0

Normally nothing in SW is checking for those kinds of things, but as a catch all you can usually write a powershell script to identify anything you want and have SAM run that powershell and store the results.

Re: export automatically the report on orion solarwinds

Re: Error in SSL Certificate Verification

Re: AVAILABILITY QUERY IS DROPPING DATA

0
0

What is your detailed data retention setting?  The first think that I would expect to skew your numbers is the weekly roll up, since it doesn't look like you are doing any kind of weighting in your query to reflect the number of polls in each hourly/daily time slice.

Re: AVAILABILITY QUERY IS DROPPING DATA

0
0

mesverrum Are you referring to "Detailed Statistics Retention"? it's currently 15 days...

Is that the retention setting for availability? i thought the Daily Statistics Retention held node availability.

Re: How to assigned SNMPv3 credential set of a node ?

0
0

A SWQL query like this would help you start taking a peek at which credentials are assigned to your nodes:

 

SELECT TOP 1000    n.NodeID, -- From nodes    n.IPAddress,    n.Caption,    s.NodeSettingID, -- From settings    s.Description,    s.SettingName,    s.SettingValue,    c.ID AS CredentialID, -- From credentials    c.Name,    c.Description AS CredentialDescription
FROM Orion.Nodes n
INNER JOIN Orion.NodeSettings s ON s.NodeID = n.NodeID
LEFT JOIN Orion.Credential c ON c.ID = s.SettingValue
WHERE s.SettingName LIKE '%Credential%'
ORDER BY n.NodeID, s.NodeSettingID

 

You would need to filter that down more to look at just SNMP credentials.


NPM Interface Min/Max/Avg bps historical data

0
0

Hello,

 

With the Orion REST API, is there a way to pull historical data of Min/Max/Avg bps In/Out from an NPM Interface? For example, an ability to specify a Sampling Interval to get a list of data points over a specified Duration? The best I've found was querying for current In/Out bps and Max In/Out Bps for the day.


Thank you

Re: AVAILABILITY QUERY IS DROPPING DATA

0
0

All NPM statistics are subject to the same rollups, other modules sometimes have their own retention settings but they basically all fall under the same model

 

Node response time, loss, cpu, memory are all rolled up using the following process.

 

details - raw data, weight is 1, min/max/avg will all be the same value

 

hourly - take the raw values that have aged past the detailed retention period and average those raw values into hourly blocks, weighted by however many polls were taken for that object in that hour, min/max/avg will reflect the data that went into this 1 hour collection.

 

daily - take the hourly averages that have aged out of the hourly retention period and average those already averaged values into 24 hour blocks, weighted by the summed weight of all the hours that formed the block, min/max is actually the min/max of the previous set of hourly averages, this smooths out actual resource load peaks and kind of makes the min/max data useless for most purposes, average is calculated properly so at least that can be relied on.

 

If you are reporting on data that crosses these roll up periods I find it is extremely important to understand exactly how SW is managing the numbers when they roll ups happen.  I have long been an advocate for writing all my raw data points out to a separate data warehouse if the fine grained detail is considered really important for your org.





Latest Images