IT professionals show password sharing the red card
SolarWinds research reveals the biggest own goals, red cards and match-winning moments shaping life in IT.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Broadcom Unveils AAI v26, Bringing Financial Accountability and AI-Driven Insights to Workload Automation
New release turns automation into a measurable business service with precise cost attribution, a conversational data interface, and AI-hardened security.
Why Mocks Fail at Scale #softwareengineering #devops #softwaretesting #api #aicoding
Mocking for testing starts off easy, but once you scale to multiple teams and AI agents, handcrafted mocks become a serious form of technical liability. Instead of treating mocking as an individual software engineering task, shift your mindset to treat it as a platform engineering task focused on automation and continuously refreshed modern data. Watch to see how adopting technologies like traffic replay to simulate realistic backend sandboxes can transform your modern testing workflow!
How backend functions extend Cribl Apps: Scheduling, local testing, and logs
See how backend functions extend Cribl Apps with live data retrieval, scheduled jobs, local testing, deployment validation, and logging. In this walkthrough, Giovanni Mola shows developers how to connect app data sources such as Jira and news feeds, manage schedules, preview functions locally, verify a live deployment, and inspect emitted logs in Cribl Search.
24/7 On-Call Coverage With a Small Team
Running 24/7 on-call coverage with a small team is first of all an arithmetic problem, and most teams avoid doing the arithmetic because the answer is uncomfortable. There are 168 hours in a week. Your engineers work roughly 40 of them. Somebody has to be reachable for the other 128, and if you have four engineers, that somebody is each of them, one week in four, thirteen weeks a year.
Cron Job Monitoring: Catch Silent Failures
Cron job monitoring is the part of observability most teams skip until a backup turns out to have stopped running three weeks ago. A web server that falls over generates errors, trips a threshold and pages someone inside a minute. A nightly job that quietly stops running generates nothing at all. There is no error rate to alert on, no latency spike, no failed health check. There is only an absence, and absence is invisible to almost every monitoring setup by default.
Google Calendar On-Call Rotation Template
Most teams building an on-call rotation template in Google Calendar get the first two steps right and the third one wrong. Creating a shared calendar is easy. Inviting the team is easy. Expressing "four people, one week each, forever, handing off Monday morning" as a set of recurring events is where it falls apart, usually into a mess of one off entries that someone has to rebuild by hand every quarter.
SSL Certificate Expiry Alerts in Slack
Certificate expiry is the most predictable outage in all of infrastructure. The date is printed inside the certificate. You can read it ninety days ahead. Nothing about it is a surprise, and yet SSL certificate expiry alerts remain one of the most common gaps in otherwise mature monitoring setups, and expired certificates keep taking down production systems at companies with serious engineering teams.
IT Pro Day 2026 | Every Day is Game Day
IT Pro Day isn’t just a day. It’s GAME DAY. The lights are on, the gear is ready, and IT Pros everywhere are locked in. At SolarWinds we celebrate the people who keep technology running, problems solved, and businesses moving. Because when the network goes down, the pressure is on. When systems need saving, IT Pros show up. Happy IT Pro Day from SolarWinds!
How Traceroute Works and How to Read Its Output During an Outage
Users report that an internal application has gone slow, the server dashboards look normal, and the network group says nothing changed on their side. So where between the user and the application does the time actually go? Much of that answer comes from traceroute. The command lists every router a packet crosses on the way to its destination, with a timing figure set against each one. Arguments about ownership then come down to a single device on a single route.