This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: http://XXXXX:9100/debug/pprof/

| username: Sarah

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]


What is the debug under this address path, and can this page be closed?

| username: Kongdom | Original post link

The returned data should be the internal data of the monitoring component, which seems to be unable to be turned off.


For specific usage, you can refer to this article

| username: Sarah | Original post link

Received, it has been determined as a minor vulnerability by the penetration test.
No impact for now.

| username: Kongdom | Original post link

If you want to block access, you should be able to set it up in the firewall. However, it might not be possible to restrict it within the internal network, as the open port list of the tiup cluster includes this port.

| username: dba远航 | Original post link

This should be the entry point for debugging when issues arise, it’s better to keep it.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.