- What are the Hardware Requirements?
- Can I upgrade to Statseeker 5.4 from any previous Statseeker version?
- How do I install/upgrade?
- Do the new data types consume licenses?
- Can I threshold/alert on custom data?
- How do I control which custom data is monitored?
- What is the impact of enabling QoS or Etherlike?
- How do I configure a trend or forecast report?
- What is the difference between trend and forecasts?
What are the Hardware Requirements?
These vary depending on the size of the network being monitored, see Hardware Requirements for details.
Can I upgrade to Statseeker 5.4 from any previous Statseeker version?
You can upgrade to Statseeker 5.4 from a Statseeker 5.3.x server. If you are updating from an earlier version, please contact Customer Service for assistance.
How do I install/upgrade?
Refer to the relevant documentation:
Do the new data types consume licenses?
There are no additional licensing costs associated with the CDT packages that have been rolled into the base product. If your Statseeker license has device and/or port licenses, then just like non-CDT licensing, every device and port monitored counts towards your licensed device and port limits. If entity licensing was previously applied to the CDT package contents, then it will no longer apply once you have upgraded your Statseeker server to v5.4 or above.
Can I threshold/alert on custom data?
Yes, thresholds and alerts are ‘data agnostic’ within Statseeker. All custom data counts and timeseries metrics can be used to configure thresholds and alerts.
How do I control which custom data is monitored?
By default, all devices on your network that Statseeker has been configured to monitor, will report all available data types when polled. You can configure Statseeker 5.4 to store and report on a subset of this data by selectively configuring Custom Data Type Ranges in the Administration Tool. See Custom Data Types for details.
What is the impact of enabling QoS or Etherlike?
QoS and EtherLike both poll significantly more objects per port than standard interface polling. This increased polling can increase server loads and disk usage, so QoS and Etherlike should:
- Only be enabled on important ports
- If QoS/EtherLike polling is required across all ports, the server hardware should be specified accordingly
Contact Support for more information, or if you would like assistance with establishing the hardware requirements to suit your needs.
How do I configure a trend or forecast report?
For details on configuring, and interpreting these reports, see:
What is the difference between trend and forecasts?
Trendline plotting, a common practice within statistical analysis, is used to identify a pattern or ‘trend’ being displayed by the data. The trendline works by plotting a ‘line-of-best-fit’ across all data points in the reporting period, the result being a single line representing the trend found within the data, with the slope of the line representing the direction of the trend. Trend reporting in Statseeker can be used to give an indication of the direction and rate of change for a statistic over the reporting period and into the future. This is particularly useful for capacity planning with regard to disk usage or link utilization.
Data forecasting is another example of advanced analytics which requires an unabridged data history in order to be accurate. Any product that averages your data over time cannot provide reliable data forecasting. Statseeker’s Data Forecasting analyses your data history and, from that analysis, models your data into the future.
Data forecasting provides you with valuable information that can be used when restructuring, or planning upgrades and additions to, your network infrastructure and configuration. Statseeker allows you to report on this predicted data for every metric that your network infrastructure shares with Statseeker, such as remaining datastore capacity, SDN health metrics, and link utilization.