You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, the dashboard is broken. The file dashboard/dashboard.js attempts to make a websocket connection to pythd at a hardcoded URL: ws://localhost:8910. This is a problem for multiple reasons:
• You might not want to view the dashboard on the same host on which you’re running pythd.
• Even if you are viewing the dashboard on the same host as pythd’s docker container, the container’s published port is unlikely to be 8910.
The dashboard, as-is, only works if the browser you’re viewing it on is on the same host as pythd and the published port of pythd’s container is 8910. Can your team fix this?
Second, the dashboard doesn’t seem very useful to a publisher. It shows a view of the current aggregated state of all symbols. It might be more useful to us if it was a view of what pythd was seeing from its clients and sending to the broader pyth network. Is that something that you could change?
Thanks,
The text was updated successfully, but these errors were encountered:
We are working on a new re-write of pythd which will expose metrics relating to the updates pythd receives from it's clients, as you suggest. This is with the aim of increasing the observability of pythd. If you have any suggestions about which metrics would be useful to you, we'd love to hear them. Thank-you 😄
We had a few questions about the pythd dashboard referenced in your documentation [here]
(https://urldefense.com/v3/__https:/docs.pyth.network/publish-data*running-the-dashboard__;Iw!!GSt_xZU7050wKg!qOrCVC6LYuM9QkJT5v0UNKyt_FzhxX27xu4cI4ccru8FsSs_jcyUmeVdd1nmza1ybJXCPL-5Ms6r6d3DVKvlSaw$).
First, the dashboard is broken. The file dashboard/dashboard.js attempts to make a websocket connection to pythd at a hardcoded URL: ws://localhost:8910. This is a problem for multiple reasons:
• You might not want to view the dashboard on the same host on which you’re running pythd.
• Even if you are viewing the dashboard on the same host as pythd’s docker container, the container’s published port is unlikely to be 8910.
The dashboard, as-is, only works if the browser you’re viewing it on is on the same host as pythd and the published port of pythd’s container is 8910. Can your team fix this?
Second, the dashboard doesn’t seem very useful to a publisher. It shows a view of the current aggregated state of all symbols. It might be more useful to us if it was a view of what pythd was seeing from its clients and sending to the broader pyth network. Is that something that you could change?
Thanks,
The text was updated successfully, but these errors were encountered: