Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
02-21-2018
02:24 PM
- edited on
08-04-2022
01:53 PM
by
Claudia.Landiva
[Air-Date February 21, 2018] Run Time: 56 minutes.
@Mohammed.Rayan led this introductory transaction analytics session. During this session, Mohammed also demonstrated the capabilities of transaction analytics and shed light on the art-of-the-possible with Business iQ. See below for the attached slide deck and additional resource links.
BIQ Community Resources:
In the Data view, you can customize your search criteria and filter by time frame and fields (e.g., Application or Business Transaction) to see raw data.
Within the Visualization view, you can create and save a widget to your Dashboard. One helpful widget type is the Funnel widget.
Additional properties were added as part of 4.4 to provide more control over the widget appearance.
If you click the gear icon in the top-right corner of the Controller and select AppDynamic Agents and the Analytics Agents tab, you can see the Transaction Pipeline Health and Log Pipeline Health. You can also sort by All Agents, Agents Publishing Log Data, and Agents Publishing Transaction Data, which can help you identify which agents are publishing the transaction data.
As a best practice, we recommend you start by enabling just a few Business Transactions that you know well and matter most to see what the patterns and contents are and then slowly increase from there.
Avoid enabling Business Transaction collections for analytics for everything initially, as it can be challenging and can cause you to run into other types of issues (e.g., connectivity or licensing issues).
Additionally, on the Business Transaction schema that we have, you may know that we have an All Other Traffic bucket. Many times what we find is that Business Transactions are enabled but in reality, that information is going into the All Other Traffic bucket because you are limited in terms of Business Transaction numbers per node or per application. That’s why being iterative here with your Business Transaction collections makes a lot more sense and will be useful for you in learning the flow as you enable them. Start with one Business Transaction that you know really well and incrementally go from there.
It pertains only to transaction collection. SQL Data collections will show you the parameter value as part of that transaction so when the analytics data set, you’ll actually see the value was passed to that particular SQL. That’s what this will allow you to do.
It doesn’t send any other event types. In SQL Data Collectors, that’s all the SQL database calls from the Business Transactions, and from the parameters of those SQL calls, we capture specific custom or business information.
Please post your questions in the comments.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form