Linux systems do not report total physical memory on agent connect

[alanwest]

On agent connect the following utilization hash (example below) is included in the connect payload. On linux systems total_ram_mib is always null. This is because the code that pulls this information only works on Windows.

See:

• https://github.com/newrelic/newrelic-dotnet-agent/blob/main/src/Agent/NewRelic/Agent/Core/Utilities/SystemInfo.cs#L29-L46
• https://github.com/newrelic/newrelic-dotnet-agent/blob/main/src/Agent/NewRelic/Agent/Core/Utilities/SystemInfo.cs#L123-L124

I have not reviewed this discussion very closely, yet, though it appears there is an open discussion around an API to retrieve this data: dotnet/runtime#22948. To my knowledge, there is nothing on System.Diagnostics.Process that gets us physical memory, though this should be confirmed.

However, even if there was an .NET API to retrieve this information, containerized environments may cause us additional problems.

Example utilization hash:

"utilization": {
    "metadata_version": 5,
    "logical_processors": 1,
    "total_ram_mib": null,
    "hostname": "...",
    "full_hostname": "...",
    "ip_address": [
        "..."
    ],
    "boot_id": "...",
    "vendors": {
        "azure": {
            "location": "...",
            "name": "...",
            "vmId": "...",
            "vmSize": "Standard_D1_v2"
        },
        "docker": {
            "id": "..."
        },
        "kubernetes": {
            "kubernetes_service_host": "..."
        }
    }
},

[github-actions]

This has been marked stale after 30 days with no activity. It will be closed in 5 days if there is no activity.