Alternatives to LogicMonitor
Other Network monitoring vendors we measure, sorted by how much they publish that LogicMonitor does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from LogicMonitor on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LogicMonitor has 6 gaps in what we could measure: Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and LogicMonitor does not” is the one that closes them.
| Vendor | Score | Publishes, and LogicMonitor does not | LogicMonitor publishes, and they do not | |
|---|---|---|---|---|
| Kentikkentik.com | 65/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Data processing agreement, Certifications named, Uptime SLA with a figure | Compare |
| Auvikauvik.com | 52/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| Paesslerpaessler.com | 43/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Data processing agreement, Status page with history, Uptime SLA with a figure | Compare |
| Netgear Insightnetgear.com | 39/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Zyxel Nebulazyxel.com | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| Cambiumcambiumnetworks.com | 26/100 | 2 security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Netskopenetskope.com | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Domotzdomotz.com | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Icingaicinga.com | 22/100 | 2 security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Catchpointcatchpoint.com | 26/100 | 1 Named privacy contact | 3 Data processing agreement, Data location stated, Uptime SLA with a figure | Compare |
| Aristaarista.com | 13/100 | 1 No third-party tracking before consent | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Nagiosnagios.com | 13/100 | 1 Named privacy contact | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.