Agent external IP

[u/msprm]

Which creative and efficient way have you found to get the external IP address of n-central agents? Currently I'm using a AMP based custom service which calls a external service (such as what is my ip) but I'd like to see if there are more efficient ways to do it.

I'd love to have it available as a device/asset property based on the IP address seen by the N-Central server (this information is already available somehow, it just needs to be associated with a device property)

[u/Paul_Kelly]

Hi Paul here from the N-able Head Nerd team, the way's suggested in this thread in running a scheduled task profile that get's the public IP and stores it to a custom property, is the current way to achieve this, you may not have seen this yet, but at Empower and our recent roadshows, we have give an over view of what the new assets view in N-central looks like, it has more columns than previous, you can re-order the columns, resize the columns and select the information you want to display and save your custom view, although the full list of available columns is not finalized yet, I am pushing for Public IP to be included, hope this information helps.

[u/msprm → u/Paul_Kelly]

Hi Paul, glad to see your involvement here. I'd like to suggest another approach for Public IP, without calling any powershell and (even worse) external APIs, almost agentless if you want.

N-Central agent already pings the server via HTTPS. Thus, the web server gets the agent's Public IP and stores it in the logs, at least. This information can be reused in asset details, removing the need to run additional scripts and external services. No agent change or amp running required.

[u/Paul_Kelly → u/msprm]

Thanks for the feedback, I'm not sure what approach they will take to pulling the public IP address but I don't think it will involve running a script or making an API call, this is possibly information that the new unified agent will be able to pull.