Octoja currently distinguishes between clients, servers, and network devices.
We would like to see a fourth category , “Cloud Service, ” to clearly map external services and APIs.
Example: Hornetsecurity is monitored via PowerShell/API. The PowerShell script is executed by the Octoja agent on a customer’s server or client.
If an error occurs in the cloud service, it currently appears in the Octoja console as an error of the executing server or client. Likewise, this device is listed in the reports, even though the actual issue affects the cloud service.
Therefore , a separate “Cloud Service” object type would be desirable . The server or client would serve only as a proxy for executing the check, while status, errors, and—in particular—reporting would be assigned to the monitored cloud service.