{"id":1559,"date":"2026-01-01T21:26:51","date_gmt":"2026-01-01T21:26:51","guid":{"rendered":"https:\/\/b2bhostingclub.com\/blog\/?p=1559"},"modified":"2026-02-04T14:14:37","modified_gmt":"2026-02-04T14:14:37","slug":"how-to-monitor-linux-system-logs-with-logwatch","status":"publish","type":"post","link":"https:\/\/b2bhostingclub.com\/blog\/how-to-monitor-linux-system-logs-with-logwatch\/","title":{"rendered":"How To Monitor Linux System Logs with Logwatch"},"content":{"rendered":"
\n
\n
\n

Introduction<\/h2>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n
\n
\n

System logs contain valuable information about the activities and events occurring on your Linux server. However, manually reviewing these logs can be time-consuming and overwhelming. That’s where Logwatch comes in. Logwatch is a powerful log analysis and monitoring tool that automates the process of parsing and summarizing system logs, making it easier for system administrators to identify potential issues, security threats, and system performance trends. In this blog, we will explore the benefits of using Logwatch, its installation process, and how to customize its configuration to suit your monitoring needs. By the end, you’ll have a solid understanding of how Logwatch can help you gain insights into your system’s log data and keep your Linux server running smoothly.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

Benefits of Using Logwatch<\/h2>\n
Using Logwatch offers several benefits for monitoring system logs.<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n
\n
\n

Time Efficiency:<\/b>\u00a0Manually reviewing system logs can be a time-consuming task, especially when dealing with large log files or multiple servers. Logwatch automates this process by parsing and summarizing log data, providing concise and organized reports that highlight important events and trends. This saves administrators valuable time and allows them to focus on critical issues.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Centralized Log Analysis:<\/b>\u00a0Logwatch consolidates log data from various sources, such as system logs, application logs, and security logs, into a unified report. This centralized approach simplifies log analysis, making it easier to identify patterns, anomalies, and potential security threats across the system.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Quick Issue Identification:<\/b>\u00a0Logwatch provides a clear and concise summary of log events, highlighting any warnings, errors, or critical issues that require attention. By regularly reviewing Logwatch reports, administrators can promptly identify and address system problems, ensuring optimal performance and minimizing downtime.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Security Monitoring:<\/b>\u00a0System logs contain valuable information for detecting security incidents and unauthorized access attempts. Logwatch helps in monitoring and analyzing security logs, providing insights into potential security breaches, failed login attempts, suspicious activities, and other security-related events. This enables administrators to take proactive measures to enhance system security.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Customization and Flexibility:<\/b>\u00a0Logwatch offers a range of customization options to tailor the log monitoring process to specific requirements. Administrators can configure which log files to analyze, set alert thresholds, define report formats, and apply filters to focus on relevant log entries. This flexibility allows for fine-tuning the monitoring process and adapting it to the unique needs of the system.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Historical Analysis and Trend Identification:<\/b>\u00a0By maintaining a history of log reports, Logwatch enables administrators to analyze system performance trends over time. This helps in identifying recurring issues, monitoring resource usage patterns, and making informed decisions regarding system optimization and capacity planning.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

Monitor Linux System Logs with Logwatch<\/h2>\n
In this tutorial, we will use Ubuntu system for demonstration.<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

1. Install Logwatch and Sendmail<\/h3>\n
\n
\n
\n

Before the installation, log into the server as the root user, input the password as prompted, and then update your system.<\/p>\n<\/div>\n<\/div>\n

\n
\n
sudo -i\r\napt update && apt upgrade<\/pre>\n<\/div>\n<\/div>\n
\n
\n
Then, install Logwatch and Sendmail.<\/p>\n<\/div>\n<\/div>\n
\n
\n
apt install logwatch sendmail<\/pre>\n<\/div>\n<\/div>\n
\n
\n
Sendmail<\/b>\u00a0is a server application that gives businesses a way to send email using the Simple Mail Transfer Protocol (SMTP). It\u2019s typically installed on an email server on a dedicated machine that accepts outgoing email messages and then sends these messages to the defined recipient. This application will help send reports or digests to your email if it’s well configured.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
2. Configure Logwatch<\/h3>\n
\n
\n
\n
The default configuration file for Logwatch is located at “\/usr\/share\/logwatch\/default.conf\/logwatch.conf”. Use any text editor to modify the content. Here, we will use the nano text editor.<\/p>\n<\/div>\n<\/div>\n
\n
\n
nano \/usr\/share\/logwatch\/default.conf\/logwatch.conf<\/pre>\n<\/div>\n<\/div>\n
\n
\n
2.1 Log Directories<\/b><\/p>\n<\/div>\n<\/div>\n
\n
\n
LogDir<\/b>\u00a0defines directories containing log files that you want Logwatch to analyze. By default, Logwatch goes through all the logs located within the \/var\/log directory and generates reports on your system’s log activity. However, if you have logs in other directories, such as custom application logs or website logs that need to be reported, you can add them to Logwatch by including additional “LogDir” lines as below.<\/p>\n<\/div>\n<\/div>\n
\n
\n
TmpDir<\/b>\u00a0specifies the directory where Logwatch stores temporary files and working files during its execution. Although this can be any directory you want, we will keep the default value \/var\/cache\/logwatch. You\u2019ll have to manually create this directory when we finish editing this file.<\/p>\n<\/div>\n<\/div>\n
\n
\n
\"Open<\/div>\n<\/div>\n<\/div>\n
\n
\n
2.2 Output and Format Configuration<\/b><\/p>\n<\/div>\n<\/div>\n
\n
\n
Output<\/b>\u00a0and\u00a0Format<\/b>\u00a0determines the destination or method for delivering Logwatch reports. There are several options available for the “Output” setting:<\/p>\n<\/div>\n<\/div>\n
\n
\n
-stdout:<\/b>\u00a0Logwatch reports are displayed on the standard output (console) when Logwatch is executed. This is the default option, and it’s useful for immediate viewing of reports on demand or for capturing the output for further processing or redirection.
\n-mail:<\/b>\u00a0Logwatch reports are sent via email to the address specified in the Logwatch configuration. This option allows you to receive Logwatch reports directly in your email inbox. To use this feature, make sure that your system has a working mail transfer agent (MTA) configured, such as Sendmail or Postfix, to handle outgoing emails.
\n-file:<\/b>\u00a0Logwatch reports are saved to a file. You can specify the file path and name using the File option in the Logwatch configuration. This option is useful if you want to store the reports for later reference or for automated processing.
\n-text:<\/b>\u00a0Logwatch generates reports in a simple, text-based format that is easy to read and parse. This format is suitable for viewing reports in a console or terminal window, storing them as plain text files, or integrating them with other text-based tools or systems.
\n-html:<\/b>\u00a0Logwatch reports are generated in HTML format. This is suitable for viewing reports in a web browser or embedding them in web pages.
\n-html-noencode:<\/b>\u00a0Similar to the html option, but it doesn’t encode special characters in the HTML output. This option might be necessary for compatibility with certain systems or applications.<\/p>\n<\/div>\n<\/div>\n
\n
2.2.1 If you need to immediately view reports in a console or terminal window, choose the stdout and text options.<\/div>\n
\n
\"Choose<\/div>\n<\/div>\n<\/div>\n
\n
2.2.2 If you would like Logwatch to send the report to a specific email, configure the following fields.<\/div>\n
<\/div>\n<\/div>\n
\n
\n
Output = mail<\/b>
\nFormat = html<\/b>\u00a0#Choose the format (html or text) you prefer. In this case, we choose html.
\nMailTo = your email address<\/b>\u00a0#Can be a valid email address or local account user. If using a local account use, you can specify the MailTo = root
\nMailFrom = Logwatch<\/b>\u00a0#Change the MailFrom value to a valid email address, or to a local user, such as the hostname(You can get the hostname by issuing “hostname” in the terminal.). This can also be left as Logwatch.<\/p>\n<\/div>\n<\/div>\n
\n
\n
\"Choose<\/div>\n<\/div>\n<\/div>\n
\n
2.2.3 If you would like to save the Logwatch reports to a file. You can specify the file path and name using the File option in the Logwatch configuration.<\/div>\n
<\/div>\n<\/div>\n
\n
\n
Output = file<\/b>
\nFormat = text<\/b>\u00a0#Choose the format (html or text) you prefer. In this case, we choose text.
\nFilename = \/tmp\/logwatch\u00a0<\/b>Find and uncomment (remove the hashmark [#]) the Filename value. Set the path and filename in which you wish to save your Logwatch digests. In this case, we keep the default value.<\/p>\n<\/div>\n<\/div>\n
\n
\n
\"Choose<\/div>\n<\/div>\n<\/div>\n
\n
\n
2.3 Service Configuration<\/b><\/p>\n<\/div>\n<\/div>\n
\n
\n
Service<\/b>\u00a0and\u00a0Format<\/b>\u00a0are used to specify the system services or log files that Logwatch should analyze and include in its reports.<\/p>\n<\/div>\n<\/div>\n
\n
2.3.1 You can include all services by setting Service = All. If you need to exclude one or some of the services, please add additional “Service” lines as the format Service = “-servicename”<\/div>\n
\n
\"Choose<\/div>\n<\/div>\n<\/div>\n
\n
2.3.2 If you only need to include some of the services, you can add a service line for each service as below.<\/div>\n
\n
\"Choose<\/div>\n<\/div>\n<\/div>\n
\n
To see a full list of services, you can run the following command.<\/div>\n
\n
ls -l \/usr\/share\/logwatch\/scripts\/services<\/pre>\n<\/div>\n<\/div>\n
\n
\n
\"List<\/div>\n<\/div>\n<\/div>\n
\n
\n
2.4 Range and Detail Configurations<\/b><\/p>\n<\/div>\n<\/div>\n
\n
\n
Range<\/b>\u00a0determines the time range for which Logwatch generates reports.
\nDetail<\/b>\u00a0determines the level of detail in the generated Logwatch reports. It allows you to specify the amount of information and verbosity in the reports. The available options for the “Detail” setting include:<\/p>\n<\/div>\n<\/div>\n
\n
\n
-Low:<\/b>\u00a0Generates concise reports with minimal details.
\n-Medium:<\/b>\u00a0Provides a balanced level of detail in the reports.
\n-High:<\/b>\u00a0Generates comprehensive reports with maximum details and verbosity.<\/p>\n<\/div>\n<\/div>\n
\n
Set the range and detail you need.<\/div>\n
\n
\"Specify<\/div>\n<\/div>\n<\/div>\n
\n
\n
When you finish the configuration, press “Ctrl” and “x”, then enter “y”, followed by hitting the “Enter” key to save the changes.<\/p>\n<\/div>\n<\/div>\n
\n
After we save the file, there is one more step that needs to be done. That is to create that Temp directory for Logwatch since it won\u2019t do that itself. Run the following command.<\/div>\n
\n
\"Specify<\/div>\n<\/div>\n<\/div>\n
\n
\n
mkdir \/var\/cache\/logwatch<\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
3. Run Logwatch<\/h3>\n
You can choose to either manually run this program or automatically run it with a cron job.<\/div>\n
\n
\n
\n
Run Logwatch Manually<\/b><\/p>\n<\/div>\n<\/div>\n
\n
As you already configure the Logwatch file, you can simply run this command to run Logwatch with the configurations you set in the previous step.<\/div>\n
\n
logwatch\r\nsudo \/usr\/sbin\/logwatch #Run this if you have not su into root account.<\/pre>\n<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n
\n
If you would like to test different parameters, you can specify those on the command line to override your default settings. Here are the available options from the configuration file.<\/div>\n
\n
logwatch  [--detail  level  ] [--logfile log-file-group ] [--service service-name ] [--print]  [--mailto address ] [--archives] [--range range  ]  [--debug  level  ]  [--save  file-name  ]  [--logdir  directory ] [--hostname hostname ] [--splithosts] [--multiemail] [--output output-type ] [--numeric] [--no-oldfiles-log] [--version] [--help|--usage]<\/pre>\n<\/div>\n<\/div>\n
\n
For example, if you would like to get the http service with low details during yesterday by email, run the following command. Feel free to replace any of the parameters with the ones you’d like to test.<\/div>\n
\n
logwatch --detail Low --mailto email@address --service http --range today<\/pre>\n<\/div>\n<\/div>\n
\n
\n
Run Logwatch Automatically<\/b><\/p>\n<\/div>\n<\/div>\n
\n
You can also set up a cron job to run the service automatically at a regular frequency. For example, we configured to run it at 6:35 a.m. each day. First, we use the nano text editor to open the file.<\/div>\n
\n
nano \/etc\/crontab<\/pre>\n<\/div>\n<\/div>\n
\n
Then enter the settings into the configuration file. After that, press “Ctrl” and “x”, then enter “y”, followed by hitting the “Enter” key to save the changes.<\/div>\n
\n
35 6 * * *  root   \/usr\/spin\/logwatch<\/pre>\n<\/div>\n<\/div>\n
\n
\n
\"Set<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
4. View Reports<\/h3>\n
When you run Logwatch, you should be able to receive or view reports.<\/div>\n
\n
\n
\n
Output = mail<\/b><\/p>\n<\/div>\n<\/div>\n
\n
If you choose mail as output, the configured email address should receive the report at the time Logwatch runs. It happens that the email could go directly to the Junk Email folder. If you don’t see the email in your inbox, make sure to check the Junk Email folder.<\/div>\n
\n
\"Logwatch<\/div>\n<\/div>\n<\/div>\n
\n
\n
Output = stdout<\/b><\/p>\n<\/div>\n<\/div>\n
\n
With this stdout output option, you should see the report immediately as you run Logwatch manually.<\/div>\n
\n
logwatch<\/pre>\n<\/div>\n<\/div>\n
\n
\n
\"Logwatch<\/div>\n<\/div>\n<\/div>\n
\n
\n
Output = file<\/b><\/p>\n<\/div>\n<\/div>\n
\n
If the value of Output is set to file, then you can open the filename as set in the configuration file using any text editor. Here, we use the default filename.<\/div>\n
\n
logwatch\r\nnano \/tmp\/logwatch<\/pre>\n<\/div>\n<\/div>\n
\n
\n
\"\u8fd0\u884clogwatch,<\/div>\n<\/div>\n<\/div>\n
\n
\n
\"\u67e5\u770b\u62a5\u544a\"<\/div>\n<\/div>\n<\/div>\n
\n
\n
That’s it! You should now be able to set up log monitoring with Logwatch and Sendmail.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
Conclusion<\/h2>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n
\n
\n
Logwatch provides a reliable and efficient solution for monitoring system logs, enabling system administrators to stay informed about the health, security, and performance of their Linux systems. By automating the log analysis process and generating comprehensive reports, Logwatch simplifies the task of identifying and troubleshooting of potential issues, allowing for proactive and timely responses. Whether you are a small business owner or a seasoned system administrator, integrating Logwatch into your monitoring toolkit can greatly enhance your ability to maintain a stable and secure system environment. So, take the time to set up Logwatch, explore its customizable options, and gain valuable insights into your system logs, ensuring the optimal functioning of your Linux infrastructure.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Introduction System logs contain valuable information about the activities and events occurring on your Linux server. However, manually reviewing these logs can be time-consuming and overwhelming. That’s where Logwatch comes in. Logwatch is a powerful log analysis and monitoring tool that automates the process of parsing and summarizing system logs, making it easier for system […]<\/p>\n","protected":false},"author":4,"featured_media":1561,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1559","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-hosting"],"_links":{"self":[{"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/posts\/1559","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/comments?post=1559"}],"version-history":[{"count":1,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/posts\/1559\/revisions"}],"predecessor-version":[{"id":1562,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/posts\/1559\/revisions\/1562"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/media\/1561"}],"wp:attachment":[{"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/media?parent=1559"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/categories?post=1559"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/b2bhostingclub.com\/blog\/wp-json\/wp\/v2\/tags?post=1559"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}