Missing information on installing Telemetry about docs HOT 7 CLOSED

Well I was on CentOS @excalq. For firewalld it required for me to open ports 8080 and 9243. Once I did that, everything worked! Anywho, now that you guys know about this, I can close the issue or you guys can if you wish. Either way is fine by me.
🤷‍♂️

from docs.

Thanks for the issue, will follow up with the eng team to get an updated process for enabling telemetry.

cc @algojohnlee for viz

from docs.

👍

from docs.

Hi, thanks for writing. In the above, it appears you are opening up port 8080. This shouldn't affect telemetry at all, as telemetry is (optionally) writing out diagnostic logging to our logging destination. Most people do not filter egress traffic, so no further action is necessary, but if you are filtering egress, then you would have to open up port 9243.

Are you perhaps referring to the REST API? That would work after enabling ingress on port 8080.

from docs.

Hello @onetechnical. 😃
Well unfortunately, telemetry did not work until I opened port 8080 and then restarted the process. Once I did, everything worked. I had already opened port 9243, and nothing worked until I opened port 8080. So I guess you're documentation says you need to open port 8080 and port 9243. Please let me know, and thanks again for your time.

from docs.

I guess I'm not sure how you verified telemetry was working. Were you pointing to a custom telemetry destination and verifying data was getting written?

from docs.

There's definitely opportunity to improve documentation on algod telemetry.
I'm suspecting that the service restart is what enacted the configuration change.

Unlike the /metrics API endpoint, telemetry connections are outbound only, so requires no firewall changes in a default ufw setup.

from docs.