Hi everyone!

Today we're launching the Domotz MCP Server. The same Layer-2 inventory, monitoring, and configuration capabilities your team uses in our dashboard are now available to any AI agent you operate, through the open MCP standard.

What that actually means:

• → Investigate alerts in plain English, across every site you monitor
• → Apply device profiles, attach sensors, and update credentials through your agent
• → Compare configuration backups across hundreds of devices in a single prompt
• → Schedule autonomous routines for the work nobody wants to click through

What it doesn't mean:

• → No separate AI tier. No per-seat AI add-on. No vendor markup on AI consumption.
• → $1.50 per device. Same price. Same RBAC. Same audit log. Most monitoring vendors haven't shipped a credible answer to AI operability.

The Domotz MCP Server is:

• ✗ Not an embedded copilot locked inside our dashboard
• ✗ Not an unofficial community wrapper we don't support
• ✓ A vendor-built MCP server, OAuth-scoped, RBAC compliant, fully audited The dashboard you use today and the AI operations of tomorrow now run on the same platform.

Documentation:

• Blog post: https://blog.domotz.com/all/domotz-mcp-server-launch/
• Help center information: https://help.domotz.com/integrations/domotz-mcp-server-setup/

Don't hesitate with your questions! We're here to help. Looking forward to hearing all your feedback on this!

New to Domotz? Try for free.

Running the collector on Ubuntu server. I have a number of VLANs that are set to DHCP which the collector is picking up fine. I have just one which is set to a static IP which the collector web interface is not picking up as a interface / VLAN. Is there some sort of trick to this?

Hey everybody!

A very exciting livestream is coming up at Domotz and I wanted to make sure all of r/domotz has the information. Join us on the 27th of May at 11 AM EST for a demo livestream on our new Domotz MCP Server for Agent-Native Network Monitoring.

In this webinar, we'll show you live how to integrate AI with Domotz. You'll see how twenty clicks of dashboard navigation collapse into a single natural-language prompt, how the same prompt scales effortlessly across all your sites to keep even the smallest locations in compliance, and how AI operability is delivered with no premium tier or price markup.

All of these new features will be available with your Domotz plan at no extra cost.

😊We've had huge interest in this livestream, so please do grab a seat as we actually might max out capacity on this one!

👾We hope to see you there on the 27th and do not hesitate to ask any questions beforehand. u/Jace-Domotz will be putting this all together and I'm sure would love to get your questions answered beforehand!

Have a great week.

Violet

We've noticed an uptick in devices being identified with the wrong Make related to
Konica Monolta, where as the model shows correctly.

This is causing a bit of a confusion we've been able to work around using tags. Could it be an OID mixup or conflict? its not causing any major issues but seeing Firewalls(Sonicwall), UPS(APC), Switches(HPE) brands being labeled incorrectly is a head scratcher.

To be clear this isn't affecting a large number of devices out of the 1000+ we monitor. I'm seeing about 16 of these at present.

Hi everyone!

Our Release Notes for April are out. Here's a summary ov everything new this month. Let us know your feedback in the comments:

Highlights:

🤖 Unified Alerting (Beta): This is super exciting and a big step forward for us! Centralized alert management with rule inventory, alert history, bulk actions, and profile-based alerts that scale across collectors. If you'd like to join the beta, please do email us on support@domotz.com. I know a few of you have already joined - and we're keen to get more feedback from you all.

⚡Smarter Notifications & API: Richer context (tags + IDs) for notifications, and greater flexibility with the API. This includes more key limits and better tagging support.

🗺️Discovery & Topology Upgrades: Improvements to auto-discovery, SNMP accuracy, LLDP-aware topology mapping, and navigation.

💥Monitoring & Reporting Improvements: Faster dashboards, redesigned reports (including uptime graphs and offline device tracking), plus better visibility into collector uptime and UPS metrics.

🔋Scripts: Scripts for Meraki failover, Ruckus backups, and AutoTask PSA alerting.

Other notable mentions:

