The issue is attributed to two primary factors:
vmw_nsxt_firewall_ruleid metadata required by VCD.This issue is targeted to be fixed in a future release. Subscribe to this article to be updated on the fix status.
To mitigate the behavior:
vmw_nsxt_firewall_ruleid field is correctly populated.curl -k -X POST https://<Aria_Logs_FQDN_or_IP>:9543/api/v2/sessions -d '{"username":"<username>", "password":"<password>", "provider":"Local"}'Note: These steps serve as prerequisites and validation checks while the permanent fix is being incorporated into a future VCD release.
If "No Logs Found" persists after the Content Pack upgrade, verify that logging is explicitly enabled on the specific Distributed Firewall rules in VCD and that the Host Transport Nodes (ESXi) are configured to forward syslog data to Aria Operations for Logs.