GraphOS reporting

The Apollo Router can report operation usage metrics to GraphOS that you can then visualize in GraphOS Studio. These metrics also enable powerful GraphOS features like schema checks.

Enabling usage reporting

You enable usage reporting in the Apollo Router by setting the following environment variables:

1
export APOLLO_KEY=<YOUR_GRAPH_API_KEY>
2
export APOLLO_GRAPH_REF=<YOUR_GRAPH_ID>@<VARIANT_NAME>

For more information, see Sending operation metrics to GraphOS.

Reporting field-level traces

In their responses to your router, your subgraphs can include field-level traces that indicate how long the subgraph took to resolve each field in an operation. By analyzing this data in GraphOS Studio, you can identify and optimize your slower fields:

Your subgraph libraries must support federated tracing (also known as FTV1 tracing) to provide this data.

• To confirm support, check the FEDERATED TRACING entry for your library on this page.
• Consult your library's documentation to learn how to enable federated tracing.
  • If you use Apollo Server with @apollo/subgraph, federated tracing support is enabled automatically.

Trace sampling rate

By default, the Apollo Router requests subgraph trace data for 1% of operations. In most cases, this provides a sufficient sample size while minimizing latency for most operations (traces can affect latency because they increase the size of subgraph response payloads).

You can customize your router's trace sampling rate by setting the following options in your YAML config file:

1
telemetry:
2
  apollo:
3
    # In this example, the router will request traces for 50% of requests.
4
    # This value can't exceed the value of tracing.common.sampler.
5
    field_level_instrumentation_sampler: 0.5
6

7
  exporters:
8
    tracing:
9
      common:
10
        # FTV1 uses the same trace sampling as other tracing options,
11
        # so this value is also required.
12
        sampler: 0.5

Disabling field-level traces

To completely disable requesting and reporting subgraph trace data, set field_level_instrumentation_sampler to always_off:

1
telemetry:
2
  apollo:
3
    field_level_instrumentation_sampler: always_off

Advanced configuration

send_headers

Provide this field to configure which request header names and values are included in trace data that's sent to GraphOS. By default, no header information is sent to GraphOS as a security measure.

1
telemetry:
2
  apollo:
3
    field_level_instrumentation_sampler: 0.01 # (default)
4
    send_headers:
5
      only: # Include only headers with these names
6
        - referer

Supported values:

1
send_headers: none

1
send_headers: all

send_variable_values

Provide this field to configure which GraphQL variable values are included in trace data that's sent to GraphOS. By default, no variable information is sent to GraphOS as a security measure.

1
telemetry:
2
  apollo:
3
    field_level_instrumentation_sampler: 0.01 # (default)
4
    send_variable_values:
5
      except: # Send all variables EXCEPT ones with these names
6
        - first

Supported values:

1
send_variable_values: none

1
send_variable_values: all

1
telemetry:
2
  apollo:
3
    # The percentage of requests will include HTTP request and response headers in traces sent to Apollo Studio.
4
    # This is expensive and should be left at a low value.
5
    # This cannot be higher than tracing->common->sampler
6
    field_level_instrumentation_sampler: 0.01 # (default)
7

8
    # Include HTTP request and response headers in traces sent to Apollo Studio
9
    send_headers: # other possible values are all, only (with an array), except (with an array), none (by default)
10
      except: # Send all headers except referer
11
        - referer
12

13
    # Include variable values in Apollo in traces sent to Apollo Studio
14
    send_variable_values: # other possible values are all, only (with an array), except (with an array), none (by default)
15
      except: # Send all variable values except for variable named first
16
        - first
17
  exporters:
18
    tracing:
19
      common:
20
        sampler: 0.5 # The percentage of requests that will generate traces (a rate or `always_on` or `always_off`)

errors

You can configure whether the Apollo Router reports GraphQL error information to GraphOS, and whether the details of those errors are redacted. You can customize this behavior globally and override that global behavior on a per-subgraph basis.

By default, your router does report error information, and it does redact the details of those errors.

• To prevent your router from reporting error information at all, you can set the send option to false.
• To include all error details in your router's reports to GraphOS, you can set the redact option to false.

Your subgraph libraries must support federated tracing (also known as FTV1 tracing) to provide errors to GraphOS. If you use Apollo Server with @apollo/subgraph, federated tracing support is enabled automatically.

To confirm support:

• Check the FEDERATED TRACING entry for your library on the supported subgraphs page.
• If federated tracing isn't enabled automatically for your library, consult its documentation to learn how to enable it.
• Note that federated tracing can also be sampled (see above) so error messages might not be available for all your operations if you have sampled to a lower level.

See the example below:

1
telemetry:
2
  apollo:
3
    errors:
4
      subgraph:
5
        all:
6
          # By default, subgraphs should report errors to GraphOS
7
          send: true # (default: true)
8
          redact: false # (default: true)
9
        subgraphs:
10
          account: # Override the default behavior for the "account" subgraph
11
            send: false