As platform engineering teams increasingly take on enterprise performance management tasks in production, there have been missed opportunities to give developers insights into their applications, experts say. <\/p>\n
Observability is an area where platform engineers and SREs have stepped in on behalf of some application developers, who aren't as steeped in the complexities of distributed cloud infrastructure systems such as Kubernetes. Analysts have also seen an increase in observability teams, specifically, within the platform engineering discipline that connect developers' application performance insights with underlying infrastructure data. <\/p>\n
\"[There's] a move toward centralizing observability teams and centers of excellence,\" said Nancy Gohring, an analyst at IDC. \"One driver for doing that is to try to control costs -- and one way those teams are trying to control costs is setting up data [storage] quotas for teams.\" <\/p>\n
Such teams don't replace the need for developers to instrument their own application code but have helped ease the burden of managing the ongoing operational costs associated with collecting observability data, Gohring said. <\/p>\n
There are some aspects of infrastructure monitoring, too, that developers don't need to concern themselves with, said Gregg Siegfried, an analyst at Gartner. Still, there remains a divide between the interests of platform teams in production observability and the interests of application developers, Siegfried said. <\/p>\n
\"I see an emergence of tools trying to give developers closer access to that data, to give them more insight, maybe allow them to put better instrumentation into the software,\" he said. \"But none of them have really set the world on fire yet.\" <\/p>\n
It's a commonly understood best practice in observability that developers instrument their own code before it's deployed to production, the better to manage its performance in the \"you build it, you run it\" mode of DevOps. <\/p>\n
\"I'm part of the OpenTelemetry End User Working Group, and recently we had somebody come in and talk to our user community about how they work in a company that really fosters an observability culture,\" said Adriana Villela, developer advocate at ServiceNow's Lightstep, an observability vendor, in a presentation at the recent Monitorama conference. \"The wonderful thing about it is that there is a directive from the executive saying, 'Thou shalt do observability and also developers are the ones instrumenting their own code,' which means that if you've got some disgruntled development team saying, 'I don't have time to instrument my code,' tough [s---].\" <\/p>\n
But some newer entrants to the market and their early customers question whether the developer experience (devx) with observability needs to be quite so tough. <\/p>\n
\"Developers being able to add custom metrics to their code or spans or use observability tools is really critical to help developers take ownership of what they run in production,\" said Joseph Ruscio, a general partner at Heavybit, an early-stage investor in cloud infrastructure startups, in a Monitorama presentation. <\/p>\n
However, to a new engineer, the overwhelming number of tools available for observability is \"inscrutable and not at all welcoming to someone new to the craft,\" Ruscio said. <\/p>\n
A production engineering team at a market research company is trying to make this task less onerous for developers using a new Kubernetes-based APM tool from Groundcover. Groundcover uses eBPF to automatically gather data from Kubernetes clusters and associate it with specific applications, which could eventually replace the language-specific SDKs developers used to instrument applications using incumbent vendor Datadog. <\/p>\n
\"For what we are calling custom metrics that monitor a specific application's behavior, these will continue to be the responsibility of the developers,\" said Eli Yaacov, a production engineer at SimilarWeb, based in New York. \"But we, the production engineers, can provide the developers the [rest of] the ecosystem. For example, if they are running Kubernetes, they don't need to worry about [instrumenting for] the default CPU or memory. Groundcover collects all this data in Kubernetes without requiring the developers to integrate with anything into their services.\" <\/p>\n
Other emerging vendors also offer automated instrumentation features in debugging tools to instrument developers' apps without requiring code changes. These include Lightrun and Rookout. <\/p>\n
Amid this year's general hype about generative AI, observability vendors have been quick to roll out natural language interfaces for their tools, mostly to add a user-friendly veneer over their relatively complex, often proprietary, data query languages. Such vendors include Honeycomb, Splunk, and most recently, Dynatrace and Datadog. <\/p>\n
However, generative AI interfaces are not necessarily an obvious slam dunk to improve the developer experience of using observability tools, Siegfried said, as most developers are comfortable working in code. <\/p>\n
\"They have better things to do with their time than learn how to use an [application performance management] solution,\" he said. <\/p>\n
Long term, generative AI and artificial general intelligence may have a significant effect, Ruscio said. But in the short term, he said he is skeptical that large language models such as ChatGPT will make a major impact on observability, particularly the developer experience. <\/p>\n
Instead, unlike security and production-level systems monitoring, observability has yet to shift very far left in the development lifecycle -- and developers would be best served by changing that, Ruscio said during his presentation. New and emerging vendors, some of which are among Heavybit's portfolio companies, are working in this area, termed observability-driven development. <\/p>\n
\"There's this missing mode where, wouldn't it be nice if you had some input when you are actually writing code as to, what does this code look like in production?\" Ruscio said. \"It's cool that when I ship it, I'll get a graph. But why shouldn't I just know now, in my IDE, [how it will perform?]\" <\/p>\n
Beth Pariseau, senior news writer at TechTarget, is an award-winning veteran of IT journalism. She can be reached at[emailprotected]or on Twitter @PariseauTT. <\/p>\n
<\/p>\n
See the original post: <\/p>\n
IT pros mull observability tools, devx and generative AI - TechTarget<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" As platform engineering teams increasingly take on enterprise performance management tasks in production, there have been missed opportunities to give developers insights into their applications, experts say. Observability is an area where platform engineers and SREs have stepped in on behalf of some application developers, who aren't as steeped in the complexities of distributed cloud infrastructure systems such as Kubernetes. Analysts have also seen an increase in observability teams, specifically, within the platform engineering discipline that connect developers' application performance insights with underlying infrastructure data. Continue reading