Operations | Monitoring | ITSM | DevOps | Cloud

Recently someone on our team opened a traffic snapshot and found an HTTP request that was captured with our eBPF capture agent, nettap. Our protocol dissector parsed most of the response correctly, but that correctness ended once the response headers were processed. What they ended up with was a recording of an HTTP request/response where the response body was just an incorrect collection of garbage binary data when it should have been JSON text.

Billing has always been one of the parts of running an MSP that doesn't scale on its own. More endpoints, more tickets, and more monitors under management all mean more usage to track—and for most MSPs, that usage still gets tallied by hand before an invoice can go out. Not anymore. We're rolling out the MSP Central billing module, powered by our integration with Zoho Billing—and it's live with usage-based billing from day one.

The NAS Died. My WhatsUp Gold Server Died With It. WhatsUp Gold 360 Still Alerted Me. A real home-lab failure shows why always-on external monitoring and cloud-originated notifications matter when the local monitoring stack becomes part of the outage. On April 13, 2025, the NAS providing NFS storage to several virtual machines in my Proxmox lab locked up and halted.

Terraform gives you two ways to express the same infrastructure. You can declare resources directly, or you can wrap them in a module and call that module with inputs. Both produce identical cloud objects. The choice is not about capability, it is about where you want the complexity to live and who you want to be responsible for it. Most teams get this decision wrong in one of two directions.

TL;DR Agent projects turn into infrastructure projects fast. Managed agent platforms handle memory, integrations, scheduling, and scaling so builders can focus on the agent itself.