Alternative data fetching methodology for HaloPSA - Halo Reports
product review
R
RJ Madsen
Following for a discussion with Leonard during onboarding, I believe MSPBots could benefit from expanding ticket data acquisition from Halo from just directly utilizing the tickets API to pull date but also support pulling data from Halo reports. This would require support for either custom mapping on the MSPBots side or a more rigid report setup guide provided by MSPBots on what fields it can process
The current NextTicket filter options for HaloPSA seem to be limited by the Halo /Tickets endpoint and their available parameters. Utilizing Halo reporting allows for more customized and accurate ticket data retrieval
Log In
This post was marked as
product review
Micus
Hi RJ Madsen,
Thanks for the suggestion! Can you help me to better understand this approch please?
- Could you please provide more specifics regarding what Halo reports entail and what data can be retrieved from them?
- We are currently facing rate limit issues with the Halo APIs and have not received reports of any missing fields.
- Additionally, since report data is typically not immediate, I am concerned about whether this could impact ticket calculations in NextTicket.
R
RJ Madsen
Hello Micus, we're working on putting together a meeting with the products team to dive into the technical details but I can start with some details in this post:
• Halo reports are highly customizable data sources that can be configured to retrieve basically anything that’s stored in Halo. We’ve got full access to the database that stores ticket information. Data is retrieved through calling the /Reports endpoint, providing the report ID, and passing the loadreport parameter
• Last I checked in with support the rate limit was set to allow 450 requests per rolling 5-minute window. Not great if you’re doing a lot of big frequent queries for ticket data. I like to use reports to pull large quantities of data back with a single query to get around the rate limit as opposed to several calls to the /Tickets endpoint. I haven’t delved too deeply into the specific fields MSPBots is or isn’t pulling but by initial concern is about the limited overall ticket pool that can be fetched.
• A nice thing about Halo is the report data is immediate and up to date with whatever point in time the report was queried. On call it’s executing whatever SQL query makes up that report and pulls back the data