Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update ghcr.io/apollographql/router docker tag to v1.54.0 #402

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 11, 2024

This PR contains the following updates:

Package Update Change
ghcr.io/apollographql/router minor v1.53.0 -> v1.54.0

Release Notes

apollographql/router (ghcr.io/apollographql/router)

v1.54.0

Compare Source

🚀 Features

Add configurability of span attributes in logs (Issue #​5540)

The router supports a new telemetry.exporters.logging.stdout.format.json.span_attributes option that enables you to choose a subset of all span attributes to display in your logs.

When span_attributes is specified, the router searches for the first attribute in its input list of span attributes from the root span to the current span and attaches it to the outermost JSON object for the log event. If you set the same attribute name for different spans at different levels, the router chooses the attributes of child spans before the attributes of parent spans.

For example, if you have spans that contains span_attr_1 attribute and you only want to display this span attribute:

telemetry:
  exporters:
     logging:
       stdout:
         enabled: true
         format: 
           json:
             display_span_list: false
             span_attributes:
               - span_attr_1

Example output with a list of spans:

{
  "timestamp": "2023-10-30T14:09:34.771388Z",
  "level": "INFO",
  "fields": {
    "event_attr_1": "event_attr_1",
    "event_attr_2": "event_attr_2"
  },
  "target": "event_target",
  "span_attr_1": "span_attr_1"
}

To learn more, go to span_attributes docs.
By @​bnjjj in https://github.com/apollographql/router/pull/5867

Add a histogram metric tracking evaluated query plans (PR #​5875)

The router supports the new apollo.router.query_planning.plan.evaluated_plans histogram metric to track the number of evaluated query plans.

You can use it to help set an optimal supergraph.query_planning.experimental_plans_limit option that limits the number of query plans evaluated for a query and reduces the time spent planning.

By @​Geal in https://github.com/apollographql/router/pull/5875

🐛 Fixes

Fix Datadog sampling (PR #​5788)

The router's Datadog exporter has been fixed so that traces are sampled as intended.

Previously, the Datadog exporter's context may not have been set correctly, causing traces to be undersampled.

By @​BrynCooke & @​bnjjj in https://github.com/apollographql/router/pull/5788

📃 Configuration

General availability of Apollo usage report generation (#​5807)

The router's Apollo usage report generation feature that was previously experimental is now generally available.

If you used its experimental configuration, you should migrate to the new configuration options:

  • telemetry.apollo.experimental_apollo_metrics_reference_mode is now telemetry.apollo.metrics_reference_mode
  • telemetry.apollo.experimental_apollo_signature_normalization_algorithm is now telemetry.apollo.signature_normalization_algorithm
  • experimental_apollo_metrics_generation_mode has been removed because the Rust implementation (the default since router v1.49.0) is generating reports identical to the previous router-bridge implementation

The experimental configuration options are now deprecated. They are functional but will log warnings.

By @​bonnici in https://github.com/apollographql/router/pull/5807

Helm: Enable easier Kubernetes debugging with heaptrack (Issue #​5789)

The router's Helm chart has been updated to help make debugging with heaptrack easier.

Previously, when debugging multiple Pods with heaptrack, all Pods wrote to the same file, so they'd overwrite each others' results. This issue has been fixed by adding a hostname to each output data file from heaptrack.

Also, the Helm chart now supports a restartPolicy that enables you to configure a Pod's restart policy. The default value of restartPolicy is Always (the same as the Kubernetes default).

By @​cyberhck in https://github.com/apollographql/router/pull/5850

📚 Documentation

Document OpenTelemetry information for operation limits (PR #​5884)

The router's docs for operation limits now describe using telemetry to set operation limits and logging values.

By @​andrewmcgivery in https://github.com/apollographql/router/pull/5884


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from alessbell as a code owner September 11, 2024 22:05
@renovate renovate bot enabled auto-merge September 11, 2024 22:05
@renovate renovate bot added this pull request to the merge queue Sep 11, 2024
Merged via the queue into main with commit 6e63b72 Sep 11, 2024
2 checks passed
@renovate renovate bot deleted the renovate/ghcr.io-apollographql-router-1.x branch September 11, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants