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

[Bug] graph-node:v0.34.0 metrics bloat #5161

Closed
1 of 3 tasks
trader-payne opened this issue Jan 25, 2024 · 0 comments · Fixed by #5164
Closed
1 of 3 tasks

[Bug] graph-node:v0.34.0 metrics bloat #5161

trader-payne opened this issue Jan 25, 2024 · 0 comments · Fixed by #5164
Assignees
Labels
bug Something isn't working

Comments

@trader-payne
Copy link

Bug report

The /metrics endpoint of the graph-node is bloated massively after the 0.34.0 upgrade, coming mainly from deployment_eth_call_execution_time metrics.

Tests have been done syncing one subgraph from scratch, and polling /metrics after some time.

v0.33.0/:
 13K Jan 25 21:19 metrics-v0.33.0.json
 27K Jan 25 21:20 metrics-v0.33.0.take2.json
 32K Jan 25 22:14 metrics-v0.33.0.take3.json
 32K Jan 25 22:21 metrics-v0.33.0.take4.json

v0.34.0-rc.0/:
112K Jan 25 22:30 metrics-v0.34.0-rc.0.json
450K Jan 25 22:40 metrics-v0.34.0-rc.0.take2.json
913K Jan 25 22:53 metrics-v0.34.0-rc.0.take3.json

v0.34.0/:
 14K Jan 25 22:59 metrics-v0.34.0.json
125K Jan 25 23:03 metrics-v0.34.0.take2.json
237K Jan 25 23:07 metrics-v0.34.0.take3.json
474K Jan 25 23:13 metrics-v0.34.0.take4.json

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

  • Tick this box if this bug is caused by a regression found in the latest release.
  • Tick this box if this bug is specific to the hosted service.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants