Thundra was born out of the observability pains experienced by developers in the Opsgenie engineering team. The journey to Thundra’s creation started by helping the serverless community with monitoring, observability, and then debugging. Later, Thundra started to serve developers who run and maintain their applications on any plain, not just in serverless computing.
Today, applications are increasingly built using services provided by third parties. While the complexity of applications increases, developers are still expected to manage that complexity before and after production. Although there are best practices (and multiple tools) that have been designed to simplify the complexity and to resolve issues after code is in production, managing pre-production complexity for modern applications is still a problem with few insufficient solutions.
Since Thundra adheres to our motto of being a developer’s best friend throughout the complete development cycle, we focus on the most intense part of the cycle: pre-production. Troubleshooting issues before production is always better for developers, as this keeps the stress of production issues from becoming overwhelming. Thundra Sidekick removes debugging burdens and enables developers to put tracepoints to code, which doesn’t break execution but instead takes snapshots for developers to examine later. This tool takes things to the next level by displaying the distributed trace, providing developers with the ability to make hotfixes and reload without having to redeploy.