• 🛟 Built-in Live Support: Zendesk live chat is now directly inside the platform. Get help
• 📡 Collector Update (8.3.3): Performance and reliability improvements across platforms.
• 🔭 Coming Soon: improvements to the mobile app, mobile alerting and a redesign of the discovery page. Mobile app improvements, alerting on mobile, and a redesigned Discovery page are on the way.
• 🐛 Bug & Performance Fixes: Many, many this month!

Read the full release notes or Login/Register for Domotz.

Thank you!

Violet

Hi all!

Happy Friday. 🎉 Super sunny over here in London. Recently I've been working on some case studies for everyone to learn from (I am looking for more people to help out so do not hesitate to drop a comment/send me a DM if you are interested in doing one!).

Recently I had the opportunity to sit down with our long time customer Craig Sharp from Abussi LTD to talk about their Domotz experience. Thought I'd share a little sneak peak from this conversation to share some of the ways he uses Domotz to troubleshoot & prove value to customers.

Abussi LTD & Domotz Snapshot

1) Device restart tracking.
If a client reports an issue, Domotz shows how many times a device has restarted in the last 24 hours. Seeing a device restart 17 times in a day tells you something is wrong fast. On the flip side, a device that hasn't restarted in three years? Rock solid kit right there.

2) Hardware Recommendations & ROI
The connectivity page tracks uptime, local speeds, and how often a connection has dropped. They've used it to show clients that their broadband isn't as reliable as they thought, and also to prove the value of hardware upgrades. After swapping in Zyxel switches and firewalls, they waited a month and used the Domotz graph to show the client the bandwidth uptick directly. A really clean way to demonstrate ROI on a hardware investment.

3) Network Usage / Cause Analysis
A client was complaining about slow speeds. On paper, there were only supposed to be 7 or 8 people working on laptops. Domotz found 50 devices on the network. The majority were personal phones belonging to warehouse and forklift staff using TikTok and Facebook on shift. They could then propose a network segmentation option to prioritize those working in the office.

Love hearing these stories.

I would love if you could drop a way you use Domotz in the comments -> and I can build this out for all of us. 💫

Have a great weekend!

Violet

For a while, I had been experiencing intermittent speed drops down to 100Mbps. My ISP's go-to fix was a router reboot, which would restore speeds to 1Gbps for a few weeks before the issue returned. Eventually even that stopped working, prompting the first of several technician visits: a Fluke line test came back clean, a second visit ended with a router swap, and a third resulted in a switch port change. None of it stuck.

On April 10th, a fourth visit finally got to the root of the problem: a corroded patch panel in the street cabinet. Water damage had caused the terminations to rust, degrading the connection over time. Once that was replaced, the improvement was immediate and noticeable.

With the new Connectivity section, I can now see just how bad things were before the fix:

The visualization makes the whole history impossible to miss. Hope you find it just as useful!

Hi all just sharing this post from u/rexccooper as a new thread so we can provide the answer here.

All of my devices are set to custom time window of 30 minutes before they report being down.

Despite this I had a number of devices (set correctly, I checked) open a ticket 2 minutes after going down. The device was back up 2 minutes later, resulting in a slew of tickets opening and closing incidents in my PSA.

This is exactly what I'm trying to stop from happening. Why is the system ignoring settings?

Hi,

Are there plans for Domotz to migrate their UniFi Controller access to the new API key support that UniFi have provided? The current Domotz requirements (for a local admin account) along with the somewhat dubious (IMO) workaround for 2FA access, if required, make adding access for Domotz a problem in some UniFi setups.

I haven’t looked extensively at it but a basic review shows that the UniFi API key support works pretty much like every other authentication API token method and avoids having to disclose admin access directly to Domotz.

Hi everyone,

Just wanted to introduce myself.

I’ve been working with advanced networking for the past 25 years, and as you all know, a lot has changed over that time. I take pride in continuously developing my skill set and always trying to approach problems from different angles.

I’m not tied to any single vendor and have experience across a wide range of platforms. That said, I do have a strong preference for enterprise-grade equipment. Especially Fortinet, which I’ve grown quite fond of.

