Skip to main content

SolarWinds Launches "SysMan Hero!" Online Game for Sysadmins

SolarWinds calls on all IT professionals to save the Web with the launch of its new "SysMan Hero!" game.

A Web-based gaming experience that can be played in any browser, without downloading a plug-in, and on any webpage, "SysMan Hero!" gives players the opportunity to fight, defend and save the Web from an attack of virulent bugs.

The game transforms any webpage into an epic battle where Web-eating bugs swarm the screen in increasing numbers and attack the selected site. Players start by selecting their own SysMan hero persona and a spaceship. Bugs invaders will then execute an all-out attack on whatever Web page the player happens to be browsing at the time, "eating" content along the way and leaving a minefield of torn-up code in its wake. The SysMan Hero must defend the Web using overhead 2D shooters with rotation, thrusters, shields and a blaster to zap space bugs before it's too late.

SysMan Hero! can be played for free by going to http://bit.ly/XWMBL0 and bookmarking the launch button, or installing the "SysMan Activator" button in the browser's toolbar. From there, players can compete with themselves or one another by following top scores on the Leader Board.

Sysadmins choose from one of three "SysMan Hero" personas, each of which represents the heroic qualities of a systems administrator, such as tactical prowess and the power to troubleshoot and respond. But in the end, they have only one mission: to restore order and productivity to the Internet.

The personas are:

- Snap, whose superpowers are logic and effectiveness

- Simplo, who always seeks the simplest solutions to every problem

- Reeeboot, who prides himself in making life easier for the user

In addition, some bugs will follow the player and attempt to attack him, decreasing his lifespan. If the player successfully destroys all the bugs, a new round will begin. When all five rounds have been successfully played, the player has won.

"Systems administrators work behind the scenes to provide a vital service to their companies - they are the unsung heroes. More than that, they have to deal with an ever-increasing volume and complexity of work, often with diminishing resources," said Kevin Thompson, SolarWinds' President and CEO. "We wanted to give IT pros a way to blow off some steam through a free, engaging and easy-to-play game, featuring everyday IT challenges that they can relate to instantly."

Play SysMan Hero! for Free

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

SolarWinds Launches "SysMan Hero!" Online Game for Sysadmins

SolarWinds calls on all IT professionals to save the Web with the launch of its new "SysMan Hero!" game.

A Web-based gaming experience that can be played in any browser, without downloading a plug-in, and on any webpage, "SysMan Hero!" gives players the opportunity to fight, defend and save the Web from an attack of virulent bugs.

The game transforms any webpage into an epic battle where Web-eating bugs swarm the screen in increasing numbers and attack the selected site. Players start by selecting their own SysMan hero persona and a spaceship. Bugs invaders will then execute an all-out attack on whatever Web page the player happens to be browsing at the time, "eating" content along the way and leaving a minefield of torn-up code in its wake. The SysMan Hero must defend the Web using overhead 2D shooters with rotation, thrusters, shields and a blaster to zap space bugs before it's too late.

SysMan Hero! can be played for free by going to http://bit.ly/XWMBL0 and bookmarking the launch button, or installing the "SysMan Activator" button in the browser's toolbar. From there, players can compete with themselves or one another by following top scores on the Leader Board.

Sysadmins choose from one of three "SysMan Hero" personas, each of which represents the heroic qualities of a systems administrator, such as tactical prowess and the power to troubleshoot and respond. But in the end, they have only one mission: to restore order and productivity to the Internet.

The personas are:

- Snap, whose superpowers are logic and effectiveness

- Simplo, who always seeks the simplest solutions to every problem

- Reeeboot, who prides himself in making life easier for the user

In addition, some bugs will follow the player and attempt to attack him, decreasing his lifespan. If the player successfully destroys all the bugs, a new round will begin. When all five rounds have been successfully played, the player has won.

"Systems administrators work behind the scenes to provide a vital service to their companies - they are the unsung heroes. More than that, they have to deal with an ever-increasing volume and complexity of work, often with diminishing resources," said Kevin Thompson, SolarWinds' President and CEO. "We wanted to give IT pros a way to blow off some steam through a free, engaging and easy-to-play game, featuring everyday IT challenges that they can relate to instantly."

Play SysMan Hero! for Free

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...