3 Replies Latest reply on Sep 27, 2019 6:54 AM by Dima Seliverstov

    Capacity Optimization Agent Configs

    Darryl Day
      Share This:

      Is there a way to see the configuration of an agent remotely ? e.g. via GeneralManagerClient or other API's ?

       

      I'm interested in seeing configuration to identify if the agent has been amended and to check status on metric groups.

       

      Ideally for each metric group, granularity, summarization, and if enabled

       

      Thanks

        • 1. Re: Capacity Optimization Agent Configs
          Darryl Day

          I tried

           

          GeneralManagerClient -s localhost:10129 getAgentHistoryMetricGroupTimeList -A localhost -M "Process Statistics"

           

          but this returns

          Header:beginTime,endTime,

          Computation:Raw,Raw,

          Units:time_t,time_t,

          1569406493,1569409193,

          1569409193,1569412793,

          1569412793,1569416393,

          1569416393,1569419993,

           

          which implies  hourly ... ? which is not correct

          • 2. Re: Capacity Optimization Agent Configs
            Dima Seliverstov

            Re: Is there a way to see the configuration of an agent remotely seeing configuration to identify if the agent has been amended and to check status on metric groups.Ideally for each metric group, granularity, summarization, and if enabled

            No, there is no way to get the agent's Repository.cfg remotely, or view Look output remotely.

             

            You can see if agent History is enabled via

            remoteHistoryConfig -n localhost -q

            Info : history enabled on node :localhost

             

            Of via the GeneralManagerClient method  getAgentHistoryAgentHistoryConfiguration

            • 3. Re: Capacity Optimization Agent Configs
              Dima Seliverstov

              Re: getAgentHistoryMetricGroupTimeList returns hourly resolution

              The agent history has considerable more data points than daily UDR.

              The agent could be configured to have thousand of intervals. (Default is 1 hour at 10 second, but could be as low as 1 sec and longer duration)

              Very expensive to get, transfer and overwhelming for the user.

               

              The choice of 1 hour granularity was chosen, to provide a begin and end time of availability for the metric group.

              Using the 1 hour ranges, the desired interval can be chosen for the actual data request.

              (There is no remote API to see the number of intervals or data points, so for backwards compatibility with older agents, we do a series of drill downs at 1 hour increments)

              If you need to get the exact number of data points, you can iterate the hourly intervals via getAgentHistoryMetricGroupDataString (must specify a unique process pid, begin time, end time but no interval). Very expensive operation.

               

              The getUDRMetricGroupTimeList returns the exact number of intervals available.