Systems
The Systems page shows everything monsys watches: servers, websites, platforms, cloud accounts, services and containers. monsys builds the list itself from what agents, web servers, uptime checks and connectors report, and refreshes it every five minutes. There is nothing to enter.
Relations
Section titled “Relations”| Relation | Meaning | Source |
|---|---|---|
| Runs on | A container, service or website lives on this server. | agent, web server configuration |
| Served by | This website is answered by this web server (for example caddy.service or an nginx container). |
web server configuration |
| Reached through | This platform (for example a WordPress site with the monsys plugin) is reached through this website. | connector |
| Depends on | Added by you: this system needs that other system. | you |
What a problem hits
Section titled “What a problem hits”Every problem shows what it hits:
- a stopped container or service: the websites it serves and the platforms behind them;
- a full disk, memory or cpu shortage, a silent server or a rolled back patch: everything running on that server;
- a website that does not answer or an expiring certificate: the platforms behind it.
A vulnerable package or a changed file does not automatically hit every site on the server. monsys ranks the vulnerabilities that are really reachable by what actually runs.
Timeline
Section titled “Timeline”For every system, what happened in the last 30 days: problems opened and resolved, activity, patches, changed files and changes someone made in monsys.