An administrator has enabled monitoring for a new tenant environment. The administrator checks 24 hours after the new environment has been added and sees data for other tenants' environments but no…

If the SNMP Community String were misconfigured for the new tenant, authentication would fail and polling requests would be rejected, but other tenants working correctly indicates the manager-side community string configuration is valid.

The SNMP Destination IP Address specifies where traps are sent from managed devices, but since other tenants are successfully delivering data to the same monitoring system, this address is correctly reachable.

The SNMP Manager IP Address identifies the monitoring server that collects data - since other tenants' data is appearing in the same monitoring system, the manager is online and accessible.

SNMP Traps are unsolicited notifications sent from a managed device to the SNMP manager when specific events occur - if traps are not configured on the new tenant's devices, no monitoring data is pushed and the manager receives nothing from that environment. Since all other tenants' environments are reporting data correctly, the SNMP manager, community string, and destination IP are all functioning properly on the manager side. Configuring SNMP traps on the new tenant's devices to target the monitoring manager's IP would resolve the missing data.