potpie-debug-memory

You can retrieve historical context for debugging by searching for prior occurrences and correlating current issues with service topology changes. This streamlines the investigation process by matching your expanded symptom query against past infra events.

Correlating system failures with change timelines requires accessing historical data and service neighborhoods. By querying prior occurrences and viewing service topology, you can efficiently trace current symptoms back to previous infrastructure modifications.

Yes, you need a Potpie-enabled environment and the Potpie CLI installed. This setup is required to execute the graph reading commands, search subgraphs by symptom, and retrieve the historical occurrences needed for troubleshooting.

To search prior occurrences by symptom, run the potpie graph read command with the debugging subgraph. Specify the view as prior_occurrences, input your expanded symptom query, set the scope to your service name, and limit the results.

Yes, you can record and share debug memory to document bug fixes and verification history. This allows you to save historical occurrences and timeline correlations, creating a reference for future troubleshooting and system analysis.

The context retrieval process is limited to the scope of your Potpie-enabled environment and the data indexed within it. Troubleshooting effectiveness depends on the availability of historical occurrences, service topology data, and accurate symptom queries.