Uploaded image for project: 'Couchbase Monitoring and Observability Stack'
  1. Couchbase Monitoring and Observability Stack
  2. CMOS-446

Alert if a query is running to long

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • 0.3
    • None
    • cluster-monitor
    • None

    Description

      This was highlighted in CBSE-11959. Using system:active_requests we are able to see how long the query was running for: 

      "active_requests": {
      		 
        "clientContextID": "0f6a02b7af1b7b91",
      		 
        "elapsedTime": "10h22m48.77278988s",
      		 
        "executionTime": "10h22m48.772766703s",
      		 
        "node": "10.176.3.96:8091",
      		 
        "remoteAddr": "10.176.7.31:36382",
      		 
        "requestId": "24a9ca34-4cf1-4f5b-b342-b4e865fdcb6f",
      		 
        "requestTime": "2022-05-10T10:20:21.319Z",
      		 
        "scanConsistency": "unbounded",
      		 
        "state": "submitted",

      I think elapsedTime is more useful here than executionTime .

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            pvarley Patrick Varley (Inactive)
            pvarley Patrick Varley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty