When we get customer issues with Smart View often the first thing we ask for is a “Fiddler” log. The first response is often “What is Fiddler?” so I thought I would take some time to go over what fiddler is and how it can be used to debug a Smart View issue.
What is Fiddler?
http://www.fiddler2.com/fiddler2/
From the fiddler web site: “Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect traffic, set breakpoints, and "fiddle" with incoming or outgoing data.”
Simply put for Smart View; it is a tool that can be used to monitor the HTTP/XML traffic that Smart View uses to communicate with most of it’s providers.
Example Request/Response for Smart View:
How To Use Fiddler with Smart View
- Download and install fiddler on the client where you are experiencing the Smart View issue. http://www.fiddler2.com/fiddler2/ – Remember this is a client tool and needs to be installed on the same machine as the Smart View add-in. There is no need to install fiddler on any server (provider).
- Launch Fiddler and make sure you are capturing traffic (File | Capture Traffic)
- Recreate the Smart View issue while fiddler is capturing traffic. When doing this is best if other applications are closed as many application use http requests and these will also be captured. Things like email, iTunes, and any browser based application. This will not be an issue but when sharing logs with support you do not want to share traffic dealing with emails or other personal items. Plus it will be a lot easier to read if the only traffic is related to Smart View.
- The last step is to share these logs with Smart View support or development. It is always best to have this along with a SR logged. This way the issue can be properly tracked.
How to Read the Fiddler Log
There are tons of options in Fiddler but there are a few things we are looking for and a few areas in Fiddler where we find this information.
Statistics:
Inspectors:
Inspectors has many sections be we are usually looking at the XML sections and seeing what is happening with each request/response to narrow down the issue.
Fiddler is a great tool for debugging but be sure to have a support case opened so that support can help guide you and interpret what you are seeing. For additional details you can review a short tutorial on this same topic. http://www.oracle.com/webfolder/technetwork/tutorials/demos/hyp/CollectingLogs/CollectingLogs.htm
6 comments:
Hi Matt. Just curious what issues this has helped you resolve?
Too many to list but everything from timeout issues, network issues, token issues and provider issues. The key is it can easily tell you where the issues is (client or provider) and often times you will see more details about an error from the provider.
Does this allow you to capture the MDX for a query?
That sort of traffic mostly occurs between APS and Essbase. In the case of query designer you might see some snippets but not full MDX statements. Most SV calls do not issue MDX anyhow.
Yes...we do get a lot of Smart View issues with some of the users.
Client doesn't accept to install the software, is there any other alternative for this?
If you cannot install fiddler then Smart View logging is your best bet. In the newest versions of SV (11.1.2.1 and up) logging will include this XML exchange.
Post a Comment