The original KB (TEC598248) was a checklist for investigating transaction discovery issues. This update offers a more procedural approach.
This approach typically resolves most transaction discovery recording issues.
Step 1: Are things running?
- Is a TIM available, running, and seeing traffic?
- Is the database operational and able to read and write transactions?
- Is the Transaction Discovery Service running? Check Transaction Discovery pull down option for the TIM Collector under the Services Tab.
- Is the TIM Collector/TIM having performance issues?
Step2: Is something filtering out the traffic?
- Are the private keys correct and decoding the transactions?
- First, Are you seeing the transaction on the TIM in tcpdump or in a packet capture (pcap) file?
- Second, does the transaction appear in the TIM logs?
Step 3: What's in the Transaction Discovery configuration?
- Is the template enabled?
- Is the definition unique or overlaps another definition?
- If it is a catch-all definition, is it at the bottom of the list?
- Are all the parameters marked as required?
- Are there too many parameters?. (Each one is an AND condition, so all must be present to be recorded.)
- Is the URL Path too specific? (So /* will work but not /foo if the url is /pharmacy)
- Is the content type matching? (Such as text/xml will not be matched with text/tml. But it will match with text/* or *.
- See if you can record at all by doing a catch all (Path /*), then get more specific.
- Start with one definition and add additional definitions as needed.
- Always check to see if services running, servers are up, and url is showing up on the network before looking at Transaction Discovery configuration
Note that some of these steps apply to RTTM as well since they both run on the same Collector.