Limiting the Scope of scrutinize Data Collection
scrutinize
provides several options that let you narrow scope of the data collection, to reduce output size and improve performance:
- Limit the time span of collected data.
- Limit the amount of collected data.
- Limit collection to specific cluster nodes.
- Specify the type of content to collect.
- Exclude types of content.
You can use these options singly or in combination, to achieve the desired level of granularity.
Limiting the Time Span of Collected Data
You can use scrutinize
--begin
and --end
options together or separately to limit the time frame of diagnostic data that is collected from vertica.log
and editor.log
:
--begin
specifies to collect log data from the specified begin time to the specified end time or log end.--end
specifies to collect data from the specified begin time or log start to the specified end time.
You can specify begin and end time arguments as offsets from the current time or as absolute times:
Offset time format: | ' Dd Hh Mm Ss 'For example: '3d2h1m' |
Absolute time format: | 'YYYY-MM-DD HH:MM:SS 'For example: '2014-01-02 13:29:59' |
For example:
$ scrutinize --begin='2014-01-01 00:00:00' --end='2014-01-07 23:59:59'
$ scrutinize --begin='2014-01-01 00:00:00'
$ scrutinize --end='2014-01-07 23:59:59'
$ scrutinize --begin='2014-09-23 00:00:00' --end='1d''
Limiting the Amount of Collected Data
Two options let you limit how much data scrutinize
collects:
--log-limit=limit |
Limits how much data is collected from Vertica logs, where limit specifies, in gigabytes, how much log data to collect, starting from the most recent log entry. By default, 1 GB of log data is collected. For example, the following command specifies to collect 4 GB of log data: $ scrutinize --log-limit=4 |
--include_gzlogs=num-files
|
Specifies to include num-files rotated log files (
By default, For example the following command specifies to collect two rotated log files: $ scrutinize --include_gzlogs=2 |
Limiting Collection to Specific Cluster Nodes
By default, scrutinize
collects data from all cluster nodes. You can specify that scrutinize
collect from individual nodes in two ways:
--local_diags
|
Specifies to collect diagnostics only from the host on which scrutinize was invoked. |
--hosts=host-list
|
Specifies to collect diagnostics only from the hosts specified in host-list, where host-list is a comma-separated list of IP addresses or host names. Example: $ scrutinize -n host_1,host_2,host_3 $ scrutinize --hosts=127.0.0.1,host_3,host_1 |
Specifying the Type of Content to Collect
scrutinize
provides several options that let you specify the type of data to collect:
--diag-dump
|
Limits the collection to database design, system tables, and Data Collector tables. Use this option to collect data to analyze system performance. |
--diagnostics
|
Limits the collection to log file data and output from commands that are run against Vertica and its host system. Use this option to collect data to evaluate unexpected behavior in your Vertica system. |
--type=type
|
Specifies the type of diagnostics collection to perform, where type can be one of the following arguments:
|
--tasks=tasks
|
Specifies that Note: Use this option only in consultation with Vertica Customer Support |
Excluding Types of Content
scrutinize
provides two options that let you specify types of data to exclude from its collection:
--vsql-off
|
Excludes
|
--exclude=tasks
|
Excludes one or more types of tasks from the diagnostics collection, where tasks is a comma-separated list of the tasks to exclude. Note: This option is typically used only in consultation with your Vertica Customer Support contact. Specify the tasks to exclude with the following case-insensitive arguments :
|