Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1848

Give warning of too large reports

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 2.5.0-alpha1, 2.5.0
    • None
    • backend, frontend
    • None

      AT:

      • the number of datapoints that a report can evaluate is restricted to 1000
      • if a report evaluation would contains more than the maximum allowed databpoints, then only the first 1000 entries are shown and a warning is displayed to the user similar to the one that already exists in the raw data report
      • changes in the rest api are adjusted in the documentation
      • there is documentation in the user guide about this behavior

      Context:
      When the user creates a report, he usually selects a view, groupby and visualize as and the report is displayed. However, there are scenarios where there are a lot of datapoints to display, e.g. if you grouped by StartDate: Hour with data from several years or grouped by a variable with a lot of distinct values.

      Depending on the visualization and browser, this might create problems where the page appears to become unresponsive while the huge dataload is transferred and processed.

      Also there is a back-end dimension to this: if there are too many datapoints, Elasticsearch will reject to evaluate a query in the future. Also it can crash Optimize/Elasticsearch if the queries evaluate too many datapoints.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: