Operations | Monitoring | ITSM | DevOps | Cloud

IT environments are getting increasingly complex and can often straddle on-premises gear, private cloud, public and/or multi-cloud, and SaaS environments... oh, and it’s a moving target. Your legacy applications may have to reincarnate in one of these forms with minimal disruption. And when things go wrong, you need all the help and pointers you can get to identify the root source of the problem and what it’s impacting.

For-Each is a new feature added to the DX Unified Infrastructure Management’s (DX UIM) Monitoring Configuration Service (MCS) that uses the device attributes with one or multiple values. MCS will loop through each value and create a profile for each one. If that attribute does not exist for a device, no profile will be created. Similarly, if a new value is added or removed from a device, MCS will revaluate and add or remove profiles.

2022, the world is the technological paradise you always dreamed of. Space mining, smart cities, 3D printers to make your own Darth Vader mask… Just a little problem, society is based on digitization and communications and you have no idea about the visibility of distributed networks. Something of vital importance considering the rise of cybercrime. Well, don’t worry, we’ll help you.

Unplanned downtime carries a hefty price tag for enterprises. In 2020, critical server outages cost enterprises on average at least $10,000 per hour, with 95% of respondents stating that the cost was $200,000 per hour or more. 40% said that the average cost was closer to $1 million per hour, and 17% lost $5 million or more for every hour offline. Those are some sobering statistics that demonstrate the importance of being prepared for the worst. But you’re thinking, “We back up everything!

Load balancing is an indispensable technique for improving a website’s performance. I’ll explain why. With Firefox’s Web Developer Tools open, I visited a popular retailer’s website to see how many HTTP requests my browser made when loading the site. In this case, I counted 119 requests needed to render the landing page.