09-08-2020 04:15 AM
09-08-2020 10:50 AM
Currently that isn't something you can change, unless you modify the python code that is publishing it (not recommended). Why do you want to change it?
We specifically set it to localhost to make it easier to build server health monitoring dashboards that will work on any server.
09-08-2020 10:21 PM
Thanks for clarifying, Joshua. Supporting portable server dashboards makes sense.
I wanted to change it because the name "localhost" has a special meaning on a network related to loopbacks: (see 6.3.3 at https://tools.ietf.org/html/rfc6761 ). When I'm working from a client PC and I see a dashboard talk about "localhost CPU usage", I'd normally understand it to mean "my current PC's CPU usage" rather than "the server's CPU usage".
Since changing it is not supported, I'll make a note in my customer's documentation about the non-standard usage of "localhost".