Read Ticket Management can be seen as a load balancing concept which ensures the stability of your database and prevents peak load scenarios that could potentially block your users. It gives you also the full control of your project’s performance.
We provide two kinds of read tickets:
UI Read Tickets
Define how many query requests can be performed from UI side at the same time
API Read Tickets
Define how many query requests can be performed from API side at the same time
Admin users can easily adjust the number of Read Tickets and steer the load distribution in Bosch IoT Insights. Each Read Ticket comes with the possibility to queue 5 query requests. So if you have 5 Read Tickets, 25 query requests can be queued.
For more information on Read Tickets, refer to:
Define the the number of Read Tickets used for your project.
See all the states of a query explained
Query History Chart
Monitor your Read Tickets to always have an overview of queued query times and queued Read Tickets. This helps you to detect possible bottlenecks and peaks and lets you decide whether you want to increase the number of Read Tickets.
Read Ticket limits
Error messages might occur on your dashboard in case too many queries have to be executed at once. Either increase the timeout or the number of Read Tickets.