Tell us how we can improve octoja for you!
Help us with the Roadmap
Completed
Support line breaks in table cells in custom checks
Description: When running custom checks, line breaks within a table cell are currently displayed as spaces. As a result, multiple messages appear as a single block of text and are difficult to read. Desired Behavior: The table display should incorporate existing line breaks from the check output, for example, in PowerShell output using `$probleme -join "`n"`.
Record Graphics Cards in the Device and Hardware Inventory
Installed graphics cards should be recorded in the device inventory, including the model and the size of the graphics memory. This information should also be displayed under Inventory → Hardware.
Synchronize RMM Agents with AD Computers
To see if there are still systems in AD that don't have an agent, compare the agent list with the AD computers. Conversely, this method could also be used to check for agents that have been offline for an extended period. If the offline agent is an AD member but no longer exists in AD, it could be marked for deletion. If the computer was recently online according to AD, then we know that the agent is defective and a technician needs to address the issue.
Assigning Messages to a Device Retrospectively
FR1 (PRIO A) -> When a report is created via the "Reports" menu item (left column), no asset can be assigned to it—neither during creation nor afterward. FR2 (PRIO B) -> In some cases, it would also be useful to assign a report to multiple assets. FR3 (PRIO C) -> If more than one contact person could be stored for a customer, it would also be possible to link a contact person to the report—or even multiple contact persons, if necessary Then it would be, so to speak, a “ticket system light”—of course, not a full-fledged PSA, but a “ticket light” system that’s almost complete. Are there plans for further enhancements, or is this something the integrations are supposed to handle? Because then I’d have two or three more comments based on my current test system—but the question is, do such topics even fit into your general roadmap?
Build more reading rights into the system
I'd like people to read it, but not change it. That's important.
Completed
Unifi Fabric Support
Configure the Unifi integration so that an unlimited number of API keys can be added, since we have configured them as "Fabrics" and therefore have one key per customer that covers all of that customer's locations.
Check Extension for MailStore (Server & SPE)
Monitors MailStore Server (Administration API) or MailStore Service Provider Edition (SPE, Management API): number of users, archiving profile runs, and TLS certificate expiration. Windows only. In addition, the"usedLicenseCount" should also be read and displayed. Billing is based on this, so it would be great to see it displayed. Thank you very much.
Automating Versioning
It should be possible to version automations so that, for example, you can switch to older versions.
Read antivirus information / as a column
For clients, "Antivirus" should be read and displayed as a column
Dashboard Views as Tabs
The saved views in the dashboard should be displayed as tabs—or at least be able to be displayed that way—so that users can quickly switch between views during their daily work.
Add OpenMediaVault
We really like using OpenMediaVault to set up an affordable SMB share in small environments, where we don't have to rely on Asian or U.S. providers (at least when it comes to software). It would be great if OMV were integrated as a check. I added it as a network device via SNMP, but the information it provides is still a bit sparse.
Customize TV View
We came from another provider, where we used the “Wall” (similar to the TV view) on monitoring screens in the IT department. Unlike Server-Eye, in the TV view, alerts are repeatedly moved to the top of the list (i.e., after every check), which means that warnings and errors—such as those checked only once a day—always slide down the list because “repeat messages” are moved to the top of the list. Here, it would be helpful for us to have two columns: “Time of Last Check” and “Time of First Message.” In my opinion, this second column would make it easier to sort the list and keep track of what is truly NEW and what has “just” been checked again.
Completed
Make locations clickable in the customer overview
Unlike the rest, the locations on a customer's overview page are not clickable. The pre-filtered view already exists, but you can't access it from this page.
Battery Condition Analysis
Currently, the battery status is determined and displayed on the system overview map, but it cannot be shown in the inventory or in the lists. However, the check that could be used in reports works differently than the one behind the overview. It doesn’t recognize the battery on many devices and is therefore not usable either. Could you please align the two and make the evaluation possible?
Running Multiple octoja Agents Simultaneously on a Single Device
It would be helpful to be able to connect a device to multiple octoja instances at the same time. For example: A customer is already monitoring their servers using their own octoja instance. The IT service provider supporting them would like to additionally monitor some of these servers using their own instance. To achieve this, it should be possible to run multiple agents in parallel on the same device, each connecting to a different octoja instance. The connections and configurations should remain independent of one another so that an additional installation does not overwrite or interfere with the existing monitoring.
Different Color for Cleared Checks
It would be nice if there were a way to highlight the checks that have been marked as paid manually. Maybe in a different color or with a marker that’s easier to see. It should also be possible to filter them somehow afterward. So far, filtering is only possible by "OK."
Custom Quick Links for Customers, Locations, and Devices
It should be possible to assign custom links with freely chosen names to customers, locations, and devices. These links should be accessible directly from the respective entry as a quick button or via a context menu and should open in the browser. Example: A technician adds a link at a location to an externally stored 360° tour of the office. When providing support, the technician can open the relevant recording directly, get their bearings on-site, and assist employees more effectively. This eliminates the need for time-consuming searches in a separate application. The feature should support any external links, such as those to documentation, site maps, or customer portals. An integrated camera view is not required for this.
Unlock devices not assigned to customers for restricted groups
Groups should be able to explicitly grant access to devices without assigning them to customers, while their customer access remains restricted by customer lists or customer rules. This should not require either global customer access or an artificial assignment of devices to customers.
Targeted Evaluation of LAPS Cycle Errors in the Absence of a Domain Connection
The "LAPS Passwords" check is designed to distinguish temporary connection issues with the domain controller from other rotation errors. If a current password is confirmed to be on file, the assessment should also take into account the time remaining until rotation. Authorization errors, unknown causes of errors, and expired passwords should continue to be reliably flagged.