| Author |
Message
|
| goffinf |
 Posted: Fri Feb 26, 2010 4:58 am Post subject: Flowstats and non MQ Input nodes |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Surprisingly I can't seem to find a definite answer to the question of whether flowstats can be collected for flows that do NOT use an MQInput node.
Perhaps I should clarify further. I want to be enable stats & accounting messages to be published to the defined topic to which I have subscribed in cases where I use an HTTPInput, SOAPInput and in some cases a custom input node.
A small amount of testing appears to suggest that when I invoke a flow through MQInput the S&A messages are successfully published and received by my subscriber queue, but not if I switch to HTTPInput.
I'm having a hard time accepting that fact so I'm hoping I'm just plain wrong and there's another reason why they are emitted in the HTTP case.
Here's what I'm using to turn flowstats ON :-
mqsichangeflowstats WBRK61_DEFAULT_BROKER -a -g -j -c active -t basic -n advanced -o xml
Can anyone provide a definitive answer please.
Thanks
Fraser. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 26, 2010 5:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you verified that you don't get a message, or is it just that the content is different enough that the message is not being parsed as you'd expect?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 26, 2010 5:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| I imagine the behavior is different in different versions, and I'm sure that it's *better* in version 7 than it is in, say, version 5. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Feb 26, 2010 6:35 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Each input node needs to be enabled for stats collection.
I can't recall the v5 state of affairs, but I'm pretty sure that all built-in input nodes in Broker v7 are enabled for stats collection. |
|
| Back to top |
|
|
| Mandeep |
| Posted: Fri Feb 26, 2010 7:26 am Post subject: |
|
|
Apprentice
Joined: 03 May 2004
Posts: 33
|
We are on Ver 6.1 and able to generate A&S for HTTP based Flows.
Example Topic:
$SYS/Broker/ESBBROKER/StatisticsAccounting/#/DEV_EG/CTWrapper |
|
| Back to top |
|
|
| goffinf |
| Posted: Fri Feb 26, 2010 8:51 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Ok, sorry not quite enough detail :-
Version: 6.1.0.3
I have a subscription to the topic :-
$SYS/Broker/WBRK61_DEFAULT_BROKER/StatisticsAccounting/#
as shown by this output from mqsibrowse :-
| 2010-02-17 13:58:4100017 | WBRK61_DEFAULT_QUEUE_MANAGER:NUGI.FLOWSTATS.SUBSCRIPTION | *Unlimited Expiry * | 2010-02-17 16:47:05 | 772 | $SYS/Broker/WBRK61_DEFAULT_BROKER/StatisticsAccounting/# | | | applIdentityData wbimbv61 |
which, when flowstats are on, should send messages to the queue :-
NUGI.FLOWSTATS.SUBSCRIPTION
I just turned flowstats ON for the flow (Test) in the execution group (tuning) using :-
mqsichangeflowstats WBRK61_DEFAULT_BROKER -a -e tuning -f Test -c active -t basic -n advanced -o xml
Popped a message onto the flow's MQ Input queue (with RFHUtil) and yes there were messages on NUGI.FLOWSTATS.SUBSCRIPTION.
Turned flowstats OFF with :-
mqsichangeflowstats WBRK61_DEFAULT_BROKER -a -e tuning -f Test -c inactive
and verified with :-
mqsireportflowstats WBRK61_DEFAULT_BROKER -a -s -g -j
which did indeed report INACTIVE for all the flows.
All good so far ...
Then turned flowstats on for my second flow with the same command as above but with a different flow name (this ones got a HTTPInput). Verified with mqsireportflowstats, which showed ACTIVE for the flow. Sent a message though with my HTTP client and ..... nothing on NUGI.FLOWSTATS.SUBSCRIPTION ????
Turned flowstats OFF for the HTTP flow, and then ON for MQInput (Test), but now that one isn't sending flowstats messages through again ?
Hmmm ... its gotta be something stupid that I'm doing ?
Can anyone spot what it is.
Thanks
Fraser. |
|
| Back to top |
|
|
| goffinf |
| Posted: Fri Feb 26, 2010 9:44 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Ok, a bit more info.
It now appears that flowstats DO work ok for flows that have HttpInput nodes, since eventually (after restarting the Broker) the flowstats publications for this flow appeared on my subscription queue, as did some others from the flow that has the MQInput.
So the problem now seems to be, why are the publications taking so long to come through. Is there any setting for how often broker publishes flowstats messages ?
Regards
Fraser. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 26, 2010 1:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I believe there is a default statistics publish interval. Look it up in the infocenter.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Mandeep |
| Posted: Sun Feb 28, 2010 11:25 pm Post subject: |
|
|
Apprentice
Joined: 03 May 2004
Posts: 33
|
| There are 2 types of A&S messages. One is Archive and other is snapshot. The mqsichangeflowstats command with -a option is for archive. i.e. broker would generate the A&S message when it stops. And with snapshot (-s option), it has a default time of 20 sec (which you can probably change) to generate the A&S messages. |
|
| Back to top |
|
|
| goffinf |
| Posted: Tue Mar 02, 2010 3:19 pm Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| Mandeep wrote: |
| There are 2 types of A&S messages. One is Archive and other is snapshot. The mqsichangeflowstats command with -a option is for archive. i.e. broker would generate the A&S message when it stops. And with snapshot (-s option), it has a default time of 20 sec (which you can probably change) to generate the A&S messages. |
Thanks. There are settings for archive too and these can also be changed. What I have done thus far picks up from some advice that was given in one of the many posts that I have looked at, and that is, when using archive, you can cause Broker to 'flush' the flowstats collected thus far by re-issue'ing the mqsichangeflowstats command with at least one argument changed. I have tested this and it seems to worked consistently so will suffice for my purpose. Interestingly turning flowstats OFF (inactive) doesn't have the same effect so they only appear after the interval set or when the execution group is recycled. |
|
| Back to top |
|
|
|
|
