Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2847 Isolate requests to the Event Ingestion API from rest of the API
  3. OPT-3155

Respond with correct error code when we can't serve ingestion API requests

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha1, 3.0.0
    • None
    • backend
    • None

      When we can't serve a request due to the QoS filter, we should respond with the correct status code. CloudEvents spec says this should be a 429 and must include a `Retry-After` Header

      ATs:

      • We respond with an appropriate status code when requests can't be served
      • We include the Retry-After header when requests can't be served
      • The documentation is updated

        This is the controller panel for Smart Panels app

            [OPT-3155] Respond with correct error code when we can't serve ingestion API requests

            There are no comments yet on this issue.

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: