Discussion Feed

Maria.Garcia · ‎03-02-2020

Thanks Allan, Yes, the SE graph seems to be the correct value but… How to solve that huge difference between BTs and SEs metrics? Which changes should we done on detection rules in order to have the right metrics on the BTs too? We have a dashoard for support team and we see that some tiers displays the right metrics on BT load but anothers don´t (and all of them have the same configuration) so metrics cannot be used as expected... Thanks

Maria.Garcia · ‎02-28-2020

Hi, Yes we have configured it due to: - BTs has to include the 2 segments and the soap action in order to capture the specific operation executed on the application - SEs configuration was added because some actions are not captured as BT, it only appears as SE. Which should be the best configuration in order to obtain a real total load in the load graph? Thanks a lot!

Maria.Garcia · ‎02-27-2020

Thanks Allan, Which metrics are used to calculate the load graph? I mean, I do not understand why a BT with 21 calls/min have service endpoints associated with 330 calls/min in each node and the tier only reflects in the load the 21calls/min... However other tiers in the same controller under the same rules detection are displaying values closer tan the expected ones. Just trying to understand how dbAPM calculates the load and how to solve the issue... Thanks

Maria.Garcia · ‎02-27-2020

Hi, We do not have any specific configuration, just detecting the first 2 segments and including the SOAP action But please, what we need is to confirm and verify which values are used to calculate the LOAD graph that is displayed in the Tier Flow Map. Thanks

Maria.Garcia · ‎02-26-2020

Thanks Alan, In this case the number of calls for an specific BT (21 calls/min) is much lower than the number of executions (330 calls/min) of the SE associated to that BT. So the load graph at tier level is not reflecting the real traffic of those nodes. How to solve it please? Thanks

Maria.Garcia · ‎02-26-2020

Hi, We have several tiers with several Business Transactions and several Service Endpoints (in fact almost the traffic used to be detected under Service Endpoints) but the load values are not the expected ones. The tier flow map shows the following load: That seems to be the Business Transactions values: But the service endpoints of that tier are executing a lot of calls (a higher value of calls): The Service endpoint load graph displays the expected values: From our point of view the tier load should take into account all the calls under the BTs, I mean, also add all the service endpoints calls, but seems not be the case... We need to confirm how dbAPM calculates the calls values displayed in the Load graph under the Tier Flow Map view. Which entities are taking into account to obtain that values? Please kindly confirm it. Thanks a lot in advance!

Maria.Garcia · ‎02-20-2020

Thanks Ryan, Sorry but I do not see how information points can provide us that information. Should we use the code to identify how many calls are being processed? Thanks

Maria.Garcia · ‎02-20-2020

Hi, Do you know if is there any metric/function to check how many requests/calls are really processed? I mean, we would like to know if a tier is queuing requests. So we would need to calculate how many calls/requests are received and how many are really processed... Thanks in advance.

Maria.Garcia · ‎12-12-2019

Hi, Is it possible to check/list all the transactions registered as first class? Thanks

Maria.Garcia · ‎12-12-2019

Hi, Not solved yet 😞

Date Registered	‎07-05-2017 05:26 AM
Date Last Visited	‎04-01-2020 12:37 PM
Total Messages Posted	39
Total Kudos Received	3

Discussion Feed

Re: LOAD graph values on Tier Flow Map view

Re: LOAD graph values on Tier Flow Map view

Re: LOAD graph values on Tier Flow Map view

Re: LOAD graph values on Tier Flow Map view

Re: LOAD graph values on Tier Flow Map view

LOAD graph values on Tier Flow Map view

Re: Requests being procesed

Requests being processed

Business Transaction registered as First Class

Re: Remote Services detection