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

synapse_http_server_response_time_seconds_bucket has too high cardinality #11082

Open
matrixbot opened this issue Dec 19, 2023 · 0 comments
Open

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 19, 2023

This issue has been migrated from #11082.


Description

This issue was discovered while looking at other problematic time series due to #11081. There's a similar cardinality issue here, caused by the multiplying factor between the code, servlet and tag labels on the series.

Also, it's problematic to have time series that are part of the same bucket but don't all have the same set of labels. There's only a few series that have the tag label. That should probably be a separate histogram as the label difference will cause aggregation issues.

Steps to reproduce

  • Run lots of Synapse instances
  • Scrape them all with a single Prometheus instance
  • Prometheus gets sad

Version information

  • Homeserver: any
  • Version: any since this metric got introduced
  • Install method: unrelated
  • Platform: unrelated
@matrixbot matrixbot changed the title Dummy issue synapse_http_server_response_time_seconds_bucket has too high cardinality Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant