How long until the first device shows up, and is setup a learning curve?

Admins praise monitors that set up in minutes and leave ones that take days to learn. What SoloNOC’s setup involves, and the timing we have not measured yet.

Updated 2026-10-24. Every quote links to where it was published.

In admins’ own words

“Setup time took literally seconds.”

“took me less than five minutes. I haven't had to improve it since.”

“It was not intuitive to set them up. I had to use a lot of time to learn it.”

What it is

An outside uptime check is quick to set up because it only pings a public address. Monitoring a client network from the inside needs something running inside it, and that step is where tools either take a minute or take a weekend.

How SoloNOC does it

• Create a site in the app and it shows a one-line install command. Run it on any always-on Linux machine inside the network, with curl installed. (pinned by: answers.test.tsx)
• The agent connects out over HTTPS, so no inbound firewall port is opened. (pinned by: answers.test.tsx)

What admins report from other tools

Reviewers of sensor-based monitoring suites describe setup that was not intuitive and took a long time to learn.

Install the SoloNOC agent

1. Create a site in the SoloNOC app.
2. Copy the one-line install command it shows.
3. Run it on an always-on Linux machine inside that network.
4. Declare the upstream of your core devices so an outage pages once.

Questions

What do I need to run the SoloNOC agent?

Any always-on Linux machine inside the network, with curl installed.

Do I need to open a firewall port?

No. The agent connects out over HTTPS.

Is there a Windows agent?

No.

Related

• How do I get one page per outage instead of forty alerts?
• Will the free plan be pulled or restricted after I build on it?
• All answers