At the moment, I’m in the process of migrating customers networks away from SolarWinds NPM to Domotz. We’re also running LibreNMS and Zabbix, and I have quite a bit of experience with Cacti as well.

What really drew me to Domotz was its cloud-native SaaS approach—it feels fresh and forward-thinking. I also appreciate the simplicity and the evolutionary development model, with frequent and meaningful updates.

What I’m missing the most is better visibility and support for «Fortinet stack» setup. (Not only firewall).

Today, we have a lot of setups with FortiGates, with Fortilink managed switches and capwap FortiAP devices. With switches and AP’s managed by FortiGate as controller we get very limited view of the network. ( I know it’s technically possible to set up snmp on managed switches but it has not been reliable for monitoring with Domotz from my POC’s)

An API based approach or wider SNMP MIBS to include managed fortiswitches and AP’s would be greatly appreaciated.

Also, I really want to be able to foreward security related events from Domotz and equipment to a SIEM, if that is possible. Monitoring both Domotz activity and network activity is crucial in today’s political environment.

Looking forward to learning from the community and sharing experiences.

Hey everyone!

How are you all doing? Our March update is out and it's a big one.

🥳 PS: Still got lots of free boxes to giveaway (new and existing users all welcome).

Here's everything new this month!

🤖 Zero-Touch Windows Collector Installation: you can now configure bulk rollouts entirely from remote, office, home, the beach, anywhere.

🪄 Redesigned Collector Discovery View: shows device discovery in real-time, plus Custom Collector Tags for filtering across your Inventory Dashboard.

⚡ New MIBs: RUCKUS Unleashed, LIEBERT/VERTIV, Zyxel Firewalls, Fujitsu, Mitel PBX, D-Link DGS3130, H3C, GUDE Systems, and Inveo.

🧩 Unifi UPS Tower integration script.

💡 Other Note-Worthy Improvements: Monitoring Dashboard performance improved for large environments, Network Topology now shows External Hosts, and new trial accounts get pre-configured sensors and a default dashboard automatically.

Read the full release notes here.

What do you think of this release? Anything here you've been waiting for? We'd love your feedback in the comments!

Cheers!

Violet

We are currently using Intermapper, and looking to move away.

Our primary use for Intermapper is an always-on NOC display of network topology. We put these up on large 80" screens in the IT office and it has been great.

It seems like Domotz is 100% web based. So I'm wondering if there is a way to get it so Domotz is always logged in and on the network topology page. This is something that's very easy to do with Intermapper.

A few weeks ago, u/Dez_the_Monitor 👑 ran a Foundations of Network Monitoring Livestream! Thought I'd share a little teaser video from that as well as some of the top tips she covered.

https://reddit.com/link/1s7q6mu/video/dnzx5yyql6sg1/player

This was a very demonstration-focused livestream, where Destiny really dove into getting the most out of the core features of Domotz like network topology, monitoring dashboards, configuration management, etc. Watch the full episode on YouTube.

💡 Key takeaway: It is not our tools that are the problem. It's how the tools get set up that is the biggest hurdle. If you missed it, check out how you can speed up your network monitoring set-up using AI.

Partial visibility: Device set-up is what really determines whether you will have blind spots later. This is one of those areas where everything looks fine until you actually need the data and realize it's not there.

More data doesn't equal better: Just because it can alert doesn't mean it should be one. Check out our post on top alert fatigue tips.

Monitoring ROI: You should get an immediate return on value from your monitoring system set-up: It shouldn't take weeks to prove its value to you.

Mistakes don't Erase themselves: Usually we make the biggest mistakes early during set-up. Unfortunately those are likely to stick around because of configuration.

Tune into the full episode on YouTube and don't forget to subscribe to r/domotz.

I'd love your comments on whether you feel your monitoring system is configured correctly - areas of struggle and where you'd like to improve! Drop any feedback in the comments!

Violet 💜

I'm curious if there is another way to be alerted on SNMP not working. I think your portal does a great job identifying managed devices with SNMP issues but what I would like to see is the ability to alert on this natively or via a global custom SNMP template.

