Link: Misunderstanding “Open Tracing” for the Enterprise

Enterprise systems management software is hard.

“OpenTracing doesn’t solve the interoperability problem, so what does the “open standard” attempting to solve? Well, for one thing, is that it allows those making gateways, proxies, and frameworks the ability to write instrumentation. That should, in theory, make it easier to get traces connected, but once again the requirement to change implementation details for each tool is a problem.”
Original source: Misunderstanding “Open Tracing” for the Enterprise

Link: Datadog log monitoring software branches out as DevOps spreads

‘Enterprises initially implemented DevOps within specialized groups that owned a specific application and chose their own IT management tools, said Nancy Gohring, analyst at 451 Research. “Then one day, the enterprise woke up and saw it had 50 different tools, and in some cases, multiple instances of the same tool, each managed by different people,” she said.’
Original source: Datadog log monitoring software branches out as DevOps spreads

Link: With Loggly, SolarWinds scoops up another log service

“With the acquisition of Loggly, SolarWinds obtains an asset that was slow in getting started but has hit a patch of growth recently. As of September, we believe the company was on track to finish 2017 with roughly $10m in billings, up from mid-single digits in 2016. Founded in 2009 with a mission of offering a SaaS-based, easy-to-use logging product with helpful visualizations built using advanced analytics, Loggly had raised $47m in venture capital, including a $11.5m series D round in June 2016.” They estimate ~3,000 paying customers.
Original source: With Loggly, SolarWinds scoops up another log service

Link: Microsoft gets serious about monitoring

“Microsoft’s vision is to deliver tools that can offer a holistic view of services to application architects looking to optimize their software; performance information and debugging capabilities for DevOps and ops pros; insight into KPIs for executives; and information about customer usage to product owners. Microsoft doesn’t yet have a cohesive offering for all of the above, but it has the pieces to enable it and has begun delivering on some integrations across products.”
Original source: Microsoft gets serious about monitoring

Good, simple explanation of Service Level Objectives (SLOs)

SLOs are objectives that your business aspires to meet and intends to take action to defend; just remember, your SLOs are not your SLAs (service level agreements)! You should pick SLOs that represent the most critical aspects of the user experience. If you meet an SLO, your users and your business should be happy. Conversely, if the system does not meet the SLO, that implies there are users who are being made unhappy!

Source: Building good SLOs – CRE life lessons

ScienceLogic momentum

The company targets very large users, with 60% of its customers being MSPs, followed by enterprises at about 30%, and the rest coming from government agencies. It doesn’t report the number of direct customers, but its website boasts 47,000 organizations as users, many of them employing ScienceLogic via service providers. Average annual contract value for direct customers is $125,000.

Source: ScienceLogic targets new use case aimed at frustrated CMDB users