Having issue creating a syslog server entry to collect system logs from a MX-68W

[spollard]

Ive downloaded syslog watcher on my VM i want the logs to go to.  I did the following: 

• Network-wide → Configure → General → Reporting → Syslog servers, or

• Security & SD-WAN → Configure → Syslog (MX-specific).

1. In Meraki Dashboard, navigate to the network that contains your MX-68W.

2. Go to Syslog servers.

3. Click Add a syslog server:

   • Hostname/IP: the static IP of your Windows VM (e.g., 10.10.10.50).

   • Port: 514

   • Protocol: UDP

4. Roles / Log types to send (check all that apply to your use case; for MX these are the usual picks):

   • Security appliance event log (MX events)

   • Flows (connection summaries)

   • Security events / IDS-IPS

   • URL / Content filtering (if enabled)

   • VPN events (if you use AutoVPN/Client VPN)

   • (Optionally) Network-wide / Switch / Wireless logs if you want those too.

5. Save changes.

Because your syslog server is on the same LAN as the MX, the MX will source syslog from its local interface that can reach the server (no NAT rules needed).

I save it refresh the page and it disappears not syslog server. Its there when i save when i refresh it just goes away.

[alemabrahao]

My suggestion is that you can try saving the configuration in incognito mode with all roles selected.

But if it still disappears, open a Meraki support ticket. They can check the backend logs and confirm if the configuration is being silently rejected.
You can also test with a different network or create a new test network to see if the issue persists.

[spollard]

thank you!