How to forward rsyslog logs from multiple locations to ELK and make it show in kibana?












0















rsyslog server template consideration for multiple remote hosts
---> link to previously answered question



@ meuh, I find this post very useful as am currently working on this configuration.



I have done the steps which is mentioned above and its working fine. thanks for that



My case is, I have ELK setup were rsyslog forwards the logs to it.



My templates are,




$template
templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



$template mylogsec,"/data01/RemoteLogs/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



if $fromhost startswith "10.100.10" then ?templmesg



& stop



if $fromhost startswith "10.100.112" then ?mylogsec



& stop




so I have two locations were logs are stored



Because of multiple locations of log storages like DLF and Logserver. Kibana from (ELK) does not show logs which is received from rsyslog. It only reads from one location of logs that is from DLF/ dir and not from Logserver



Now am stuck and dont know "How to forward rsyslog logs from multiple locations to ELK and make it show in kibana?" or "is there any specific configuration in rsyslog that i need to work out?"



below is the 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 bellow 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

$template templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"
$template mylogsec,"/data01/RemoteLogs/DLF/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"

#if $fromhost startswith "10.100.10" then ?templmesg
#& stop
if $fromhost startswith "10.100.112" then ?mylogsec
& stop

local0.* ?templmesg
local1.* ?templmesg
local2.* ?templmesg
local3.* ?templmesg
local4.* ?templmesg
local5.* ?templmesg
local6.* ?templmesg


