Major Tighter integration is needed for things like naming conventions used by the cli tools. For example, running qdstat -l or qdstat -a displays non-prefixed address names:
[root@node11 ~]# qdstat -l Router Links type dir conn id id peer class addr phs cap undel unsett del presett acc rej rel mod admin oper =========================================================================================================================================== endpoint in 71 143 mobile exampleQueue 0 250 0 0 0 0 0 0 0 0 enabled up endpoint in 85 170 mobile $management 0 250 0 0 1 0 1 0 0 0 enabled up endpoint out 85 171 local temp.+6mblcbSFjWACVu 250 0 0 0 0 0 0 0 0 enabled up [root@node11 ~]# qdstat -a Router Addresses class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc ================================================================================================================ local $_management_internal closest 1 0 0 0 0 0 0 19 19 mobile $management 0 closest 1 0 0 0 82 0 0 82 0 local $management closest 1 0 0 0 0 0 0 0 0 mobile exampleQueue 0 balanced 0 0 0 0 0 0 0 0 0 local temp.mNN0xuaQfyLSUTE balanced 0 1 0 0 0 0 0 0 0
However, if I try to use qdmanage READ to get the details of a listed address, the query fails:
[root@node11 ~]# qdmanage read --type=org.apache.qpid.dispatch.router.address --name=exampleQueue NotFoundStatus: Not Found
Instead, I have to prefix the name to find the details:
[root@node11 ~]# qdmanage read --type=org.apache.qpid.dispatch.router.address --name=M0exampleQueue
{
"subscriberCount": 0,
"deliveriesEgress": 0,
"name": "M0exampleQueue",
"deliveriesIngress": 0,
"transitOutstanding": null,
"remoteCount": 0,
"inProcess": 0,
"deliveriesFromContainer": 0,
"deliveriesTransit": 0,
"containerCount": 0,
"key": "M0exampleQueue",
"distribution": "balanced",
"trackedDeliveries": 0,
"type": "org.apache.qpid.dispatch.router.address",
"deliveriesToContainer": 0,
"identity": "M0exampleQueue",
"remoteHostRouters": []
}
There is no indication given that some prefix must be prepended to the address name to resolve the entity. I was able to figure it out by running qdmanage query, but this is unwieldy on a system with thousands of addresses and link routes.
It would be nice if the qdmanage query functionallowed filtering by the name or identity parameters with wildcard support.
- relates to
-
ENTMQIC-2598 Ability to filter output of Interconnect management tools (qdstat, qdmanage)
-
- New
-
