Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-933

Introduce a new RouterStats entity and move all stats from the RouterEntity to the RouterStats entity

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.1
    • Fix Version/s: Backlog
    • Component/s: Management Agent
    • Labels:
      None

      Description

      Right now all router statistics attributes like deliveriesIngress, rejectedDeliveries, droppedPresettledDeliveries etc. reside in the router entity..

       

      Router Config Attributes  like saslConfigPath, saslConfigName, helloIntervalSeconds, helloMaxAgeSeconds etc. also reside in the router entity

       

      When a qdmanage query is issued, the results do not include the router config attributes. This is because the core does not have access to these attributes

       

      [gmurthy@localhost qpid-dispatch]$ qdmanage QUERY --type=router
      [
        {
          "linkRouteCount": 0,
          "droppedPresettledDeliveries": 0,
          "rejectedDeliveries": 0,
          "autoLinkCount": 0,
          "id": "Router.A",
          "presettledDeliveries": 0,
          "area": "0",
          "deliveriesIngress": 1,
          "deliveriesIngressRouteContainer": 0,
          "acceptedDeliveries": 1,
          "version": "1.0.0",
          "linkCount": 2,
          "connectionCount": 1,
          "addrCount": 4,
          "deliveriesEgressRouteContainer": 0,
          "nodeCount": 0,
          "modifiedDeliveries": 0,
          "identity": "1",
          "deliveriesEgress": 0,
          "releasedDeliveries": 0,
          "name": "Router.A",
          "type": "org.apache.qpid.dispatch.router",
          "deliveriesTransit": 0,
          "mode": "standalone"
        }
      ]
      

       

      The solution to this problem is to create a new entity called RouterStats and move all the statistics related attributes to RouterStats. This RouterStats entity will be handled by the C management agent.

       

      The old Router entity which is currently handled by the C agent will be handled by the Python agent instead.

        Attachments

          Activity

            People

            • Assignee:
              gmurthy Ganesh Murthy
              Reporter:
              gmurthy Ganesh Murthy
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: