jenkins node doesnt appear as offline

[ctNb]

Relevant telegraf.conf:

[[inputs.jenkins]]
  ## The Jenkins URL
  url = "https://some-url"
  username = "username"
  password = "password"
  ## Set response_timeout
  response_timeout = "10s"

System info:

Telegraf Version: 1.11.4
Jenkins Version: 2.89.4

Steps to reproduce:

1. Add Docker node to Jenkins
2. Shutdown the node
3. Execute telegraf to test the config telegraf --test --config=config.conf

Expected behavior:

The Jenkins plugin in telegraf should get the node as offline
jenkins_node,arch=Linux\ (amd64),disk_path=/home/jenkins,node_name=displayName,status=offline, ....

Actual behavior:

The Jenkins plugin shows the error:
Error in plugin: empty monitor data, please check your permission

Additional info:

The same user is used by the plugin and to get the the following response snippet of the API which is called by the plugin

      {
         "_class":"hudson.slaves.SlaveComputer",
         "actions":[
            {

            },
            {

            },
            {

            }
         ],
         "description":"",
         "displayName":"displayName",
         "executors":[
            {

            }
         ],
         "icon":"computer-x.png",
         "iconClassName":"icon-computer-x",
         "idle":true,
         "jnlpAgent":false,
         "launchSupported":true,
         "loadStatistics":{
            "_class":"hudson.model.Label$1"
         },
         "manualLaunchAllowed":true,
         "monitorData":{
            "hudson.node_monitors.SwapSpaceMonitor":null,
            "hudson.node_monitors.TemporarySpaceMonitor":null,
            "hudson.node_monitors.DiskSpaceMonitor":null,
            "hudson.node_monitors.ArchitectureMonitor":null,
            "hudson.node_monitors.ResponseTimeMonitor":{
               "_class":"hudson.node_monitors.ResponseTimeMonitor$Data",
               "timestamp":1571985314769,
               "average":5000
            },
            "hudson.node_monitors.ClockMonitor":null
         },
         "numExecutors":1,
         "offline":true,
         "offlineCause":{
            "_class":"hudson.node_monitors.ResponseTimeMonitor$Data"
         },
         "offlineCauseReason":"5 mal keine Antwort",
         "oneOffExecutors":[

         ],
         "temporarilyOffline":false
      }

The error from the plugin is thrown because is hudson.node_monitors.ArchitectureMonitor is null.