Welcome to docs.opsview.com

Differences

This shows you the differences between two versions of the page.

opsview4.6:systemsurvey [2014/09/09 12:19] (current)
Line 1: Line 1:
 +====== Opsview System Survey ======
 +To help us with software development and testing we have included a feature for collect some information about your Opsview system.
 +You can opt out of the survey by disabling the Include Survey check box in the System Preferences' Updates tab. You can click on the Display Survey Information button to show the information that would be sent back.
 +
 +Opsview uses the //check_opsview_update// plugin, which is defined in the //Opsview Updates// service check on new systems. You can add an argument to the plugin of ''--donotsendstats'' if you want the plugin to override the system preference setting and never send any statistical information back.
 +
 +**Note**: For MSP systems, the survey data is always sent, as required by the MSP contract.
 +
 +===== Update Information =====
 +The check_opsview_update plugin sends us the following information so it can check whether a new Opsview version is available:
 +
 +^Information^Explanation^
 +|The operating system type, version and architecture associated with your system.|This allows us to identify whether new software packages have been released for your system. We also use this data to identify the popularity of each operating system type and version. We use this when deciding when to deprecate support for a particular platform|
 +|Your current Opsview software version|So we can compare the software version you're running with the latest available version|
 +|A parameter defining what type of release should result in an alert|Whether you want to be warned of all new software releases or just major releases (only available for Opsview Enterprise versions)|
 +===== Survey Information =====
 +If the Opsview System Survey is enabled the check_opsview_update plugin will also send the following information back to us:
 +
 +^Information^Explanation^
 +|The unique ID number (UUID) associated with your Opsview system.|This is how we identify data collected from your system.  We use the [[http://search.cpan.org/dist/Data-UUID/UUID.pm|Data::UUID]] Perl module from [[http://www.cpan.org|CPAN]] to generate this ID. The UUID is anonymous and doesn't tell us anything about you. It will look something like this: 4162F712-1DD2-11B2-B17E-C09EFE1DC403|
 +|Anonymised Opsview host information.|This data is used to distinguish between multiple Opsview systems that may have the same UUID (due to migration of the Opsview database to different hardware). This uses the Opsview master's host name and creates an MD5 hash. It will look something like this: B21FC650D13482C1F3F362B834E8BC4A|
 +|The number of hosts configured on your system|This data is used for performance tuning and scalability testing|
 +|The number of contacts configured on your system|This data is used for performance tuning and scalability testing|
 +|The number of keywords configured on your system|This data is used for performance tuning and scalability testing|
 +|The number of current services on your system|This data is used for performance tuning and scalability testing|
 +|The number of service check results processed in the last hour|This data is used for performance tuning and scalability testing|
 +|The number of performance results processed in the last hour|This data is used for performance tuning and scalability testing|
 +|The number of slave clusters with the total number of nodes|This data is used for performance tuning and scalability testing|
 +|The number of CPUs on the Opsview master|This data is used for performance tuning and scalability testing|
 +|The amount of system memory available on the Opsview master|This data is used for performance tuning and scalability testing|
 +|The 15 minute system load average on the Opsview master|This data is used for performance tuning and scalability testing|
 +|The number of API sessions in the last day|This data is used for performance tuning and scalability testing|
 +|The average Opsview reload duration|This data is used for performance tuning and scalability testing|
 +|The average ODW import duration|Based on an average over the last day's worth of ODW imports. This data is used for performance tuning and scalability testing.|
 +|The number of logins over the last day|This data is used for performance tuning and scalability testing|
 +|Perl software version|This data is used for system testing|
 +|Whether a remote database server is being used|This data is used for performance tuning and scalability testing|
 +|Whether SNMP trap processing is enabled|This data is used for performance tuning and scalability testing|
 +|Whether ODW importing is enabled|This data is used for performance tuning and scalability testing|
 +|The Opsview instance id number|This data is used to group collected data|
 +|A list of web browser software used to access Opsview in the last month|This is identified by the 'user agent' parameter supplied by each web browser. Collecting information about your web browser software allows us to test against the right mix of browser types and versions|
Navigation
Print/export
Toolbox