template(name="json-template"
type="list") {
constant(value="{")
constant(value=""@timestamp":"") property(name="timereported" dateFormat="rfc3339")
constant(value="","@version":"1")
constant(value="","message":"") property(name="msg" format="json")
constant(value="","sysloghost":"") property(name="hostname")
constant(value="","severity":"") property(name="syslogseverity-text")
constant(value="","facility":"") property(name="syslogfacility-text")
constant(value="","programname":"") property(name="programname")
constant(value="","procid":"") property(name="procid")
constant(value=""}n")
}


# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
#
#$createDirs on

*.info;mail.none;authpriv.none;cron.none;local0.none;local1.none;local2.none;local3.none;local4.none;local5.none;local6.none ?templmesg

# The authpriv file has restricted access.
authpriv.* ?templmesg

# Log all the mail messages in one place.
mail.* ?templmesg


# Log cron stuff
cron.* ?templmesg

# 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.* ?templmesg


# ### begin forwarding rule ###
# The statement between the begin ... 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
*.* @10.100.10.30:10514;json-template
# ### end of the forwarding rule ###









share|improve this question









New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

    – Haxiel
    yesterday











  • No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

    – vignesh9816
    21 hours ago













  • Okay, are the forwarding rules written before the configuration snippet you have shown above?

    – Haxiel
    21 hours ago











  • yes, the forwarding rules are written before the configuration!

    – vignesh9816
    21 hours ago











  • Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

    – Haxiel
    21 hours ago
















0















rsyslog server template consideration for multiple remote hosts
---> link to previously answered question



@ meuh, I find this post very useful as am currently working on this configuration.



I have done the steps which is mentioned above and its working fine. thanks for that



My case is, I have ELK setup were rsyslog forwards the logs to it.



My templates are,




$template
templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



$template mylogsec,"/data01/RemoteLogs/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



if $fromhost startswith "10.100.10" then ?templmesg



& stop



if $fromhost startswith "10.100.112" then ?mylogsec



& stop




so I have two locations were logs are stored



Because of multiple locations of log storages like DLF and Logserver. Kibana from (ELK) does not show logs which is received from rsyslog. It only reads from one location of logs that is from DLF/ dir and not from Logserver



Now am stuck and dont know "How to forward rsyslog logs from multiple locations to ELK and make it show in kibana?" or "is there any specific configuration in rsyslog that i need to work out?"



below is the 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 bellow 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

$template templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"
$template mylogsec,"/data01/RemoteLogs/DLF/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"

#if $fromhost startswith "10.100.10" then ?templmesg
#& stop
if $fromhost startswith "10.100.112" then ?mylogsec
& stop

local0.* ?templmesg
local1.* ?templmesg
local2.* ?templmesg
local3.* ?templmesg
local4.* ?templmesg
local5.* ?templmesg
local6.* ?templmesg


template(name="json-template"
type="list") {
constant(value="{")
constant(value=""@timestamp":"") property(name="timereported" dateFormat="rfc3339")
constant(value="","@version":"1")
constant(value="","message":"") property(name="msg" format="json")
constant(value="","sysloghost":"") property(name="hostname")
constant(value="","severity":"") property(name="syslogseverity-text")
constant(value="","facility":"") property(name="syslogfacility-text")
constant(value="","programname":"") property(name="programname")
constant(value="","procid":"") property(name="procid")
constant(value=""}n")
}


# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
#
#$createDirs on

*.info;mail.none;authpriv.none;cron.none;local0.none;local1.none;local2.none;local3.none;local4.none;local5.none;local6.none ?templmesg

# The authpriv file has restricted access.
authpriv.* ?templmesg

# Log all the mail messages in one place.
mail.* ?templmesg


# Log cron stuff
cron.* ?templmesg

# 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.* ?templmesg


# ### begin forwarding rule ###
# The statement between the begin ... 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
*.* @10.100.10.30:10514;json-template
# ### end of the forwarding rule ###









share|improve this question









New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

    – Haxiel
    yesterday











  • No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

    – vignesh9816
    21 hours ago













  • Okay, are the forwarding rules written before the configuration snippet you have shown above?

    – Haxiel
    21 hours ago











  • yes, the forwarding rules are written before the configuration!

    – vignesh9816
    21 hours ago











  • Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

    – Haxiel
    21 hours ago














0












0








0








rsyslog server template consideration for multiple remote hosts
---> link to previously answered question



@ meuh, I find this post very useful as am currently working on this configuration.



I have done the steps which is mentioned above and its working fine. thanks for that



My case is, I have ELK setup were rsyslog forwards the logs to it.



My templates are,




$template
templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



$template mylogsec,"/data01/RemoteLogs/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



if $fromhost startswith "10.100.10" then ?templmesg



& stop



if $fromhost startswith "10.100.112" then ?mylogsec



& stop




so I have two locations were logs are stored



Because of multiple locations of log storages like DLF and Logserver. Kibana from (ELK) does not show logs which is received from rsyslog. It only reads from one location of logs that is from DLF/ dir and not from Logserver



Now am stuck and dont know "How to forward rsyslog logs from multiple locations to ELK and make it show in kibana?" or "is there any specific configuration in rsyslog that i need to work out?"



below is the 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 bellow 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

$template templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"
$template mylogsec,"/data01/RemoteLogs/DLF/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"

#if $fromhost startswith "10.100.10" then ?templmesg
#& stop
if $fromhost startswith "10.100.112" then ?mylogsec
& stop

local0.* ?templmesg
local1.* ?templmesg
local2.* ?templmesg
local3.* ?templmesg
local4.* ?templmesg
local5.* ?templmesg
local6.* ?templmesg


template(name="json-template"
type="list") {
constant(value="{")
constant(value=""@timestamp":"") property(name="timereported" dateFormat="rfc3339")
constant(value="","@version":"1")
constant(value="","message":"") property(name="msg" format="json")
constant(value="","sysloghost":"") property(name="hostname")
constant(value="","severity":"") property(name="syslogseverity-text")
constant(value="","facility":"") property(name="syslogfacility-text")
constant(value="","programname":"") property(name="programname")
constant(value="","procid":"") property(name="procid")
constant(value=""}n")
}


# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
#
#$createDirs on

*.info;mail.none;authpriv.none;cron.none;local0.none;local1.none;local2.none;local3.none;local4.none;local5.none;local6.none ?templmesg

# The authpriv file has restricted access.
authpriv.* ?templmesg

# Log all the mail messages in one place.
mail.* ?templmesg


# Log cron stuff
cron.* ?templmesg

# 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.* ?templmesg


# ### begin forwarding rule ###
# The statement between the begin ... 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
*.* @10.100.10.30:10514;json-template
# ### end of the forwarding rule ###









share|improve this question









New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












rsyslog server template consideration for multiple remote hosts
---> link to previously answered question



@ meuh, I find this post very useful as am currently working on this configuration.



I have done the steps which is mentioned above and its working fine. thanks for that



My case is, I have ELK setup were rsyslog forwards the logs to it.



My templates are,




$template
templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



$template mylogsec,"/data01/RemoteLogs/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"



if $fromhost startswith "10.100.10" then ?templmesg



& stop



if $fromhost startswith "10.100.112" then ?mylogsec



& stop




so I have two locations were logs are stored



Because of multiple locations of log storages like DLF and Logserver. Kibana from (ELK) does not show logs which is received from rsyslog. It only reads from one location of logs that is from DLF/ dir and not from Logserver



Now am stuck and dont know "How to forward rsyslog logs from multiple locations to ELK and make it show in kibana?" or "is there any specific configuration in rsyslog that i need to work out?"



below is the 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 bellow 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

$template templmesg,"/data01/RemoteLogs/DLF/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"
$template mylogsec,"/data01/RemoteLogs/DLF/Logserver/%$YEAR%/%$MONTH%/%HOSTNAME%/%HOSTNAME%-%$DAY%-%$MONTH%-%$YEAR%.log"

#if $fromhost startswith "10.100.10" then ?templmesg
#& stop
if $fromhost startswith "10.100.112" then ?mylogsec
& stop

local0.* ?templmesg
local1.* ?templmesg
local2.* ?templmesg
local3.* ?templmesg
local4.* ?templmesg
local5.* ?templmesg
local6.* ?templmesg


template(name="json-template"
type="list") {
constant(value="{")
constant(value=""@timestamp":"") property(name="timereported" dateFormat="rfc3339")
constant(value="","@version":"1")
constant(value="","message":"") property(name="msg" format="json")
constant(value="","sysloghost":"") property(name="hostname")
constant(value="","severity":"") property(name="syslogseverity-text")
constant(value="","facility":"") property(name="syslogfacility-text")
constant(value="","programname":"") property(name="programname")
constant(value="","procid":"") property(name="procid")
constant(value=""}n")
}


# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
#
#$createDirs on

*.info;mail.none;authpriv.none;cron.none;local0.none;local1.none;local2.none;local3.none;local4.none;local5.none;local6.none ?templmesg

# The authpriv file has restricted access.
authpriv.* ?templmesg

# Log all the mail messages in one place.
mail.* ?templmesg


# Log cron stuff
cron.* ?templmesg

# 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.* ?templmesg


# ### begin forwarding rule ###
# The statement between the begin ... 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
*.* @10.100.10.30:10514;json-template
# ### end of the forwarding rule ###






centos rsyslog kibana






share|improve this question









New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 12 hours ago









Haxiel

1,733410




1,733410






New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









vignesh9816vignesh9816

12




12




New contributor




vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






vignesh9816 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

    – Haxiel
    yesterday











  • No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

    – vignesh9816
    21 hours ago













  • Okay, are the forwarding rules written before the configuration snippet you have shown above?

    – Haxiel
    21 hours ago











  • yes, the forwarding rules are written before the configuration!

    – vignesh9816
    21 hours ago











  • Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

    – Haxiel
    21 hours ago



















  • Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

    – Haxiel
    yesterday











  • No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

    – vignesh9816
    21 hours ago













  • Okay, are the forwarding rules written before the configuration snippet you have shown above?

    – Haxiel
    21 hours ago











  • yes, the forwarding rules are written before the configuration!

    – vignesh9816
    21 hours ago











  • Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

    – Haxiel
    21 hours ago

















Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

– Haxiel
yesterday





Welcome to the U&L SE. How are you sending the data from the log file to Elasticsearch? Do you have Filebeat configured?

– Haxiel
yesterday













No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

– vignesh9816
21 hours ago







No Filebeat configured, it is just using UDP ports that is configured to listen and forward remote logs, if you require i can give you the configuration of rsyslog, elasticsearch,logstash and kibana

– vignesh9816
21 hours ago















Okay, are the forwarding rules written before the configuration snippet you have shown above?

– Haxiel
21 hours ago





Okay, are the forwarding rules written before the configuration snippet you have shown above?

– Haxiel
21 hours ago













yes, the forwarding rules are written before the configuration!

– vignesh9816
21 hours ago





yes, the forwarding rules are written before the configuration!

– vignesh9816
21 hours ago













Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

– Haxiel
21 hours ago





Can you verify the steps you have completed against this blog post? It's written for Ubuntu, but the flow of messages should work the same way.

– Haxiel
21 hours ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






vignesh9816 is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494772%2fhow-to-forward-rsyslog-logs-from-multiple-locations-to-elk-and-make-it-show-in-k%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








vignesh9816 is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















vignesh9816 is a new contributor. Be nice, and check out our Code of Conduct.













vignesh9816 is a new contributor. Be nice, and check out our Code of Conduct.












vignesh9816 is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494772%2fhow-to-forward-rsyslog-logs-from-multiple-locations-to-elk-and-make-it-show-in-k%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux