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: Monitoring drivers status for Desktops
↧
↧
Re: export automatically the report on orion solarwinds
You can generate reports from Orion on a schedule. See Generate reports in the Orion Platform on a schedule for additional details. You can also use the Orion SDK (https://github.com/solarwinds/OrionSDK) to retrieve tons of information from Orion in a variety of ways (REST API, PowerShell, Python). You could use that information to produce reports.
↧
Re: Error in SSL Certificate Verification
See Enabling SSL Certificate Verification for the SDK for details about this behavior. If you omit the verify parameter, the default behavior will be to skip SSL certificate verification, which is convenient since Orion uses a self-signed certificate that won't be trusted by default. The library is open source, so you can see the code for SwisClient here: https://github.com/solarwinds/orionsdk-python/blob/master/orionsdk/swisclient.py
↧
Re: AVAILABILITY QUERY IS DROPPING DATA
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
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 ?
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
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
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.
↧
Re: AVAILABILITY QUERY IS DROPPING DATA
that makes sense. Where are the raw data points located in the database?
↧
↧
Re: AVAILABILITY QUERY IS DROPPING DATA
You would use the same responsetime view are you are looking at, IIRC there is a column called archive i believe will be 0 for raw data, then it increments up as they go through the various phases of rollup.
↧
More Pages to Explore .....
