Feature Requests

issue including: SQL Agent server Memory utilization exceeds Max allowed SQL Agent server CPU load too high

Per customer, they want to remove the list of integration that categorizes assets under the Dashboard/Widget section of the app for the following reason: We operated under the notion of list privilege and “need to know”. We shouldn’t be advertising the technologies that we use nor integrate with on the back end to the general end user population.

Client wants to add an additional QuickBooks Online instance to our integration. However, our current system allows only one single instance for one integration.

Client has 10 Cisco Meraki tenants and would have 10 connection to them while current integration for MSPBOTS only support 1 connection per integration

What we are looking for is to integrate our VoIP service into MSP bots to monitor the following * number of calls taken by each service team member daily * if the API allows for it, busy lamp field (who is on the phone presently) * caller frequency - top 3 callers * caller alert - X number of calls within Y timeframe - yellow and red indicators, i.e., 3 calls from same number within 3 minutes would light up red whereas 3 calls from same number within 90 minutes would light up yellow. We are looking to use this to monitor response times to client calls. In the event that a call from a client is missed we would potentially want the bot to alert us if the misses and the call that was missed so that we can call them back.

Client uploaded CSV with blanks for numeric fields, and noticed the dataset was created with no data. We should enhance the current code to manage blanks for all datatypes.

Currently if dataset depends on SQL Agent is stopping syncing data, the only option is to restart SQL Agent. This could be done by mspbots if SQL Agent is online. However, if it goes offline, we have to ask customer to do that. And we don't know why it goes offline and why cpu/memory usuage are climbing up to 90% or above. It's difficult for customer and support team to find the root cause for this problem. So we need to enhance SQL Agent to improve the obsservabilities. From support perspective, below features are needed: standard hardware/software required by SQL Agent how much and how frequency data could be synced under standard hardware automatically circuit breaker for overloading to avoid offline automatically restart SQL Agent to work when workload is fall to threshold which dataset consumes the most resources from time serial time serial statistical data of resources consumed by SQL Agent cpu/memory/disk usage details of SQL Agent and the host bot/dashboard to show working status of SQL Agent

This API is for taking data OUT of MSPB. I am looking to integrate MSPB with other systems you don't have integration yet. This would requires pulling data INTO MSPB from the third party system.

Zendesk Ticket ： https://mspbotsai.zendesk.com/agent/tickets/5866 Problem Statement： My initial issue with the MFA setup revolves around the inconvenience of repeatedly entering a code for(MFA, especially considering the high level of access required by MSPBots. Given that this tool necessitates significant permissions, ensuring its security with MFA is crucial. However, the user experience is compromised if users have to input a code every time they sync the system. When I mentioned that "most vendors allow entering the secret instead of a code for MFA setup," I was referring to the practice where some MFA implementations permit the use of a secret key, which can be stored securely and used to generate authentication tokens automatically, rather than requiring manual entry of a code each time. This approach maintains a high level of security while enhancing usability by reducing the frequency of manual code entry. In your response, you mentioned the configuration for integrating with CW Automate, noting that for this integration, the input of a URL, username, and password is required, and that MFA is not mandatory. While I appreciate the clarification regarding CW Automate's integration requirements, my concern lies more broadly with the overall MFA implementation. I believe it would be beneficial for us to explore options that streamline the MFA process without compromising security. For instance, enabling the use of an MFA secret key could significantly enhance the user experience by minimizing the need for repetitive code entries, thereby making the MFA process more efficient and user-friendly. Reference for other vendors mechanism https://docs.immy.bot/connectwise-automate-integration-setup.html