Remove experimental_when_header feature

[bnjjj]

If you used the experimental_when_header feature previously like this for example:

telemetry:
  exporters:
    logging:
      # If one of these headers matches we will log supergraph and subgraphs requests/responses
      experimental_when_header: # REMOVED
        - name: apollo-router-log-request
          value: my_client
          headers: true # default: false
          body: true # default: false

This feature no longer exists and can be replaced with another one included in custom telemetry. Here is how you would configure custom telemetry to achieve the same result:

telemetry:
  instrumentation:
    events:
      router:
        request: # Display router request log
          level: info
          condition:
            eq:
            - request_header: apollo-router-log-request
            - my_client
        response: # Display router response log
          level: info
          condition:
            eq:
            - request_header: apollo-router-log-request
            - my_client
      supergraph:
        request: # Display supergraph request log
          level: info
          condition:
            eq:
            - request_header: apollo-router-log-request
            - my_client
        response:
          level: info
          condition:
            eq:
            - request_header: apollo-router-log-request
            - my_client
      subgraph:
        request: # Display subgraph request log
          level: info
          condition:
            eq:
            - supergraph_request_header: apollo-router-log-request
            - my_client
        response: # Display subgraph response log
          level: info
          condition:
            eq:
            - supergraph_request_header: apollo-router-log-request
            - my_client

[svc-apollo-docs]

✅ Docs Preview Ready

Configuration

{
  "repoOverrides": {
    "apollographql/router@next": {
      "remote": {
        "owner": "apollographql",
        "repo": "router",
        "branch": "bnjjj/fix_786"
      }
    }
  }
}

Name	Link
Commit	fdbaa9b
Preview	https://www.apollographql.com/docs/deploy-preview/fddd42489b267968ec57
Build ID	fddd42489b267968ec57
File Changes	0 new, 1 changed, 0 removed * graphos/reference/migration/from-router-v1.mdx
Pages	1

---

1 pages published. Build will be available for 30 days.

[router-perf]

CI performance tests

• connectors-const - Connectors stress test that runs with a constant number of users
• const - Basic stress test that runs with a constant number of users
• demand-control-instrumented - A copy of the step test, but with demand control monitoring and metrics enabled
• demand-control-uninstrumented - A copy of the step test, but with demand control monitoring enabled
• enhanced-signature - Enhanced signature enabled
• events - Stress test for events with a lot of users and deduplication ENABLED
• events_big_cap_high_rate - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity
• events_big_cap_high_rate_callback - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity using callback mode
• events_callback - Stress test for events with a lot of users and deduplication ENABLED in callback mode
• events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• events_without_dedup_callback - Stress test for events with a lot of users and deduplication DISABLED using callback mode
• extended-reference-mode - Extended reference mode enabled
• large-request - Stress test with a 1 MB request payload
• no-tracing - Basic stress test, no tracing
• reload - Reload test over a long period of time at a constant rate of users
• step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• step-local-metrics - Field stats that are generated from the router rather than FTV1
• step-with-prometheus - A copy of the step test with the Prometheus metrics exporter enabled
• step - Basic stress test that steps up the number of users over time
• xlarge-request - Stress test with 10 MB request payload
• xxlarge-request - Stress test with 100 MB request payload

[abernix]

@bnjjj @garypen Does this get a place in some section of the migration guide?

[bnjjj]

@abernix Yes. Do we have an existing one somewhere ?

[abernix]

@bnjjj Yup! https://github.com/apollographql/router/blob/next/docs/source/reference/migration/from-router-v1.mdx

[garypen]

Needs an entry in the migration guide.