At Honeycomb, we’ve often discussed the value of making software deployments early and often, and being able to understand your code as it runs in production. However, these principles aren’t specific to only your customer-facing software. Configuration-as-code, such as Terraform, is in fact code that needs to go through a release process as well. Lacking formal process around Terraform deployment means a de-facto process that generates reliability risk.
Transformation of IT Ops When I think of the term IT Ops I immediately think of Enterprise IT and the traditional attributes that make up this function – many of which are in the middle of an industry-wide disruption – and its associated impact. At LinkedIn, when we first looked at business process support, shadow IT and non-accounted-for IT spend, about 10 years ago, it was a bit of a revelation to me how the landscape had already changed by then.
Gartner’s Hype Cycle for ITSM report highlights tools or technologies that improve IT operations. It’s a comprehensive, in-depth document, allowing support teams to gain insight into the latest innovations, industry trends and recommendations. The OnPage team is pleased to be included in the latest Hype Cycle for ITSM report, listing OnPage’s solution as a trusted, reliable source for IT service alerting (ITSA).
We are thrilled to announce that we now offer Single Sign-On (SSO) support for ALL customers on the CHAOSSEARCH platform. You can now integrate your existing identity provider with CHAOSSEACH and have your users access the platform without needing to manage a separate set of credentials.
Censorship appears to be increasingly tough not only in countries, which we traditionally view as authoritarian (Iran, North Korea, China, Russia, etc.) but in Western ones as well. It is not uncommon anymore for users from around the globe to find themselves unable to access their favorite resources.
Debugging. It’s one of the most time-consuming ways of finding a bug. As a senior .NET developer, I can tell you that it’s best to avoid the necessity for debugging altogether by writing clean code that’s covered by automated tests. If you’re a senior developer yourself, you probably already know this. And if you’re a junior developer, now you know it too! However, the world isn’t binary.
We’ve changed Transaction steps and Multi-step API Monitoring steps to Transaction credits and Multi-step API Monitoring credits. In short: Steps are used to group your actions in your monitor definitions, and credits are used to buy Transaction or Multi-Step API monitors. Let’s explain that in more detail.
In the world of Software Engineering, observability seems to be the talk of the town. We discuss it at conferences, read about it in blogs or articles, and see it promised to us by vendor after vendor. But what is observability? What issues have recently evolved to make it such an integral concept? What strategies are engineers employing to ensure observability? And most importantly of all, why are engineers looking to achieve it?
If you’re not familiar with APIs, let’s run through a quick primer. API stands for application programming interface and refers to a set of tools and protocols that makes it possible to easily and efficiently access a software or hardware system from the outside.
Tools like Rollbar have changed the way development teams are recording and managing their exceptions. What used to be a very personal developer-by-developer activity can now be a team-wide tool for greater transparency, and increased application quality. But many still treat exception monitoring as a developer activity, and they are not leveraging its benefits across all environments, from development to stage and integration, to systems testing and production.
