LAT Reference
LAT Service Configuration
data pipelines are now the preferred method for loading data into the ocient system for details, see load data docid\ xq0tg7yph vn62uwufibu the lat service is configurable using service configuration this configuration is derived from three sources, with the following precedence order environment variables properties file code defaults configuration file backup when you install a new lat instance or upgrade the existing instance, lat creates a backup file of the /etc/lat/lat conf as /etc/lat/override conf and creates a new version of the /etc/lat/lat conf file the /etc/lat/overrirde conf file does not control the lat configuration if you made prior changes to lat conf , you must review override conf and add any custom values into the revised lat conf environment variables lat default workers default number of workers used by a newly configured pipeline 275,379 false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat shutdown duration duration, in milliseconds, to wait prior to termination on shutdown false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat udt path directory containing zero or more user defined transformation (udt) jars ensure that the specified path can be accessed by the lat (e g , {{centos}} does not allow the lat to access the home directory of an administrative user) false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api port rest api and metrics port false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat data path path to the lat data directory this directory is used to store persistent data related to pipelines ( pipeline/ ) and sinks ( sink/ ) in almost all cases, using the lat client command line interface docid\ xpvlz0ewuxmgynxvxz jb is preferred over editing the files in this directory manually ensure that the specified path can be accessed by the lat (e g , centos does not allow the lat to access the home directory of an administrative user) false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat auto start on lat startup, automatically starts running a pipeline if one is present this only supports pipelines with {{kafka}} sources; file sources will not automatically start even if this configuration is set to true false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat allow log original records allow the original records that are being loaded to be logged when errors occur this setting must be enabled for log original records to be enabled this setting only affects pipelines that log errors to the error log file false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat max retrievable errors a limit on the number of errors that you can retrieve using the pipeline errors command of the lat client false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api proxy host api proxy host for {{okta}} authorization requests false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api proxy port api proxy port for okta authorization requests false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api oauth domain okta authorization domain false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api oauth endpoints a list of lat api endpoints that okta should apply authentication on to override, provide a comma delimited list, e g , /endpoint1,/endpoint2,/endpoint3 false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api oauth server okta authorization server false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat api cert path api cert file path ensure that the specified path can be accessed by the lat (e g , {{centos}} does not allow the lat to access the home directory of an administrative user) false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat dns cache ttl the time to live (ttl) in seconds that the lat should use for its dns cache this configuration is only supported as an environment variable or as default 269,379 false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat memory maximum jvm ® heap memory this configuration is only supported as an environment variable or as default when running the lat through the provided package service file or through the provided lat sh script if directly running the jar jvm heap memory should be set through command line arguments false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type lat memory direct maximum jvm direct memory this configuration is only supported as an environment variable or as default when running the lat through the provided package service file or through the provided lat sh script if directly running the jar jvm heap memory should be set through command line arguments 289,360 false left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type override environment variables the recommended way to manage the production service configuration when lat is running as a daemon is using environment variables or the /etc/systemd/system/lat service d/override conf file to override lat environment variables as a systemd service, there are two recommended commands that edit the etc/systemd/system/lat service d/override conf file run sudo vim etc/systemd/system/lat service d/override conf or sudo systemctl edit lat insert the environment variables to override in the file save and exit the editor configuration file example \[service] environment=lat memory direct=200g environment=lat memory=200g related links ingest data with legacy lat reference docid\ tt6tfoulap0mt aycm2ka lat packaging and installation docid 4gawr9v 2cqsdff9an6t