-
Notifications
You must be signed in to change notification settings - Fork 3
Configuration
queryda can be configured either via commandline or using a JSON file (supplied via --configfile parameter). Both ways require to specify option groups with individual settings (e.g. for elasticsearch, for the reporters, for the validator). Example JSON files can be found in the jobs and example dirs.
The following options are currently available:
A name of your choice to identify this job. This will be used by the reporters to identitfy this individual call.
Settings for elasticsearch, expects the following madatory fields:
- host: where to find the elasticsearch host
- port: which port elasticsearch is running on
- index: the index name to send youe query to
- type: the document type to query
An elasticsearch query statement. Refer to the elasticsearch documentation for details about syntax and features. Should return a result set that contains the supplied fieldName to match against.
An elasticsearch aggregation statement. Refer to the elasticsearch documentation for details about syntax and features. Should return a result set that contains the supplied aggName to match against.
Settings for elasticsearch, expects the following madatory fields:
- host: where to find the cassandra host
- keyspace: which to use for queries
A Cassandra query statement. Refer to the cassandra documentation for details about syntax and features. Should return a result set that contains the supplied fieldName to match against.
A set of Parameters/Variable to be used by the CQL Query.
Validator(s) to compare the query results against. Expects an object with key/value pairs where key ist the name of the validator and value is the validator-specific configuration. See Validators for more details.
Reporter(s) to notify about alarms. Expects an object with key/value pairs where key ist the name of the reporter and value is the reporter-specific configuration. See Reporters for more details.
Name of JSON file to read config from. Expects main options as top-level properties (see example.json for a live example).