Rollbar

@rollbar

Code-first observability that connects errors, replays, and releases in one place.

San Francisco, CA

rollbar.com

Replies Reposts Media

Rollbar
@rollbar
Sep 18
Before markets opened on Aug 1, 2012, Knight Capital's systems sent 97 automated emails about a router error. None were built to page anyone. The next 45 minutes cost $460M, per the SEC's order. In Rollbar you pick which errors page a human, and who.
Rollbar Error Monitoring | Know when something breaks and why
From rollbar.com
Rollbar
@rollbar
Sep 17
Wiring an agent to real production errors is the easy half. Running the tests is where our Resolve beta still bites. Complex suites cannot always stand up in an ephemeral environment, and then you get a fix with no test evidence behind it.
Rollbar Resolve | Automated Bug Fixing and Error Resolution
From rollbar.com
Rollbar
@rollbar
Sep 16
An agent hands you a patch for a production error. Nothing has run it. A fix is only worth trusting once your test suite has executed against it and the results are on the pull request. That is what Rollbar Resolve ships.
Rollbar Resolve | Automated Bug Fixing and Error Resolution
From rollbar.com
Rollbar
@rollbar
Sep 15
Your agent gets the stack trace and guesses. Give it the 30 seconds before the throw instead: the click, the failed fetch, the retry, then the error. Most impossible production bugs stop being impossible once the sequence is in the prompt.
Rollbar
@rollbar
Sep 14
An AI coding agent has no sense of priority. It works on the error you paste in, whether that one fired twice last night or forty thousand times. What is breaking right now, ranked, exists only in production. Our MCP server gives the agent that list.
Rollbar MCP Server | Model Context Protocol for Observability
From rollbar.com
4