Muru: tracing in the toolbar
Turning on tracing with wrapture under muructl run, so the development toolbar shows each request's calls, SQL queries and outbound calls, and finding an N+1 query with it.
Turning on tracing with wrapture under muructl run, so the development toolbar shows each request's calls, SQL queries and outbound calls, and finding an N+1 query with it.
The development toolbar Muru adds to every HTML page under muructl run, with each request's timings, logs and errors, and nothing changed in the application.
How Muru's conditions watch its own figures, such as the share of requests from AI crawlers or the health of a payment service, and trigger overlays that respond and then stop once it is over.
How Muru's overlays lay temporary changes over a site's configuration, by hand or on a schedule, for backups, maintenance windows, timed cutovers and busy periods.
How the Muru daemon takes an idle release down to no workers, then to no processes at all, what the next request pays at each stage, and how that interacts with a node's worker budget.
How the Muru daemon decides how many workers a release needs, and the diagnosis that says when the answer isn't more workers but a change to the release.
Follow my journey and get notified about new posts and projects.
You can also follow this site via RSS feed.
If you're a Python developer, you might also want to check out the RSS feed available from planetpython.org for posts from various Python developers, including myself.
Support my open source work and help me continue creating tools that benefit the developer community.
Sponsor on GitHub