tree 2e842f21b9b6c5180b31e29c0fcf9e62bf27febe
parent 29deb426b3adf1d73e6c5e74330280efbebc974e
author Ziting <9065044+ZitingShen@users.noreply.github.com> 1616758790 -0700
committer GitHub <noreply@github.com> 1616758790 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgXcgGCRBK7hj4Ov3rIwAAdHIIACrvxw2VqpGsk/Dkfl5kug5x
 +8u7TfiZ/+24jJ9UyZ8NUPA0dH91TVzzLHFvbPBhuwV4qDSI5+nYkRQrj6nBJy6k
 X5WaRl9/VusTcCOXGD9VPnze6YagxT7B7fxsGfsGanAh5C9WL4+KDTdfUANUMGEm
 IFHzs6YL+/9bz3RbMd+4AWwrifrAEFizzktUXmPRD9olQ6zB0JyAjnYpYqpiTVPg
 waZw52AQI5mCscdWJYsKfIG7to54UMOj3DXUy2qgfOls1/JjELDOwt/hFcIv6qj0
 SjgaEM6VrCbbrZZOE19+YxGGpSjHv822vbF60VdGl/H4NxQKSDR19ljkLKA4Q3Y=
 =cLSX
 -----END PGP SIGNATURE-----
 

Fix NPE when thread pool size is 0 and thread pool is null (#1481)

Problem: when thread pool size is 0 and thread pool is null, hostStatisticsMonitor will throw NullPointerException when calculating containerActiveThreads and containerThreadPoolSize metrics. This will subsequently lead to the physical memory metrics to be missing as well, which can trigger alerts, lead to undesirable autosizing, etc.

Solution: add a null check for the thread pool before calculating containerActiveThreads and containerThreadPoolSize metrics