-
-
-
Configuration via Local Config Files
-
Config File Syntax
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Config File Syntax
uberAgent’s configuration file supports several advanced syntax features.
Windows
PATH_REGEX
PATH_REGEX
stands for a regex in which environment variables can be used. It is matched against a file system path. The following rules apply:
- Environment variables (enclosed in percent signs, e.g.,
%ProgramFiles%
) are expanded first, regex matching happens second. - Paths are specified as regular expressions.
- Backslashes must be escaped by prepending a second backslash.
- Matching is case-insensitive.
- Specifying only the file name without the full path works but is not recommended.
Agents on All Operating Systems
ConfigInclude
A @ConfigInclude
directive includes another configuration file. The other file is identified by name (without path) and must reside in the same directory as the configuration file including it. The additional platform
parameter may be used to conditionally include a file on the selected platform (Windows
or macOS
). Platform matching is case-insensitive.
Examples:
#Include on all platforms
@ConfigInclude other-file.conf
<!--NeedCopy-->
# Include on Windows only
@ConfigInclude windows-specific.conf platform=Windows
<!--NeedCopy-->
PROCESS_NAME_REGEX
PROCESS_NAME_REGEX
stands for a regex that is matched against a process name. The following rules apply:
- Backslashes must be escaped by prepending a second backslash.
- Matching is case-insensitive.
- Only the file name is used for matching, not the full path.
URL_REGEX
URL_REGEX
stands for a regex that is matched against a URL. The following rules apply:
- Backslashes must be escaped by prepending a second backslash.
- Matching is case-sensitive.
Format of the URLs matched against URL_REGEX
:
- Origin and path (without query segment), e.g.:
https://uberagent.com/download/
- Port numbers are stripped from the URL if they match the default port number.
platform=
All configuration stanzas can optionally be limited to a specific platform using the platform=
attribute.
- The platform is either Windows or macOS
- Stanzas without
platform=
are active on all supported platforms.
Example
[Timer platform=Windows]
...
[Timer platform=macOS]
...
<!--NeedCopy-->
Change configured setting values dynamically with uAQL
Some configuration settings are changeable using prefixed uAQL queries. This allows use cases where configuration values depend on environment variables, registry values or require string prefixes/suffixes. For now, the following configuration settings are changeable:
[Receiver]
- RESTToken
- TLSClientCertificate
- ElasticIngestPipeline
- Index
- Host
- Source
- PersistentOutputQueuePathWindows
- PersistentOutputQueuePathMacOS
- KafkaTopicName
Consider the following example to configure a prefix string in any KafkaTopicName setting.
KafkaTopicName = uaql(set(KafkaTopicName, concat('vastlimits_', KafkaTopicName)))
<!--NeedCopy-->
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.