/

Overview

Learn about Graph Manager features and create your account


Apollo Graph Manager (formerly Apollo Engine) is a cloud service that helps you manage, validate, and secure your organization's data graph.

In addition to serving as a GraphQL schema registry, Graph Manager ingests operation metadata and execution trace data from your GraphQL server to help you understand your schema and query usage.

Feature summary

Graph Manager provides the following features to all Apollo users for free:

Advanced features are available to organizations with a subscription to an Apollo Team or Enterprise plan:

Learn more about pricing and billing

The Apollo Graph Manager Architecture

Managing graphs

A graph in Graph Manager represents the data graph for a single project or application. Every graph has its own associated GraphQL schema.

Creating a graph

To create a graph in the Graph Manager interface, first select the Graph Manager organization that the graph will belong to. Then click New Graph in the upper right and proceed through the creation flow.

Note that every graph in Graph Manager has a globally unique graph name. We recommend that you prefix your graph names with the name of your company or organization to avoid naming collisions.

Viewing graph information

After selecting an organization in Graph Manager, click on a particular graph to view its data and settings. All of a Graph Manager organization's members have access to the data and settings for every graph that belongs to that organization.

Transferring graph ownership

You can transfer a graph to a different Graph Manager organization you belong to by visiting the graph's Settings page and changing the graph owner.

Deleting a graph

Deleting a graph cannot be undone!

You can delete a graph from Graph Manager by visiting its Settings page and clicking Delete.

Distinguishing between application environments

Every graph in Graph Manager should correspond to a single application. However, a single application might run in multiple environments (such as test, staging, and production).

To distinguish between graph activity for different application environments, you can define variants for a graph. Each variant has its own schema that can (but doesn't have to) differ from the default variant.

When your server sends metrics to Graph Manager, it can associate an operation with a particular variant. Variants appear as separate items in your organization's graph list, allowing you to view analytics for each application environment in isolation.

Ingesting and fetching data

Graph Manager ingests and stores performance metrics data sent from your GraphQL server. Use one of the following methods to send data to Graph Manager:

API keys

Any system that communicates with Graph Manager (whether to send metrics or fetch them) must use an API key to do so. You can add and remove API keys from your graph from its Settings page in the Graph Manager UI.

You should use a different API key for each system that communicates with Graph Manager. This provides you with more granular control over how Graph Manager data is sent and accessed.

Edit on GitHub