Operations | Monitoring | ITSM | DevOps | Cloud

Location Management in Skylar One

Location Management in Skylar One gives IT teams a centralized way to create, maintain, and organize location data, building the foundation for trusted geographic visibility across distributed environments. In this walkthrough, Brian Harding, Director of Product Management at ScienceLogic, demonstrates how to create and manage locations in Skylar One. See how teams can define locations, associate them with the right organizations, and use accurate latitude and longitude data to establish the geographic context needed for devices, services, and Geographic Maps.

Geographic Maps in Skylar One

Geographic Maps in Skylar One give IT teams a faster, more intuitive way to understand infrastructure and service health across distributed environments. In this walkthrough, Brian Harding, Director of Product Management at ScienceLogic, demonstrates how to create and configure a Geographic Map in Skylar One. See how to create locations, align devices and services, use filters to control what appears on a map, and visualize infrastructure health based on real-world locations.

Why AI Agent Architecture Needs a Runtime Context Layer

Every AI agent architecture diagram shows the same five layers: perception, memory, reasoning, action, and feedback. Each layer assumes the one before it worked correctly, and none of them can confirm that once the agent runs against live production data. Runtime context is the sixth layer most designs leave out, and it’s the one that decides whether any of the other five can be trusted.

Why AURA Scratchpad Is Rad: Bound the AI SRE Agent Context Window

A big tool result does not have to be a big context cost. AURA moves it to disk and hands the model a pointer plus the tools to navigate what is there. A large MCP tool result can consume or overflow an agent's context window, and on a third-party server you do not control how much comes back. Scratchpad breaks the link between how big a tool result is and how much context it costs: the full output goes to disk, and only the slice the model asks for ever enters the window. Errors always pass through inline, so the model can react to them.

Signal vs. Spend: Building Cost-Aware Observability at Slack - O11yCon 2026

It started with a single log line taking up a massive amount of volume: 500 million emissions per hour. Pulling that thread led Emma and Steven into Slack's broader logging pipeline: 311 billion logs per day at 4.4M/sec peak, with no volume limits, no per-service attribution, and no feedback to the teams generating the noise.

Suppressing OnPage Notifications During Maintenance

Learn how to suppress OnPage notifications during a scheduled maintenance window so your on-call team isn’t unnecessarily alerted while planned work is underway. OnPage’s Suppress Notifications option temporarily prevents notifications from being sent during a defined period. This is especially useful during scheduled maintenance, planned downtime, testing, or other known activities that could otherwise generate unnecessary alert noise.

Creating Message Templates in OnPage

Learn how to create and configure a message template in OnPage to make critical communication faster, more consistent, and easier for your team. OnPage message templates are predefined message formats that help teams standardize frequently used communications without having to compose every alert or message from scratch, and can be pulled up on both web message dispatcher and OnPage's phone app. In this step-by-step tutorial, we show you how to navigate to Settings then Template, create a new message template, and configure the information users will see when that template is selected.

How task containers give AI agents real infrastructure without idle cost

Infrastructure for AI agents usually forces a choice between two bad options. A sandbox is safe but blind, cut off from the data and services that would make the agent's output useful. Full access means paying to keep a container idle between runs, waiting on a prompt that might not arrive for hours. Task containers, which Upsun released on August 12, 2026, are built to avoid that choice. A task container is a single-purpose container defined in a project's.upsun/config.yaml file.

Turn every branch into a production-like environment, automatically

You push a branch. If your team is like most, that branch now waits: for the shared staging server to free up, for someone to remember to refresh the seed data, for whoever broke staging last to fix it. By the time you actually test your change, you're testing it in an environment that's drifted from production in ways nobody fully tracked. The alternative isn't a better staging server. It doesn't need one.

Pain Killer, Not a Vitamin: What Actually Triggers a DCIM Vendor Switch

Organizations replace their DCIM vendor when an unresolved pain point becomes urgent enough to act on — not because a competing platform has a longer feature list. Understanding what those pain points actually are, for each type of stakeholder in the data center ecosystem, is the clearest way to predict where DCIM displacement is happening now and where vendor stickiness will hold.