# How Apollo Studio's GraphQL Client Awareness Helps Track Clients and Avoid Breaking Changes

DevFeed: [How Apollo Studio's GraphQL Client Awareness Helps Track Clients and Avoid Breaking Changes](<https://devfeed.tech/articles/who-s-using-my-graph-23358.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/how-apollo-studio-client-awareness-improved-our-lives>)

Author: Adam Zionts

Published: 2020-08-19T11:00:00Z

Content type: article

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [client](<https://devfeed.tech/topics/client.md>), [API](<https://devfeed.tech/topics/api.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [development](<https://devfeed.tech/tags/development.md>), [feature](<https://devfeed.tech/tags/feature.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [incident](<https://devfeed.tech/tags/incident.md>)

## AI overview

This article explains GraphQL client awareness in Apollo Studio: identifying which clients and client versions use particular graph fields, viewing operation metrics, assessing breaking-change costs, and supporting safer development workflows.

## Source excerpt

We're all used to celebrating big, sparkly successes, like major releases, new customer successes, and the end of a long saga of re-architecture. My favorite kind of success, however, often goes unnoticed: the success of avoiding failure. In our day-to-day lives as engineers, sadly, these events come to pass without much recognition: the sweet quietude of an incident avoided, rolling out a new feature with only a few code changes thanks to a sound architecture, automation set up behind the...