| Author |
Message
|
| Esa |
 Posted: Mon Apr 15, 2013 7:22 am Post subject: wrong monitoring profile |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Hi,
I have created a monitoring profile, set up a configurable service for it and assigned that to a flow.
I get the correct profile when I run
| Code: |
| mqsireportflowmonitoring BROKER8 -e ESA -f Foo -x -p <output file> |
so I guess I have done everything right.
However, when I send a message to the flow, I get a monitoring event that does not match my profile. I think it might match the default monitoring profile, although there is more stuff than I would expect.
My event source looks like this:
| Code: |
<p:eventSource p:enabled="true" p:eventSourceAddress="[b]MQInput.transaction.Start[/b]">
<p:eventPointDataQuery>
<p:eventIdentity>
<p:eventName p:literal="MQInput.transaction.Start" />
</p:eventIdentity>
<p:eventCorrelation>
<p:localTransactionId p:queryText="$Root/MQMD/MsgId"
p:sourceOfId="query" />
<p:parentTransactionId p:queryText="$Root/MQMD/CorrelId"
p:sourceOfId="query" />
<p:globalTransactionId p:queryText=""
p:sourceOfId="generated" />
</p:eventCorrelation>
<p:eventSequence p:name="creationTime" />
<p:eventFilter p:queryText="true()" />
<p:eventUOW p:unitOfWork="independent" />
</p:eventPointDataQuery>
[b]<p:bitstreamDataQuery p:bitstreamContent="none" p:encoding="none"/>[/b]
</p:eventSource> |
and this is the event that I get:
| Code: |
<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="8002" wmb:eventSchemaVersion="6.1.0.2">
<wmb:eventIdentity wmb:eventName="[b]transactionStart[/b]"/>
<wmb:eventSequence wmb:creationTime="2013-04-15T15:08:00.302Z" wmb:counter="1"/>
<wmb:eventCorrelation wmb:localTransactionId="414d5120514d38202020202020202020a7996b512000611e" wmb:parentTransactionId="" wmb:globalTransactionId=""/>
</wmb:eventData>
<wmb:messageFlowData>
<wmb:broker wmb:name="BROKER8" wmb:UUID="8abc69a2-7625-492e-bf68-075f472a5de7"/>
<wmb:executionGroup wmb:name="ESA" wmb:UUID="e67e3aaf-3501-0000-0080-b0cd849289c9"/>
<wmb:messageFlow wmb:uniqueFlowName="BROKER8.ESA.Foo" wmb:name="Foo" wmb:UUID="320d9e0d-3e01-0000-0080-acb2c75a010b" wmb:threadId="11136"/>
<wmb:node wmb:nodeLabel="MQInput" wmb:nodeType="ComIbmMQInputNode" wmb:detail="IN"/>
</wmb:messageFlowData>
</wmb:eventPointData>
<wmb:bitstreamData>
[b]<wmb:bitstream wmb:encoding="base64Binary"><!-- bitstream content -->
</wmb:bitstreamData>[/b]
</wmb:event> |
The event name doesn't match my profile, and the event contains the binary payload even if I have told that I don't want it. So it's not generated with my profile.
The flow file and the compiled flow in the bar file don't have any monitoring enabled.
There is nothing monitoring-related in user trace or system log.
Broker and Toolkit version 8.0.0.2
Windows 7 Professional 64-bit |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Apr 15, 2013 7:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Welcome to the somewhat dark and murky waters of FlowMonitoring.
"There be demons ahead"
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 15, 2013 10:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
It may not match your profile, but have you defined it in the toolkit and compiled and redeployed the flow since?
Make sure you do not define any monitoring in the toolkit for a flow that is to be monitored via a configurable service.
Hope it helps 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Esa |
| Posted: Mon Apr 15, 2013 12:03 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| fjb_saper wrote: |
It may not match your profile, but have you defined it in the toolkit and compiled and redeployed the flow since?
Make sure you do not define any monitoring in the toolkit for a flow that is to be monitored via a configurable service.
Hope it helps |
I have't defined any monitoring properties in the flow or in the bar file. And I thought a monitoring profile overrides what you have defined in the flow. That's what the InfoCenter says:
| Quote: |
| Use a monitoring profile to override the monitoring properties of a message flow that has already been deployed, as an alternative to redeploying the BAR file. The monitoring profile completely replaces all monitoring properties. |
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 15, 2013 12:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Esa wrote: |
I haven't defined any monitoring properties in the flow or in the bar file. And I thought a monitoring profile overrides what you have defined in the flow. That's what the InfoCenter says:
| Quote: |
| Use a monitoring profile to override the monitoring properties of a message flow that has already been deployed, as an alternative to redeploying the BAR file. The monitoring profile completely replaces all monitoring properties. |
|
Let me try and explain that to you. I would expect a new deployment to change / invalidate / add to the monitoring profile. If nothing is defined the profile remains in effect.
It is however somewhat difficult to say without testing it.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mapa |
| Posted: Mon Apr 15, 2013 9:19 pm Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
As soon as you have associated your flow with a monitoring profile it will override the monitoring defined in the flow, even if you redeploy the flow.
I have not experienced any problems with monitoring profiles as you describe Esa, haven't tried it on my upgraded 8.0.0.2 though but it works on 8.0.0.0 on Windows 7. I will try to check if it still works on FP2 later today.
Here is how I do it:
| Code: |
mqsicreateconfigurableservice <brokerName> -c MonitoringProfiles -o <profileName>
mqsichangeproperties <brokerName> -c MonitoringProfiles -o <profileName> -n profileProperties -p <profileFileName>
mqsichangeflowmonitoring <brokerName> -e <executionGroup> -f <messageFlow> -m <profileName>
mqsireportflowmonitoring <brokerName> -n -e <executionGroup> -f <messageFlow>
mqsichangeflowmonitoring <brokerName> -e <executionGroup> -f <messageflow> -c active
|
I've actually developed a Java back-end with a REST API with CRUD operations for monitoring profiles + activate/inactivate flow monitoring on our test server that works fairly well. Hoping that one day IBM will fix my RFE for adding this to the REST and/or Java API in the broker itself, since you now need mqsi-commands to work with monitoring profiles  |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Apr 16, 2013 12:23 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Thank you very much, mapa.
I had done everything the same way you did, execpt that I combined the two mqsichangeflowmonitoring calls into one.
And I hadn't used the -n switch with mqsireportflowmonitoring.
When I did, I got a listing of all defined event sources for the flow and could verify that they were actually my event sources,
but the names were not the ones I had defined.
I decided to validate my profile against the schema. And had a lot of problems with it. Finally I found out what was wrong.
I had copied my profile from InfoCenter and modified it to fit my purposes. Now, the version number in the namespace declaration in the InfoCenter example is wrong.
It's 6.1.0 while the broker is using 6.1.0.3.
When I corrected that everything worked.
It's obvious that the broker does not validate the profiles that get imported with mqsichangeproperties.
I have submitted feedback about the InfoCenter example code.
See the event message above. The version in the namespace is 6.1.0, but the eventSchemaVersion is 6.1.0.3.
If you check the MonitoringProfile.xsd, you will see that the version number in the namespace is 6.1.0.3.
So there is a mismatch. The profile and the event are using differrent namespace versions. I guess IBM has some good reason for that... |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Apr 16, 2013 2:22 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Ah, OK, great you got it working and that you provided feedback to IBM.
I and another mqseries.net user had PMRs against IBM some time ago (should be in some of the posts here) that in WMBT8 the schema for the monitoring profiles was missing from the Monitoring example.
It is there since FP1 now and it is correct.
I validate against this schema before sending the data to my back-end just in case... |
|
| Back to top |
|
|
|
|
