Hosts don't appear after migration between environments

[anton_konikov]

• Summary
• Problem
• Troubleshooting steps
• Resolution
• What's next

Summary

When using tools like Monaco to migrate configuration between Dynatrace environments, it’s important to remember that the process typically transfers all configuration objects unless explicitly filtered. This means that settings specific to one environment - such as rules that disable host monitoring for certain hosts - will also be migrated. As a result, after the migration, those same host‑monitoring exclusions will appear in the new environment, even if they are not desired there.

Problem

After migration or installation of a new OneAgent, some hosts might not appear in the Dynatrace UI.

Troubleshooting steps

If hosts are missing from your new tenant after a migration, you will need to collect logs from one of the problematic hosts to investigate.

Operating System	Default Log Location
Linux	/var/log/dynatrace/oneagent
Windows	%PROGRAMDATA%\dynatrace\oneagent\log

Next, review the ruxitagent_host_<PID>.0.log file to determine the agent's status and the reason for its disablement. Depending on what you find, you can:

• Refer to the troubleshooting steps: Host not appearing in Dynatrace after fresh OneAgent install.

• Or, look for specific connection errors. In this case, the logs might contain the following entries immediately after connecting to the server:
  

  2026-01-01 00:00:15.452 UTC [0003dc44] info    [native] Got initial setup response (server 0x00000001)
  2026-01-01 00:00:15.452 UTC [0003dc44] info    [native] ConfigFromServer: Updating active state to OFF (server 0x00000001)
  2026-01-01 00:00:15.453 UTC [0003dc44] info    [native] Disablement reason changed to: [HOST_MONITORING_DISABLED]
  2026-01-01 00:00:15.453 UTC [0003dc44] info    [native] ============================== Agent inactivated ============================== (no more data will be sent by this agent, except heartbeats and config requests.)​

Resolution

As the first step it would be required to get HOST ID from the log file:

2026-01-00 00:00:15.732 UTC [00175140] info    [native] OSI ID ...................... 0xABCDEF1234567890

and then navigate to Host monitoring settings page the Monitroing this host toggle may be turned off: https://<tenant_id>.apps.dynatrace.com/ui/apps/dynatrace.classic.hosts/ui/settings/HOST-ABCDEF1234567890/builtin:host.monitoring

However, if the host cannot be enabled by turning on the toggle or the host entity wasn't created, please use the Settings API to retrieve all objects for this schema ID - builtin:host.monitoring.

• Settings API - GET objects
  

  curl -X 'GET' \
    'https://<tenant>.live.dynatrace.com/api/v2/settings/objects?schemaIds=builtin%3Ahost.monitoring&fields=objectId%2Cvalue&adminAccess=false' \
    -H 'accept: application/json; charset=utf-8' \
    -H 'Authorization: Api-Token <API TOKEN>'​

• and then to enable monitoring - Settings API - PUT an object, send a request with the next body:
  

  [
    {
      "schemaId": "builtin:host.monitoring",
      "scope": "HOST-ABCDEF1234567890",
      "value": {
        "enabled": true
      }
    },
    {
      "schemaId": "builtin:host.monitoring",
      "scope": "HOST-ABCDEF1234567891",
      "value": {
        "enabled": true
      }
    }
  ]​

 

What's next

If the above steps didn't resolve the issue, open a chat and provide a link to the monitor, along with details of the troubleshooting steps you have already completed.