DX Application Performance Management

Hi,

I am trying to record transaction in wily, but its not capturing any data.

I tried the following's to troubleshoot the issue, but no luck:

1) Enable all the trace option in Tim Server.
2) Sync time for all the collectors and MOM & Tim.
3) delete the web cache form the mom server.
4) in Tim logs data is showing on Tim server, but in Tim logs I found this error


" 16:07:48 2012 23609 ConnManager: recording stopped for 10.10.1.147, BrowserLanguagePattern="", MonitorId=, SessionId=700000000000000017
Sat Sep 8 16:07:51 2012 23609 WebServer: POST request for /tess/setrecorderconfig from 127.0.0.1
Sat Sep 8 16:07:51 2012 23609 WebServer: request forwarded from 10.10.1.147
Sat Sep 8 16:07:51 2012 23609 WebServer: loading recorderconfig
Sat Sep 8 16:07:51 2012 23609 ConnManager: recording started for 10.10.1.147, BrowserLanguagePattern="en-us,af*", MonitorId=700000000000000000, SessionId=700000000000000017, IgnoreIp="10.10.1.147"
Sat Sep 8 16:07:51 2012 23609 ConnManager: sessions to 10.10.1.147 will not be recorded
"

Kindly help me to resolve this issue.

Thanks in advance.

Shajada Rao

Make sure that you enable the Afrikaans language in the browser you're doing the transaction from. This is why we enable the browser language during the recording.
What this does in environments where there may be a lot activity, it should easily allow the TIM to pick up on your specific transactions from any others. I tend to run CEM from one browser (like FF) and do my transaction from IE.

-Hiko

Hi Hiko ,

Mant Thanks for your support.

This is already enable in browse language option, but still geeting same error.

Regards,
Shahzada RAO

Hi Rao


Which version of APM you are using


Cheers!!!

Gaurav

Dear Gaurav,

We r usnig 9.1.2


Rergards,
Shajada Rao

Shajada,

We are experiencing the same problem with version 9.1.1.0 and have opened a ticket with CA Support. In short, we see the transactions in the timlog.txt and when we do a Transaction Inspection on the TIM itself, we detect the ones that we are trying to record; but CEM itself claims to not encounter any record-able transactions.

We have this problem as well , and I too have an open ticket on it.

We just upgraded our 9.06 APM to APM 9.1.0.1

I can see the traffic in introscope just fine, even the transaction I am trying to record, but the recording doesnt catch it.

jakbutler wrote:

Shajada,

We are experiencing the same problem with version 9.1.1.0 and have opened a ticket with CA Support. In short, we see the transactions in the timlog.txt and when we do a Transaction Inspection on the TIM itself, we detect the ones that we are trying to record; but CEM itself claims to not encounter any record-able transactions.

Hi Jakbuler,

Thanks for response.

I have enabled all tim trace option, & here i am able to seen packet in tim. But still there is no transaction captured by CEM.

IN TIM log i am geeting this:

"Tue Sep 11 13:00:06 2012 9449 WebServer: loading recorderconfig
Tue Sep 11 13:00:06 2012 9449 ! Warning: RecorderManager: no recording session with id 700000000000000017 to stop
Tue Sep 11 13:00:06 2012 9449 ConnManager: recording stopped for 10.10.1.147, BrowserLanguagePattern="", MonitorId=, SessionId=700000000000000017
Tue Sep 11 13:00:09 2012 9449 Trace: timing out [10.10.1.59]:4574->[10.10.1.46]:7788
Tue Sep 11 13:00:09 2012 9449 Trace: [10.10.1.59]:4574->[10.10.1.46]:7788 closed by timeout
Tue Sep 11 13:00:09 2012 9449 Trace: open-components=0, total-components=0
Tue Sep 11 13:00:13 2012 9449 WebServer: POST request for /tess/setrecorderconfig from 127.0.0.1
Tue Sep 11 13:00:13 2012 9449 WebServer: request forwarded from 10.10.1.147
Tue Sep 11 13:00:13 2012 9449 WebServer: loading recorderconfig
Tue Sep 11 13:00:13 2012 9449 ConnManager: recording started for 10.10.1.147, BrowserLanguagePattern="en-us,af*", MonitorId=700000000000000000, SessionId=700000000000000017, IgnoreIp="10.10.1.147"
Tue Sep 11 13:00:13 2012 9449 ConnManager: sessions to 10.10.1.147 will not be recorded
"


Already raised an issue with ca support, but still no luck.

Regards,
Shahzada

You must properly configure the firewall on the machine where the APM is installed. For now, disable the firewall and try it.

If the foregoing, searches APM guides what should be the correct configuration of the firewall through the ports of the setting.

Greetings from Chile (South America)

Pablo Rodríguez
Entersoft Ltda.

Hi Ltda,

Right now there is no firewall, and all the apm servers and tim are on same subnet.

Regards,

After having a discussion with CSO about this, I'm starting to think this is an issue with some differences on how components are tagged by WTG and CEM.

If you upload your WTG scripts to CEM, then CEM will pick up your transactions. If you're relying on your CEM recordings, then WTG transactions are not reported.

The immediate workaround would be to promote your WTG scripts to CEM and define them as business transactions to a separate business application than your CEM recordings.

-Hiko

hdavis wrote:

After having a discussion with CSO about this, I'm starting to think this is an issue with some differences on how components are tagged by WTG and CEM.

If you upload your WTG scripts to CEM, then CEM will pick up your transactions. If you're relying on your CEM recordings, then WTG transactions are not reported.

The immediate workaround would be to promote your WTG scripts to CEM and define them as business transactions to a separate business application than your CEM recordings.

-HikoHI

Hi Hiko,

Many thanks for your support.

Could you please let me know in CEM where i need to upload WTG Scripts.

Regards,
Shahzada Rao

There may be a better way of doing this. But when I introduced WTG, I simply exported/imported all of my transactions that WTG duplicates and I put HTTP Header parameters on the identifying components. Basically I'm searching for the x-wtg-info parameter if it exists vs. doesn't. Seems to work fine for me and avoids inflating your "real" transactions.

This only works if you upload your WTG scripts and use them as business transactions. This does not work with CEM recordings.

Create a new business application and/or business service to hold your WTG transactions.

-Hiko

hdavis wrote:

Create a new business application and/or business service to hold your WTG transactions.

-Hiko

I have created a new business application & services, and enables all defect for monitoring. But still no luck in report front.

Warm Regards,
Shahzada

hdavis wrote:

Create a new business application and/or business service to hold your WTG transactions.

-Hiko

I have created a new business application & services, and enables all defect for monitoring. But still no luck in report front.

Warm Regards,
Shahzada