ESEN
Sales and support 442 138 8102 Request a demo
Fisher Platform module

Find out something is down before the customer calls you.

Monitoring watches your servers, routers, websites and certificates, and alerts you when something goes down and when it recovers. A NOC board with traffic lights and map, incidents with their history, alerts that escalate if nobody answers and each device's availability by day and by month.

See it in action What it watches
  • Nothing to install on the devices
  • Alerts on failure and on recovery
  • Integrates with the ISP CRM
admin/monitoring
The NOC board. The status of everything at a glance, refreshing by itself. Fictitious demo data.
What it watches

Each device, with the checks it needs

A device can have several: the router answers, the website loads and the certificate does not expire this week.

Ping

Does the device answer? With the average latency and the percentage of lost packets.

Ports

Checks that a service answers on its port: the alternative to ping when the device does not answer ICMP, like many routers.

Websites and APIs

Loads the page and checks the response code, a text that must appear, how long it takes and its certificate expiry. Supports access with username and password.

Certificates

Validates the certificate on any port, with its chain and its name, and warns you before it expires.

DNS

Looks up A, AAAA, CNAME, MX, NS or TXT records and checks that they return the expected value.

SNMP

Reads a value from a network device or a printer and compares it with your thresholds. Available when the server has SNMP enabled.

Filings

It alerts you when it should, and not before

One incident per problem, with its timeline, and an alert on recovery.

1

It checks

At the interval you set for each check, in parallel.

2

It retries

A single failure does not alert: it is repeated and only after several failures in a row is it considered down.

3

It opens the incident

One per problem, and it alerts whoever follows that device or its group.

4

Scale

If nobody acknowledges it in time, it alerts the next level. With an optional reminder.

5

It recovers

It closes the incident and tells you right away.

To whom and how

The alert reaches whoever should get it, by the channel each person prefers

  • Subscriptions by device, by group or to everything, for anyone who still has permission to see Monitoring. With no subscribers, it alerts whoever has that permission.
  • Panel bell by default; email, Telegram and WhatsApp are turned on in Notifications, per person.
  • Acknowledging an incident stops the escalation and records who took it, with notes on its timeline.
  • Platform events: when an incident is opened, acknowledged, escalated or recovered, webhooks, automations or Bastino tasks can fire.
admin/monitoring/hosts
A device, in the side panel. Availability, latency, quick maintenance and incidents, without leaving the list.
Less noise, more signal

A NOC you can trust

A system that alerts on everything ends up muted. This one is built so that every alert is worth it.

Retries before alerting

You define how many failures in a row are needed. On recovery, the alert is immediate.

Flapping devices

One that goes up and down non-stop is marked as flapping and stops filling your inbox.

Dependencies

If the router goes down, whatever is behind it becomes "unreachable" and does not alert on its own; the router's alert lists what is affected.

Maintenance windows

Schedule a window, or set one with a click from the device, and alerts are silenced. When it ends, if it is still bad, it alerts.

Availability

How long each device was up, measured in real time

  • Availability for the last 24 hours, 7 and 30 days, and how long it was down this month.
  • A latency chart for 6 hours, 24 hours or 7 days, and a bar for each of the last 30 days.
  • It is measured by how long each state lasted, not by counting tests, and a stopped engine does not make up "up" hours.
  • Retention of results, summaries and closed incidents is adjusted to your policy.
admin/monitoring/hosts
Devices. As cards or as a table, with filters by status and group.
With the ISP CRM

If you are an internet provider, it already brings your routers and your OLTs

  • Your devices are monitored from day one: every router or OLT you add in the ISP module shows up in Monitoring on its own, linked to its record and with its checks. The ones you already had are brought in with one click, and if you change their name or IP in the ISP module, the monitored device follows.
  • With the ISP module active, MikroTik routers and OLTs appear as check types: they read what the ISP already measures, without opening another session against the device.
  • The ISP maintenance mode also silences the alerts of whatever is linked.
  • A data point that has gone more than three quarters of an hour without updating shows as "unknown", with the reason, instead of pretending everything is fine.
  • The rest of your infrastructure —servers, websites, certificates, DNS— is watched on the same board, with the same incidents and alerts.
CRM for ISPs and WISPs
admin/monitoring/hosts/new
Adding a device. Its address, what it depends on, where it is and who to alert if it goes down.
Connected to the rest

It is not an island: it is part of your platform

It builds on what Fisher Platform already has, instead of copying it.

Assets

Tie a device to its asset and the asset record says whether it is up, without touching anything else.

Clients

Link devices to a customer and the record shows how many of their devices you watch.

Public status page

Groups you mark as public are published as the "Infrastructure" component of your status page.

Bastino

"What is down?", "what availability did the server have this month?". It acknowledges incidents, sets maintenance windows and adds devices, with a confirmation card.

Webhooks and automations

Every incident opened, acknowledged, escalated or recovered is an event you can connect to other systems or to your automations.

Home and plans

A "Devices with problems" widget on your home screen and, if you offer the platform to your customers, a limit of checks per plan.

Stated plainly

What it does and what it doesn't

Better to know before you sign up than to find out afterwards.

Designed with security in mind

A module that reaches out to the network, with the door guarded

  • Credentials, encrypted. The SNMP community or the username and password of a website are stored encrypted, tied to their destination, and never shown again. If you change the destination, they are deleted.
  • No surprises with the network. Cloud metadata addresses and other reserved ones are always barred; the internal network is opened or closed in settings, and on shared cloud instances it comes closed.
  • Who decides where it calls. Only whoever has permission to create and edit; acknowledging incidents or checking now does not change destinations.
What it is not

It does not try to be everything

  • It does not install agents on the devices: it does not measure processor, disk or memory inside. Other tools exist for that, and here it watches that the device and the service respond.
  • It does not discover the network by itself: devices are added by hand or by asking Bastino.
  • It measures from a single point: the platform server, not from several locations.
  • SNMP is available in version 2c and depends on the server having it enabled.
Frequently asked questions

What we are usually asked

Do I need to install anything on every device?

No. Checks are made from the platform towards the device or the service: ping, ports, web, certificates, DNS and SNMP. There are no agents to install; for the same reason it does not measure processor, disk or memory use inside each machine.

Does it alert on every single failure?

No. A failure is retried and only when it repeats the number of times you set is it considered down and an alert sent. A device that flaps non-stop is marked as such and stops flooding you with alerts, and whatever depends on a down router does not alert on its own.

Does it integrate with the ISP CRM?

Yes. If the ISP module is active, every MikroTik router or OLT you add is monitored from the start, linked to its record without typing anything again; the ones you already had are brought in with one click. It reads what the ISP already measures, without opening another session against the device, and the ISP maintenance mode also silences its alerts.

Can it watch my internal network?

Yes, when the platform is installed on your own infrastructure. On a shared cloud instance the provider's private network is closed for security and only public devices and services are watched, unless the provider opens it for that instance.

How do I find out about an outage if I am not watching the board?

With the panel bell, and with email, Telegram or WhatsApp if you turn them on in Notifications. If nobody acknowledges the incident in time, the alert escalates to the next level.

Is it sold separately?

It is an installable Fisher Platform module: it is turned on or off separately and, when turned off, its screens and alerts disappear. Write to us and we will tell you what your plan includes.

See it watching your own devices

We add your servers, your websites and, if you are an ISP, your routers, and we go through the board, the alerts and the availability together.

Fisher Networks ventas@fishernetworks.net 442 138 8102
Send an email
About the screenshots and the data

The screenshots are from a demo environment with fictitious devices and data; no data belongs to a real customer. Each installation defines its own intervals, thresholds and alerts.

View plans