How to Use Recorder and Playback Stages to Troubleshoot

Use the recorder and playback stages to capture the actual data of the search (query, results, or both).

Use this data to troubleshoot and reproduce the issue in other environments.

Use a recorder stage to see a detailed view of an executed query or to see the returned results. (For example, when troubleshooting.) 

The recorder stages capture, in JSON format, the executed query or the retrieved results and save these into separate files for each query or result.

The recorded file naming convention is a concatenation between the executed query text and the recording moment (date and time).

You can use a JSON editor to see and edit these files. (BA Insight recommends JSON Editor online.)

To overwrite the received query or the retrieved results with data that was previously captured by the recorder stages, use the matching playback stage.

• For example, use the matching playback stages in scenarios when you want to simulate a specific query or a results set that was captured in a different environment or configuration.

• These stages can also be used to determine whether a specific behavior is consistent between multiple environments or for configuration options

The recorded file naming convention is a concatenation between the executed query text and the recording moment (date and time).

To add the recorder and matching playback stage, go to How to Add Additional Search Engines.

Use the recorder and playback stages to perform the following operations:

• Query Recorder
  • Save the executed search queries.
• Query Playback
  • Overwrite the query with a previously captured query.
• Results Recorder
  • Save the received search results.
• Results Playback
  • Overwrite the search results with a previously captured results set

The recorded file name convention is a concatenation between the executed query text and the recording moment (date and time)