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

telemetry doesnt work on v0.46.x #13982

Closed
baabeetaa opened this issue Nov 23, 2022 · 8 comments
Closed

telemetry doesnt work on v0.46.x #13982

baabeetaa opened this issue Nov 23, 2022 · 8 comments
Labels

Comments

@baabeetaa
Copy link

Summary of Bug

http://localhost:1317/metrics doesnt work.

It relates to #12448

I reverted the changes on baabeetaa@0ce906d and tested with EvmOS testnet v10.0.0-rc1 and it works

https://api-evmos-testnet-archive-ia.cosmosia.notional.ventures/metrics

Version

v0.46.x

Steps to Reproduce

  1. enable api and telemetry in config.toml and app.toml
  2. http://localhost:1317/metrics doesnt work
  3. http://localhost:26660/metrics shows Tendermint metrics only
@tac0turtle
Copy link
Member

is the fix to revert the mentioned pr?

@julienrbrt
Copy link
Member

julienrbrt commented Nov 23, 2022

I cannot reproduce this issue using simd, from main or release/v0.46.x.
Is the whole endpoint not working for you? Metrics shows for me 🤔.

@robert-zaremba
Copy link
Collaborator

It also works for me. Did you enable telemetry in the config?

@baabeetaa
Copy link
Author

Thanks @julienrbrt and @robert-zaremba for the info that it works with release/v0.46.x.
Yes, i enabled api and telemetry. Both me and @facs95 got the same result.
Evmos v10.0.0-rc1 uses v0.46.4 (https://github.com/evmos/evmos/blob/v10.0.0-rc1/go.mod#L9)
So maybe its fixed in v0.46.5 or v0.46.6?

@baabeetaa
Copy link
Author

Update:i tested with simd version 0.46.4 and release/v0.46.x, both work. I'll check evmos.

@baabeetaa
Copy link
Author

Update2: i tested cosmoshub v8.0.0-rc which uses 0.46.4 (same to evmos), and it works

@facs95
Copy link

facs95 commented Nov 25, 2022

This is an issue on the Evmos side - @fedekunze found the root cause of this. We are currently using on Evmos a "fork" of the SDK server in which we have a custom startStandAlone and standInProcess in which we didnt use to register Telemetry. By adding it into the Start we were fine as thats the only function we use from the SDK.

@baabeetaa
Copy link
Author

great, It works now. I'll close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@robert-zaremba @baabeetaa @tac0turtle @facs95 @julienrbrt and others