Operations | Monitoring | ITSM | DevOps | Cloud

We’re back with another major SIGNL4 update! This release brings new features and improvements across Call Routing, User Profiles and Management, Stakeholder Communication, and AI.

How much of your database delivery can you actually see? For most teams, the picture is scattered. Deployment status lives in CI logs and scripts. Drift appears outside the process. And with AI multiplying the volume and speed of changes moving through pipelines, the risk that comes with low visibility rises with every release.

The State of Agent DLC 2026 asked 700 organizations already running AI agents how confident they were across five domains: testing, security, inventory, cost, and rollback. Confidence came back between 74% and 77% in every domain we tested. In most of them, the controls that would justify it are not there. “No, I don't have a nanny cam, but I'm sure my kids are OK.

Ask a platform team why their application logs aren't in their observability backend and you'll often get a one-sentence answer: And, that's where the conversation ends. The logs stay in a silo. Or, they don't get collected at all. The team loses the troubleshooting signal, and nobody revisits the decision because the alternative looks like a compliance violation. Application logs in healthcare, aviation, insurance, and retail are full of personal information that should not be stored in plain text.

Learn why modern IT complexity can slow incident response and how observability, AIOps, operational context, and automation can help teams detect, investigate, and resolve issues faster.

Certification against ISO 20000 puts your service desk under audit. That audit runs on what your team wrote down at the time. The standard does not care how your team describes its process. It does not care which ITIL 4 practices you adopted. It cares what your records show, so auditors spend their time in your tickets, approvals, and review minutes. In this blog, you will: You will finish knowing which of your records would survive an audit.

Most log management tools bill you on log ingestion, the volume of data you send them. That works until your log volume doubles, and the invoice doubles with it. The best log management tools let you control what gets indexed and kept, so growth stops being a budget problem. In this blog, you will see: By the end you will know which fits your volume. Log management is the full lifecycle of your log data, from the moment it is collected to the moment it is deleted.

Labels are a powerful way to organize telemetry and define policies across Grafana Cloud, helping to streamline alerting, attribution, access control, and more. But traditionally, custom labels in Synthetic Monitoring have worked a little differently: they only lived on a single sm_check_info metric, and Grafana Cloud prefixed each one with label_.

model-right-sizer-schema is a Claude Code skill that designs the typed contract between one agent and the controller that dispatches it. Point it at an agent plus its controller and it returns a JSON prescription with typed in/out fields, an exclusion list that keeps raw logs out of the reply, a before/after size delta, then writes the contract into the agent's own file. It picks from nine portable output-shape families, or your repo's own.

Australia’s home-grown global automated infrastructure platform is part of a cohort of companies with Australian operations that will provide regional businesses and institutions access to NVIDIA accelerated computing and NVIDIA Nemotron open models. It’s a point of pride for all of us at Megaport that we’ve built a global automated infrastructure platform while maintaining our deep Australian roots.