Operations | Monitoring | ITSM | DevOps | Cloud

An asset management policy states who owns each item, what records must exist, and what happens before equipment is bought, moved, or destroyed. Most IT teams do not need forty pages. They need rules that survive an audit and a register matching reality.

Some features start on a roadmap. Others start with a recurring customer request: Can LightMesh connect to Meraki? That request kept coming up. Now the answer is yes. LightMesh supports Meraki sites with multiple VLANs or a single LAN through the new cloud integration for Cisco Meraki. Appliance addressing from Dashboard syncs into LightMesh as subnets (with VLAN ID when Meraki provides one), and device or client LAN IPs only when they fall inside those CIDRs.

There is no doubt that LLMs have changed how we work as developers. You can go back just a year from today and I would have had a very different opinion. But, things have changed significantly. Complex work usually involves just prompting an agent for it. You still need taste and opinions to steer it the right way. With that in mind, it’s easy to se that the future of the IDE might be uncertain.

Five worktrees for five agents sounds like organization. In practice, it’s five contexts to keep straight, five places history could live, five spots for a WIP that gets left behind or diffed against the wrong branch. GitLens 19.2’s fix isn’t a second graph. It’s making the one graph you already trust point wherever the work actually is.

A funnel can tell you that 40% of users dropped off between checkout and payment. What it can’t tell you is what those users did instead, such as return to an earlier form field, leave the flow for a support page, encounter an error, or take another route entirely. Because actions and views between funnel steps don’t affect the conversion calculation, two very different experiences can produce the same funnel result.

One onboarding ticket can hold a full name, home address, device serial and passport scan. Article 32 of the General Data Protection Regulation requires you to ensure a level of security appropriate to the risk.

Less time coordinating, more flexibility to fit your schedule.

Security and operations teams are collecting more telemetry than ever, and AI is accelerating that curve. IDC projects the world will generate 393.9 zettabytes of data in 2028, up from 149 zettabytes in 2024, with AI and machine learning workloads driving much of that growth. That growth forces a hard trade-off. Ingest everything, and you pay for it. Filter aggressively, and you risk missing the signal that matters.

Today we’re taking our partnership with Chris Oliver (founder of Hatchbox and GoRails) one step further. With AppSignal, you can already store enriched telemetry about your applications, services, and infrastructure, along with your user context, in your AppSignal context store. You can use that context store for traditional observability reporting and workflows, or connect it to your agents over MCP or the CLI. AppSignal’s context store is what our Intelligence features are built on.