---
title: "Custom Syslog"
slug: "fmadio-os-monitoring-custom-syslog"
updated: 2025-05-19T10:51:34Z
published: 2025-05-19T10:51:34Z
canonical: "docs.fmad.io/fmadio-os-monitoring-custom-syslog"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fmad.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Syslog

By default the FMADIO rsyslog daemon does not replicate or distribute its internal syslog.

In many cases its good to push the syslog to a remote location, such that the system can be monitored (via syslog) at a central location. The FMADIO systems use standard rsyslog linux utility, current version

FW:100885 (2025/5/6)

```bash
fmadio@fmadio200v4-636:$ rsyslogd  -v
rsyslogd  8.2010.0 (aka 2020.10) compiled with:
        PLATFORM:                               x86_64-unknown-linux-gnu
        PLATFORM (lsb_release -d):
        FEATURE_REGEXP:                         Yes
        GSSAPI Kerberos 5 support:              No
        FEATURE_DEBUG (debug build, slow code): No
        32bit Atomic operations supported:      Yes
        64bit Atomic operations supported:      Yes
        memory allocator:                       system default
        Runtime Instrumentation (slow code):    No
        uuid support:                           Yes
        systemd support:                        No
        Config file:                            /etc/rsyslog.conf
        PID file:                               /var/run/rsyslogd.pid
        Number of Bits in RainerScript integers: 64

See https://www.rsyslog.com for more information.
```

All the usual linux rsyslog functionality is alliable.

## Customization

By default FMADIO systems use a builtin syslog configuration located in

```plaintext
/etc/syslogd.conf
```

This is the basic configuration writing to local disk only.

To customize this

### Step 1) Copy

Make a copy of the default configuration and put it

```plaintext
/opt/fmadio/etc/
```

For example

```plaintext
cp /etc/syslogd.conf /opt/fmadio/etc/
```

### Step 2) Modify

Modify the configuration file copied in

```plaintext
/opt/fmadio/etc/syslogd.conf
```

### Step 3) Restart

Rebooting the system is recommended once the final syslogd.conf is set. This ensures the system from a reboot operates as expected

For development the following can be done

```plaintext
sudo killall rsyslogd
sudo /sbin/rsyslogd -f /opt/fmadio/etc/syslogd.conf
```

This allows quick testing of the updated syslogd.conf file

## Remote Logging

Using the above example we recommend updating the file

```plaintext
/opt/fmadio/etc/syslogd.conf
```

The default configuration file has the following lines commented out at the bottom of the file

![](https://cdn.document360.io/b9aab0c4-36d0-4616-9673-30b661455571/Images/Documentation/image(227).png?sv=2026-02-06&spr=https&st=2026-11-13T19%3A40%3A38Z&se=2026-11-13T20%3A40%3A38Z&sr=c&sp=r&sig=3yV7vwtv8JZF49BiGCIYAPL49wWy0wEC69GcHa8AWzk%3D)

When modifying using the above steps, un comment this and change the IP address and Port number based on your infrastructures setting.

For example, TCP system at 192.168.100.100 on port 514, the following is used

```plaintext
*.* @@192.168.100.100:514  
```

Consult your infrastructure monitoring team on what the correct setting should be.