[
https://issues.apache.org/jira/browse/DISPATCH-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454334#comment-16454334
]
ASF GitHub Bot commented on DISPATCH-933:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/295
DISPATCH-933 - Undo changes made because this JIRA. RouterStats os no…
…w gone relaced with the old Router entity. This change has been backed out
because of backward compat issues
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-933-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/295.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #295
----
commit 328be727c8bd6c5a625d2e6d2dbba81cef6ee36b
Author: Ganesh Murthy <gmurthy@...>
Date: 2018-04-26T14:44:57Z
DISPATCH-933 - Undo changes made because this JIRA. RouterStats os now gone
relaced with the old Router entity. This change has been backed out because of
backward compat issues
----
> Introduce a new RouterStats entity and move all stats from the RouterEntity
> to the RouterStats entity
> -----------------------------------------------------------------------------------------------------
>
> Key: DISPATCH-933
> URL: https://issues.apache.org/jira/browse/DISPATCH-933
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 1.0.1
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: Backlog
>
>
> 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
>
> {noformat}
> [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"
> }
> ]
> {noformat}
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
