As a strategist, I’m often asked if we should toss the history out and start with a new fresh database for the monitoring product or push through and try to retain the history. My answer is always, “If the data is not at risk or abused, keep it.” So, how important is our history?
When you plan your monitoring and management strategies for your tooling, who is applying a deep level of understanding to that exercise? This is the framework and tooling your teams live by. It connects your ITSM tools, to your observability tools, to your automation and management tools—all the things.
Of all the capabilities of SolarWinds Orion, the most under-the-radar feature in almost every environment in some form or fashion is the ability to monitor points of failure within the network. It is critical that Orion admins take care to mitigate the single points of failure inherent in their monitoring system.
The odds are increasing that if you work in IT, you, or someone close to you, has been talking about “observability” recently. And, simultaneously, the conversation likely includes some comparison or question about the difference between observability and monitoring. So, Let’s try to clear up some of this confusion.
“We are delighted to further strengthen our SolarWinds partner status in the EMEA region by working with QBS Software to provide our comprehensive portfolio of SolarWinds training and professional services for resale through their reseller channel, commented Bill Fitzpatrick, Chairman and CEO at Loop1.