Feature Requests

Currently on-call schedule is maintain by all Service Delivery and security Teams to request help after hours. Each Team Manager maintains the schedule in OpsGenie Calendar where they can set up the rotation of their teams for the entire year. Once a ticket is escalated to a particular queue by the after hours team members - OpsGenie is able to identify a P1 in the queue and alert the on-call tech via any prefered method (Email, call, sms, app notification). If the primary on-call tech does not respond to the notification, the system should be able to reach out to the next escalation point after a set # of tries, for our process it's the on-call tech manager. likewise if the manager does not respond, it should call the next escalation point. To summarize: The app should have the following features ability to add Calendar, Schedule for any of teams Ability to pick p1 escalated after working hours and alert the scheduled staff. Ability to alert the staff by various methods Ability to reach a secondary or Tertiary if any one of the escalation point does not respond. Ability to generate an On-call Report for payroll with list of team members of each team that were on-call. Let me know if you need any more information.

Do you guys have any solutions in place for on call management? If so, what are the features and do you have anything I can look at?

When we were initially onboarded we were told the SSO would be available for the client portal( https://portal.mspbots.ai )

Problem Sidebar shows Not Mapped = 0 for Datto (only 4 clients and all are mapped). The grid still displays Matching failed badges in the Datto column for many clients. This reads like an error and adds noise. These clients likely don’t exist in Datto and should be excluded or marked N/A. Expected behavior When a source has no unmapped clients: Any client that doesn’t exist in that source should automatically be tagged Ignored (or N/A) instead of “Matching failed.” The grid and the summary must stay consistent.

Use Case refer to the picture attached

Currently, there are three APIs that can only synchronize data for one tenant in Cisco Umbrella. They are: Application Categories, Applications, Protocols Can you support syncing data for all tenants in Cisco Umbrella.

Add Case Sensitive feature in Dimension

Display all data in the widget filter instead of existing data, for example, status should display the entire status list instead of the current existing status

Due to rate limiting issues with Halo, we’ve implemented a retry mechanism for certain APIs to help ensure data integrity for our clients. However, clients are currently unable to see from the logs whether these exceptions have already been retried successfully. As a result, they still see the error messages and cannot disregard them with confidence. To improve clarity, we’d like to request either a clear indicator showing that a retry was successful, or that the error message be cleared automatically after a successful retry.

To add notes next to scorecard values to explain oddities would be good, justify scorecard entries if they are outside KPIS.