0 Replies Latest reply on Feb 13, 2020 4:19 PM by Anilkumar Nallamothu-Oracle

    Exalogic Resource Utilization ==> Consumption Tracking in OEM not showing the details for all the vServers

    Anilkumar Nallamothu-Oracle

      I have a Customer with Exalogic monitoring in OEM, who complains that they are not able to fetch vCPU Consumption stat in OEM13C (Version 13.2.0.0.0), They see collection stat only for 4 retails servers where as they have many retail servers discovered in OEM as part multiple Weblogic domains.  (From the Exalogic Elastic Cloud menu, choose Resource Utilization. and then select Consumption Tracking).

       

      Dragos helped me to find the issue, issue is that on the non-working target the associations are missing.

       

       

       

      =========================================================================================================

      target_2019_04_01_170324_ela02webabest01_workingSystem.log in target_2019_04_01_170324_ela02webabest01_workingSystem.log

      =========================================================================================================

       

      ----- Systems this target is associated with -------------------------------]

       

      ENTITY_GUID ENTITY_NAME ENTITY_TYPE

      -------------------------------- ------------------------------------------------------------ ----------------------------------------

      CFBD8F6BC4957C330D8E1B7DF7421354 /EXALOGIC_LUNDA/AK00109285 exa_rack <---------

      A7480FEE8138FA46F520C9ED21B4FB51 /EXALOGIC_LUNDA exalogic_system <----------

      BCF6CD99848450B57D0EE3C1F33C4801 Infrastructure Cloud oracle_vm_cloud

      78AFB37AE40F6834D0A4AECE114944F8 EXALOGIC_OVM_LUNDA oracle_vm_manager

      A6E24F3B296C23BA975C645DEF2C0A87 ela02Pool1 oracle_vm_server_pool

      91865220AC536E78BBF76DD40934AC06 MyCloud oracle_vm_zone

       

       

       

       

      and now the following is the data from non-working target,  the associations are missing.

       

       

      ============================================================================================================

      target_2019_04_01_164913_ela02webcvh02_NonWorkingSystem.log in target_2019_04_01_164913_ela02webcvh02_NonWorkingSystem.log

      =============================================================================================================

       

       

      [----- Systems this target is associated with -------------------------------]

       

      no rows selected

       

       

      But the Problem is, that we did not find the any difference in the discovery process for both working and non-working targets.

       

      We performed the rediscovery couple of times, but did not help.

       

      Please suggest for further troubleshooting of the issue.