Administration
Also available as:
PDF
loading table of contents...

Understanding Global Configuration

Global configurations are applied to all data sources as opposed to other configurations that are applied to a specific sensor. For example, every message from every sensor is validated against global configuration rules.

The following is an index of the global configuration properties and their associated Apache Ambari properties if they are managed by Ambari.

[Important]Important

Any property that is managed by Ambari should only be modified via Ambari. Otherwise, when you restart a service, Ambari might overwrite your updates. For more information, see Updating Properties.

Table 3.1. Global Configuration Properties

Property NameSubsystemTypeAmbari Property
es.clusternameIndexingStringes_cluster_name
es.ipIndexingStringes_hosts
es.portIndexingStringes_port
es.date.formatIndexingStringes_date_format
fieldValidationsParsingObjectN/A
parser.error.topicParsingStringN/A
stellar.function.pathsStellarCSV StringN/A
stellar.function.resolver.includesStellarCSV StringN/A
stellar.function.resolver.excludesStellarCSV StringN/A
profiler.period.durationProfilerIntegerprofiler_period_duration
profiler.period.duration.unitsProfilerStringprofiler_period_units
update.hbase.tableREST/IndexingStringupdate_hbase_table
update.hbase.cfREST-IndexingStringupdate_hbase_cf
geo.hdfs.fileEnrichmentStringgeo_hdfs_file

You can also create a validation using Stellar. The following validation uses Stellar to validate an ip_src_addr similar to the "validation":"IP"" example above:

"fieldValidations" : [
              {
                "validation" : "STELLAR",
                "config" : {
                    "condition" : "IS_IP(ip_src_addr, 'IPV4')"
                           }
              } 
                       ]