2 Replies Latest reply on Nov 12, 2019 4:49 PM by Matthew Highcove

    Best way to find out the use of an adapter in AO

    Alexander Foldats
      Share This:

      Hello,

       

      We are in a client that has to remove some adapters to be able to enable new ones as they only have contracted 5 total activated. We are in doubt that if some adapters are being used at all and I was wondering if there is an easy way of doing this? I checked the documentation on what is gathered with Grig Performance Metrics but it does not look like it stored the use of adapters.

       

      Apart from investigating all the modules that are activated and checking each one to see if an adapter is called, is there a better way?

        • 1. Re: Best way to find out the use of an adapter in AO
          Aryan Anantwar

          Hello,

           

          If you have TSO Dashboard installed in your environment you can check the adapter usage as below:

          A6374217.jpg

          It shown only the adapters in chart which are in use, the adapters which are activated on grid but not executed in specified timeframe will not be present on this chart.

           

          Regards,

          Aryan Anantwar

          • 2. Re: Best way to find out the use of an adapter in AO
            Matthew Highcove

            You can also check the peer logs. Every five minutes a peer writes something like this to its grid.log:

             

            12 Nov 2019 08:46:38,786 [Thread=AMP - Health Component - Periodic Task Executor - 1] INFO  HealthComponent [PeerName=CDP]  

            HEALTH_STAT, 2019-11-12 08:46:38, A:CDP:CommandLineAdapter, COUNT_OF_ACTOR_ADAPTER_CALLS, 14, 2019-11-11 08:57:34

            HEALTH_STAT, 2019-11-12 08:46:38, A:CDP:CommandLineAdapter, RUNNING_STATE, running, 2019-11-05 04:51:56

            HEALTH_STAT, 2019-11-12 08:46:38, A:CDP:HTTPAdapter, RUNNING_STATE, running, 2019-11-05 04:51:56

            ...

             

            This tells you every adapter on every peer, how many requests each adapter has run since the last time it was restarted, and the last time each adapter ran a request (the second date/time, at the end of each entry). This entry shows that the adapter named CommandLineAdapter on the peer named CDP has run fourteen requests since its last restart, and the most recent event ran at 08:57 on Monday. If an adapter has no COUNT_OF_ACTOR_ADAPTER_CALLS or COUNT_OF_MONITOR_ADAPTER_EVENTS entry, its count is zero. This logging exists on every peer on every supported version of BAO/TSO, so you can check it even if you do not have a Dashboard installed.