I'm using a Fleet Agent with Custom Logs integration, but the path to the log file is dynamic and dependent on the name of the agent host -- so I have "C:\logs\${host.hostname}\elastic*.log" as the log file path. However, when I try to use a variable in the path like this, it fails to initialize it. Is this the correct format for including a variable in the path? It works perfectly when I use a static path like "C:\logs\my_host_name\elastic*.log".
With the ${host.hostname} variable in use, I only see in the filebeat logs are the default log files being configured, but no errors about my custom path.
probably the Elastic Agent does not support the use of variables like ${host.hostname} in the file paths for the Custom Logs integration.
If all your logs are in subdirectories of C:\logs\ , you could use a path like C:\logs\*\elastic*.log to collect all matching log files from all subdirectories.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.