我在一个名为的目录中有一些日志文件log
ls -l /var/log/
org1_app.log org2_app.log org1_perf.log org2_perf.log ...
现在我在主机服务器上设置了一个rsyslog client。以下是配置
# rsyslog configuration file
# For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html
# If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html
#### MODULES ####
# The imjournal module below is now used as a message source instead of imuxsock.
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal
#$ModLoad imklog # reads kernel messages (the same are read from journald)
#$ModLoad immark # provides --MARK-- message capability
# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514
# Provides TCP syslog reception
$ModLoad imtcp
$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
# Where to place auxiliary files
$WorkDirectory /var/lib/rsyslog
# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
# File syncing capability is disabled by default. This feature is usually not required,
# not useful and an extreme performance hit
#$ActionFileEnableSync on
# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf
# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging on
# File to store the position in the journal
$IMJournalStateFile imjournal.state
#### RULES ####
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages
# The authpriv file has restricted access.
authpriv.* /var/log/secure
# Log all the mail messages in one place.
mail.* -/var/log/maillog
# Log cron stuff
cron.* /var/log/cron
# Everybody gets emergency messages
*.emerg :omusrmsg:*
# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler
# Save boot messages also to boot.log
local7.* /var/log/boot.log
# ### begin forwarding rule ###
# The statement between the begining ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
#
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
#$ActionQueueFileName fwdRule1 # unique name prefix for spool files
#$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
#$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
#$ActionQueueType LinkedList # run asynchronously
#$ActionResumeRetryCount -1 # infinite retries if host is down
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
#*.* @@remote-host:514
# ### end of the forwarding rule ###
#*.info;mail.none;authpriv.none;cron.none @@xx.xx.xx.xx:514
$ModLoad imfile
$InputFileName /var/log/org*.log
$InputFileTag dev-log
$InputFileStateFile stat-dev-log
$InputFileSeverity error
$InputFileFacility local3
$InputFilePollInterval 10
$InputRunFileMonitor
local3.* @@xx.xx.xx.xx:514
重新启动rsyslog后，日志正在远程服务器内部发送和接收/var/log/messages
但问题是所有这些日志都混在一起了。我想要的是，每个日志文件都应该在远程服务器中单独创建，然后将后续日志添加到相应的日志文件中。
我确实查找了一些资源，但找不到任何能满足我要求的答案。我找到的最接近的答案是这个答案https://stackoverflow.com/questions/59861378/issue-with-multiple-logs-files-forwarding-with-rsyslog但它涉及手动定义每个日志文件，但在我的情况下会有许多日志文件，我无法手动定义文件中的每一个rsyslog.conf。
如何确保多个日志文件数据不会混合在一起，/var/log/messages而是为每个日志文件创建一个单独的文件，并将后续更新放入相应的文件中？
答案1
（简单的答案，但我还不能评论）你可以尝试更多的标记https://www.gilesorr.ca/blog/rsyslog-intermediate-local.html或查看过滤条件：https://www.rsyslog.com/doc/master/configuration/filters.html