Unimus forum

Hi, currently, it's not possible to further customize our existing roles, so the options they can and cannot manage in Unimus are hard-coded." That said, we do plan to introduce support for custom roles in the future, allowing users to create a custom role and define exactly which views are acc...

Hi,

unfortunately, such an option does not currently exist in Unimus, but we plan to add it as a configurable option within the scope of our existing User Management. There is no ETA at the moment, but we will keep you updated in case of any news.

Thank you for your request. I can envision adding an address priority option similarly as already exist for Zabbix, allowing you to specify which address should be prioritized during sync process. I will record this request in our backlog, and once an ETA is determined, we will inform you accordingly.

Hi, to help you with identification of possible root cause we would need some additional information. Could you please clarify if the targets use by preset were added per address, per tag, or as a combination of both? Additionally, you mentioned that the same issue occurs during the creation of a ne...

Thank you for sharing your ideas with us. We have already considered such an enhancement, but we are still unsure about the final form this feature should take. While it would be possible to simply add the history of commands a results into the existing Device CLI history table and display it indivi...

Thank you for sharing your request with us. We agree that this feature could be a nice addition to the existing login options in Unimus. That’s why we’ve decided to add it to our backlog. However, no ETA has been set yet. I will keep you updated in case of any news

Hi Alexander, we have received several similar requests to add webhook functionality and integrate Microsoft Teams into our existing notification system. Both features are planned for implementation in the future, but no estimated delivery date (ETD) has been set at this time. However, I have linked...

Hi, thank you for reporting this problem. We checked our APIv3 documentation and found some formatting mistakes for the following endpoints: POST api/v3/jobs/push POST api/v3/zones:untag POST api/v3/zones:tag The problem has already been resolved, and we plan to release the fix publicly with the upc...

Thank you for reporting this problem. We have already reproduced the behavior you reported, and we plan to start working on the fixes in the near future. Currently, the preliminary delivery time is expected with version 2.6.0, which means sometime at the beginning of December. I will keep you update...

Hi, thank you for your post.

We received similar requirements in the past, and they are already documented in our backlog. Unfortunately, no ETA has been provided for this topic yet, but I will let you know if there are any updates.