Trooper v3.0 — circuit breaker + observability headers (based on your feedback)

Introducing Trooper v3.0: Enhanced Resilience and Observability in Service Requests

We are excited to announce the release of Trooper version 3.0, a significant update driven by valuable feedback from our community. This latest iteration introduces key features aimed at improving reliability and transparency in service interactions, all while maintaining Trooper’s core simplicity and efficiency.

New Features in Trooper v3.0

1. Circuit Breaker Mechanism
   To prevent unnecessary delays and resource wastage, Trooper now includes a circuit breaker that automatically skips a provider after three consecutive failures within a 60-second window. This proactive approach ensures that requests are routed more intelligently, reducing the chances of hitting non-responsive or problematic providers repeatedly.

2. Enhanced Observability with Log Lines
   Understanding what happens during each request is crucial for debugging and monitoring. Trooper now outputs detailed log lines in the terminal for every request, clearly indicating the steps taken and the decisions made. This transparency simplifies troubleshooting and provides immediate insights into the request lifecycle.

3. Response Header Summary
   Every response from Trooper now includes an X-Trooper-Summary header containing a succinct, one-line overview of the request’s outcome and the actions performed. This feature aids in quick assessments and can be particularly useful for integrating Trooper into larger observability workflows.

Simplicity and Performance

Despite these enhancements, Trooper continues to operate as a single, dependency-free Go binary, ensuring easy deployment and minimal overhead.

We invite you to explore Trooper v3.0 and see how these new features can improve your service reliability and debugging workflows.

For more details, visit the GitHub repository: github.com/shouvik12/trooper