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

v1.33.2 router.yaml OpenTelemetry metric error occurred: Metrics error: Warning: Maximum data points for metric stream exceeded. Entry added to overflow. #4187

Open
billnbell2 opened this issue Nov 13, 2023 · 3 comments
Labels
component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. raised by user

Comments

@billnbell2
Copy link

billnbell2 commented Nov 13, 2023

We are having an error that happens several time a minute.

OpenTelemetry metric error occurred: Metrics error: Warning: Maximum data points for metric stream exceeded. Entry added to overflow.

It does not indicate what is causing it?

Expected behavior
No error in logs for router.

Self-hosted on Kubernetes.

Should I change something in here?

telemetry:
  apollo:
    send_headers: all
    send_variable_values: all
    errors:
      subgraph:
        all:
          send: true
          redact: false
  metrics:
    prometheus:
      enabled: true
@billnbell2 billnbell2 changed the title Latest router.yaml OpenTelemetry metric error occurred: Metrics error: Warning: Maximum data points for metric stream exceeded. Entry added to overflow. v1.33.2 router.yaml OpenTelemetry metric error occurred: Metrics error: Warning: Maximum data points for metric stream exceeded. Entry added to overflow. Nov 13, 2023
@billnbell2
Copy link
Author

??

@abernix
Copy link
Member

abernix commented Nov 27, 2023

This is getting reported by the OpenTelemetry error handler, but this isn't something that we're familiar with. It'll have to be investigated a bit more (including looking at the source code) to get more information on what this even means.

Any other details you can provide about the environment could be really useful, but do you have any sort of minimal reproduction that you can put together for us?

@BrynCooke
Copy link
Contributor

This is caused by having too many permutations for a particular metric. There is a hard limit of 2000 permutations in otel.

We need to allow users to control which instruments are active and the attributes that are present on them. Part of #3226.

@bnjjj bnjjj added the component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. raised by user
Projects
None yet
Development

No branches or pull requests

4 participants