Bosch IoT Insights

Read Ticket limits

If you have a lot of widgets on your dashboard, they may take some time to execute the necessary query requests or they even fail to load and an error message like the following occurs:

images/confluence/download/attachments/2359884080/read_ticket_error_message.png

There are possibilities to avoid this from happening:

Increasing the queuing timeout

Proceed as follows

  1. Click the Explore menu item.
    → The Data Explorer tab is opened by default and displays existing query templates if already created.

  2. Select the corresponding query template.

  3. In the Read Ticket Queuing Timeout field, enter or select the length of the timeout in minutes.

    The default and minimum timeout is one minute, the maximum timeout is one hour (60 minutes).

    In case of a dashboard containing several widgets that execute several queries, it is advisable to increase the value. Otherwise, depending on the current read ticket limit, the queries that end up in the queue, waiting for a ticket to become free, will be discarded because of the short default timeout. That would lead to several widgets without a query result and to the error message displayed above.

  4. Click the Save button.
    → The query template has been adjusted.

Increasing the number of Read Tickets

As the amount of Read Tickets affects the pricing, refer to the Bosch IoT Insights' service plans.

Proceed as follows

  1. Click the Admin menu item.

  2. Click the Project menu item.
    → The General Settings tab is displayed.

  3. Scroll down to the Read Tickets section.

  4. In the UI Tickets field, enter the amount of query requests that can be performed from UI side at the same time.

  5. In the API Tickets field, enter the amount of query requests that can be performed from API side at the same time.

  6. Click the Save button.
    → The read tickets are updated.