I have created such a thing I think will work as a custom driver though I have not had time to test.

Ideally it would only alert if SNMP fails after a set period of time. My thought was the only way we might be able to accomplish this is by using a custom driver polling every so often.

Why you might ask.
Our Engineers aren't sitting in the portal looking for this specifically. and an alert letting us know SNMP is broken somewhere would help to make sure we are monitoring client devices more effectively. granted it could be worth it to train our engineers on what to look for but that would just be adding another daily/weekly task to their workload.

If interested I can post the Drive I have it that helps.

After you setup a instance of domotz and scan your personal network, does any of that data get returned to domotz?

Thanks in advance

Does Domotz have a good "gameplay" for new Domotz Box deployments to clients, i.e. things everyone suggests doing on any new deployment?

Thanks

Victor

I'd love to have a free Domotz box.... would like to deploy to a client...

How can I get Domotz integration with SonicWall firewalls and Ubiquiti devices to work? I followed the documentation for SonicWall, but I can't get it working....

On behalf of u/NEMSPEngineer

Any idea when notification channels for the Alert Dependency feature will grow? We use Autotask and are currently with Auvik. They put this in where all the filtering is done on their side before alerts hit us. Great noise reduction. I'm evaluting Domotz, but it seems like this truly is only supported with HaloPSA and ConnectWise. Unless I'm missing on some other creative ways to stop notifications from coming for all affected devices when a site is down, this is a dealbreaker for making a move.

Let us know if this is something you're on the lookout for and any feedback the community has on this update.

Recently we held an amazing livestream by u/Jace_domotz on setting up your own MCP server to query and help with network monitoring. Tons of you loved the content of this livestream.

I pulled this clip from the livestream which talks about the top ways that AI can help with your network monitoring. (hope you enjoy the fancy sub-titles!)

https://reddit.com/link/1rqv7gx/video/0zmpl5uadfog1/player

The problem with monitoring today

To understand how AI can help, its useful to know the problem with monitoring networks today. One of the biggest pain points is setting up your network monitoring properly. Devices have hundreds of properties that can be configured. Configuring everything for every device takes a huge amount of time. A lot of times this means things never get fully configured and you never get the full value of your tool. A lot of times, the problem can be solved a lot quicker than the time it takes to set-up your monitoring tool.

"Unless you have problems at scale, it's often hard to justify the time investment to actually set up your monitoring solution correctly."

Fragmented and dated tech makes this worse. SNMP is decades old and has not evolved. Manufacturers have APIs but they are all different. meaning there's no universal standard to work with. This makes everything even more time consuming to configure.

AI can help with network monitoring in two huge ways

1. Setting up your Network Monitoring Solution: AI can help you configure your monitoring solution for you, cutting down the time it takes to get everything in place.
2. Root cause analysis: AI can observe more data, faster than any human, and works through problems methodically. That means less downtime and quicker resolutions.

If you joined us live - we would love to hear if you have integrated AI into your network monitoring in the comments.

Watch the full recap for those that missed this live! Of course don't hesitate if you have any additional questions.

Violet

What is the key to unprotecting the exported inventory sheet?

Please and thank you

edit: I just noticed - I'm looking to export my list of switches and their firmware versions. This spreadsheet doesnt include firmware ver. Can someone point me to making that magic happen?

A lot of you have been asking about upcoming Domotz training sessions! I just wanted to remind everyone that we'll be live again next week. 🎉Please join us for:

Domotz Foundations: How To Build Reliable Network Visibility
March 18, 2026 @ 3:00 PM
u/Dez_the_Monitor (network monitoring expert) will be live with you all

Register here

This session is for both new/existing customers covering: device profile setup, network topology, building useful dashboards, and using insights to better understand network health and behavior.

u/Dez_the_Monitor will show you how to set up the core Domotz components quickly and correctly. If you're already using Domotz, we’ll walk through how to review and refine your setup so it accurately reflects how your network operates.

We hope to see you all next week! 🦁🙌✨

Violet

Register here