Skip to content

DOCS (question): How to interact with your testnet after deploying it #31

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

Open
brenzi opened this issue Apr 23, 2020 · 2 comments
Open
Assignees
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@brenzi
Copy link

brenzi commented Apr 23, 2020

Your tutorial stops when it gets interesting.

I just deployed a testnet with 2 validator nodes. All that I can guess from the log output is the IP of my two nodes.

  • how can I ssh to the box with the provided ssh credentials in the config? what username? It seems to be ssh -i <path to id_rsa> [email protected].
  • do the nodes send telemetry to the standard sink?

The following commands may be handy after ssh login on one of the nodes:

journalctl -f -u substrate

@DrTexx DrTexx added documentation Improvements or additions to documentation question Further information is requested labels Apr 28, 2020
@DrTexx
Copy link
Contributor

DrTexx commented Apr 28, 2020

@brenzi Those are really good points, thank you :)

Once we're next working on docs I'll try addressing these items.

@DrTexx DrTexx self-assigned this Apr 28, 2020
@rozifus
Copy link
Contributor

rozifus commented May 4, 2020

Thanks @brenzi

Added a ticket for updating docs to include ssh login, username, and journalctl

Added a ticket for telemetry documentation
*Currently we're only sending telemetry to the local telemetry exporter, however the user can add the standard sink via the node[x].binaryOptions.substrateOptions configuration object.

We can potentially readd the standard sink as a default alongside the internal telemetry exporter, I've created a ticket to investigate this although it may make sense to hold off until the inventory rework is done as this will make it easier for users to disable the standard sink if they choose to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants