The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Source string Source string

527/10000 · 527

This translation is currently locked.

English Actions
~]#{nbsp}pass:quotes[`systemctl enable rsyslog`]
Your log server is now configured to receive and store log files from the other systems in your environment.
Using The New Template Syntax on a Logging Server
Rsyslog 7 has a number of different templates styles. The string template most closely resembles the legacy format. Reproducing the templates from the example above using the string format would look as follows:
template(name="TmplAuthpriv" type="string"
string="/var/log/remote/auth/%HOSTNAME%/%PROGRAMNAME:::secpath-replace%.log"
)
template(name="TmplMsg" type="string"
string="/var/log/remote/msg/%HOSTNAME%/%PROGRAMNAME:::secpath-replace%.log"
)
These templates can also be written in the list format as follows:
template(name="TmplAuthpriv" type="list") {
constant(value="/var/log/remote/auth/")
property(name="hostname")
constant(value="/")
property(name="programname" SecurePath="replace")
constant(value=".log")
}
template(name="TmplMsg" type="list") {
constant(value="/var/log/remote/msg/")
property(name="hostname")
constant(value="/")
property(name="programname" SecurePath="replace")
constant(value=".log")
}
This template text format might be easier to read for those new to rsyslog and therefore can be easier to adapt as requirements change.
To complete the change to the new syntax, we need to reproduce the module load command, add a rule set, and then bind the rule set to the protocol, port, and ruleset:
module(load="imtcp")
ruleset(name="remote1"){
authpriv.* action(type="omfile" DynaFile="TmplAuthpriv")
*.info;mail.none;authpriv.none;cron.none action(type="omfile" DynaFile="TmplMsg")
}
input(type="imtcp" port="514" ruleset="remote1")
Using Rsyslog Modules
indexterm:[rsyslog,modules] Due to its modular design, [application]*rsyslog* offers a variety of _modules_ which provide additional functionality. Note that modules can be written by third parties. Most modules provide additional inputs (see *Input Modules* below) or outputs (see *Output Modules* below). Other modules provide special functionality specific to each module. The modules may provide additional configuration directives that become available after a module is loaded. To load a module, use the following syntax:
$ModLoad _MODULE_
where [option]`$ModLoad` is the global directive that loads the specified module and _MODULE_ represents your desired module. For example, if you want to load the Text File Input Module ([command]#imfile#) that enables [application]*rsyslog* to convert any standard text files into syslog messages, specify the following line in the `/etc/rsyslog.conf` configuration file:
$ModLoad imfile
[application]*rsyslog* offers a number of modules which are split into the following main categories:
Input Modules — Input modules gather messages from various sources. The name of an input module always starts with the `im` prefix, such as [command]#imfile# and [command]#imjournal#.
Output Modules — Output modules provide a facility to issue message to various targets such as sending across a network, storing in a database, or encrypting. The name of an output module always starts with the `om` prefix, such as [command]#omsnmp#, [command]#omrelp#, and so on.
Parser Modules — These modules are useful in creating custom parsing rules or to parse malformed messages. With moderate knowledge of the C programming language, you can create your own message parser. The name of a parser module always starts with the `pm` prefix, such as [command]#pmrfc5424#, [command]#pmrfc3164#, and so on.
Message Modification Modules — Message modification modules change content of syslog messages. Names of these modules start with the `mm` prefix. Message Modification Modules such as [command]#mmanon#, [command]#mmnormalize#, or [command]#mmjsonparse# are used for anonymization or normalization of messages.
String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by [application]*rsyslog*. For more information on templates, see xref:Viewing_and_Managing_Log_Files.adoc#s2-Templates[Templates]. The name of a string generator module always starts with the `sm` prefix, such as [command]#smfile# or [command]#smtradfile#.
Library Modules — Library modules provide functionality for other loadable modules. These modules are loaded automatically by [application]*rsyslog* when needed and cannot be configured by the user.
A comprehensive list of all available modules and their detailed description can be found at link:++https://www.rsyslog.com/doc/rsyslog_conf_modules.html/++[https://www.rsyslog.com/doc/rsyslog_conf_modules.html].
Note that when [application]*rsyslog* loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
Importing Text Files
The Text File Input Module, abbreviated as [command]#imfile#, enables [application]*rsyslog* to convert any text file into a stream of syslog messages. You can use [command]#imfile# to import log messages from applications that create their own text file logs. To load [command]#imfile#, add the following into `/etc/rsyslog.conf`:
$ModLoad imfile
$InputFilePollInterval _int_

Loading…

User avatar None

Source string added
indexterm:[rsyslog,modules] Due to its modular design, [application]*rsyslog* offers a variety of _modules_ which provide additional functionality. Note that modules can be written by third parties. Most modules provide additional inputs (see *Input Modules* below) or outputs (see *Output Modules* below). Other modules provide special functionality specific to each module. The modules may provide additional configuration directives that become available after a module is loaded. To load a module, use the following syntax:
4 years ago
Browse all string changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Multiple failing checks

Following checks are failing:
Consecutive duplicated words: Indonesian, Indonesian, Chinese (Simplified Han script)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/monitoring-and-automation/Viewing_and_Managing_Log_Files.adoc:1284
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/f32/pages/monitoring-and-automation/Viewing_and_Managing_Log_Files.pot, string 408