Grazed from SolarWinds
SolarWinds, a leading provider of powerful and affordable IT management software, today announced that it is introducing an inside out view into cloud environments to help DevOps professionals gain unmatched visibility across the internal aspects of cloud environments-metrics, traces, and logs, plus an external view of the user experience. The enhanced functionality within SolarWinds’ products Pingdom, AppOptics, Papertrail, and Loggly can be used individually to provide visibility into cloud-based infrastructure and application performance or used together as a DevOps toolkit to maintain 360-degree visibility into cloud monitoring.
"Today’s recognized ‘pillars of observability’ combine metrics, traces, and logs to enable DevOps teams to monitor system and application performance. But, these capabilities provide only limited insights into application performance because they ignore the user’s experience-a critical measure of application performance," said Christoph Pfister, executive vice president of products, SolarWinds. "Understanding if a system is slow or unavailable from an end user’s perspective is crucial in today’s digital world even if the metrics are good and there are no alerts. Bringing user experience, metrics, traces, and logs together with an easy-to-use, complementary toolkit provides DevOps teams with unmatched visibility into their environment, so they can seamlessly follow an alert or issue from one product into another to resolve issues quickly and get back to focusing on the more proactive elements of their job."
For example, if support gets a call that a web application is not letting users log in, a DevOps team can open the Pingdom (user experience) dashboard to see the login page has turned red and when the outage began. Jumping over to the metrics views in AppOptics (metrics), the DevOps team sees it’s not a problem with the website response time, therefore not a performance issue, but in the detail view they notice the HTTP status codes are red. Next, the DevOps team uses AppOptics (traces) to trace one of the failed requests and discovers the web application was trying to make a connection to a backend service, but there was an issue with the DNS entry. The DevOps team then jumps over to Papertrail (logs) or Loggly (logs) to see the log data. Here they can filter down to the application host and view when the outage started, discovering the service was stopped. With this insight, the DevOps team can quickly restart the service and get the web application up and running.