How it works
Dynamically add logs and snapshots to your live app from IDE
With a few clicks and without issuing any hotfixes - skip the deployment and CI/CD pipeline.
Virtual, non-breaking “breakpoints” (logpoints) extract all the data you need for investigation and understanding the state of your application - without affecting code execution or altering the code.
Explore traces from live requests as they occur
Receive information on variables and their values, arguments passed to methods/functions and their return values directly in your IDE.
Understand the conditions that led to a specific bug
See and understand the state of your software at any point in time. Move forward and backwards through how your code was executed.
See it in action
Advantages of continuous debugging
Increase developer productivity
and resolve bugs faster
Pinpoint error root causes instantly
Spend less time on issuing hotfixes and redeployments to debug production issues.
Save time on identifying and reproducing issues
Skip instrumenting the code (manually adding log statements) and get a faster feedback loop. Gain visibility into what’s happening immediately.
Focus more on value creating tasks
Reduce time spent on production maintenance tasks.
Empower your team
Allow support engineers, operations engineers, SREs and service owners to react fast to production issues, by providing them with a better debugging experience and easier way to understand the codebase.
Improve the collaboration between development and operations teams, allowing operations teams to quickly identify application owners.
Increase customer satisfaction and improve experience
Understand your software
Allow even the most junior of developers to understand the codebase they’re working on.
Seeing the whole 'dataflow history' (how a specific value flows through your program) makes learning a lesser-known codebase much easier and allows one to see how individual lines of code impact the behavior of running software.
Improve troubleshooting workflow
Unpredictability of production errors means that more often than not appropriate log lines are missing and prevents full dataflow analysis (determining how a value ended up in the location it did). Developers can't instrument everything and over-aggressive instrumentation would lead to maintenance overheads. Continuous debugging enables tracing of the application execution flow without the need to instrument the source code with additional log statements and redeployments, and gives full details of program state at any point in time.
Frequently asked questions
How it works under the hood? Are there any libraries that should be added to my project or other dependencies?
- PHP extension to handle diagnostic info retrieval
- PHP library that interacts with the PHP extension and sets up info retrieval
- Agent (daemon process that runs separately and forwards gathered diagnostics info)
What are the speed implications? What kind of performance overhead is there?
What about data security and privacy?
How is this different from error tracking software that I already use? (e.g. Bugsnag, Flare, Sentry)
My team is already using Xdebug. How is this different?
Is this the right solution for me? ⚠️
- Larger than average codebase
- Mission-critical services that require fast error resolution
- Errors can't be reproduced easily in a test environment (including time-consuming data replication or prohibited copying due to data sensitivity)
- Move-forward mentality (instead of performing rollbacks bugs are being solved quickly)
- Frequent or complex business-logic related errors that take time to investigate
- Missing instrumentation - understanding root cause of errors requires adding additional or new log statements to the code
- Deployment process (CI/CD) takes longer than a few minutes and you want to shorten the feedback loop and receive output from the new logs immediately
Sign up for private beta access
We're currently in a closed beta. Please sign up for the waitlist or if you just want to receive product updates.
Alternatively please feel free to reach out to us directly at [email protected].