Managing Business Transactions Flashcards
Order of discovery rules
- Manually excluded?
- Custom match rule?
- Custom match exclude rule?
- Auto discovery Rule?
- Ignore
business transaction
- end-to-end, cross-tier processing path used to fulfill a request for a service provided by the application
- represents the data processing flow for a request, most often a user request
Actions on Business transactions (CHECK)
- viewing health rule violations
- configure thresholds
- rename
- group
- starting a diagnostic session
- classifying as a background task.
- delete
- exclude
- Configure
- Configure Threshold
- troubleshoot
- mark as permanent
- view health rule violations
Exit point
Outbound requests from an instrumented application tier
Correlation
- This linking of upstream exit points to downstream entry points
- maintains the client request context as it is processed by various tiers in your business application.
Version of downstream agents
To enable detection of all the components in a distributed business transaction, downstream agents must be at the same AppDynamics release or newer than upstream agents
Business transaction limits
prevent boundless growth of the business transaction list.
- Business Application Limits: Each application is limited to 200 registered business transactions.
- App Server Agent Limits: Each agent is limited to 50 registered business transactions.
- There is no limit at the tier level
- If you have multiple app agents on a single machine, the machine the business transactions originating from the machine could be up to the number of agents times 50.
Types of transaction detection rules
- Automatic transaction discovery rules
- Custom match rules
Permission to customize transaction detection rules.
Configure Transaction Detection
Permission to use Live Preview and Business Transaction Discovery features to stream
View Sensitive Data + Configure Transaction Detection
Live Preview is only available for
Java and .NET environments
To view the default order of transaction detection rules for a tier
- Navigate to Configuration > Instrumentation > Transaction Detection > Tiers.
- Click a tier to see the rules ordered by precedence and priority.
Transaction Detection Rule PrioritiesLink to Transaction Detection Rule Priorities
- Rule priority from highest to lowest. (0 is the lowest priority possible)
- Creation date from oldest to newest.
Default naming for auto discovered rule
- For web-oriented technologies that have URI entry points such (Java Servlets) => the first two segments of the URI.
- For Web services: the Web service name + the operation name.
- For message-oriented technologies (asynchronous message listener or message-driven bean (JMS)): destination name (the queue name) or the listener class name (if the destination name is not available.)
Can customize automatic transaction discovery rules as follows
- Add an automatic transaction discovery rule for an agent type.
- Enable or disable different types of automatically discovered entry points.
- Customize transaction naming for some entry points, such as most URI-based entry points.
Disable Automatic Transaction Detection for an Entry Point Type
- the app agent stops reporting metrics for previously-detected transactions for the now disabled entry point type
- agent only detects transactions based on custom match rules.
- disabled transactions are not deleted or excluded
- Exit point detection remains enabled.
Types of custom match rules
- A custom include rule defines an entry point to use in a new transaction.
- A custom exclude rule lets you prevent AppDynamics from detecting business transactions you are not interested in tracking.
Scope Configuration Model
allows you to bundle multiple tiers into a scope, and apply transaction detection rules to that scope
Strategies to maximise into business-critical operations
- Set transaction detection priorities and delete old transactions to ensure that AppDynamics instruments your most important transactions.
- Combine multiple transactions into rules and exclude unimportant transactions to ensure that you stay within the business transaction limits.
- Rename transactions to informative names and group together similar transactions so that your metrics are easier to read.
Group Business Transactions
- lets you collect multiple related transactions into a single organizational unit in the AppDynamics model of your environment.
- can see aggregate metrics for the group.
- metrics for individual transactions that make up the group remain available.
- Grouping transactions does not affect the overall count of registered business transactions
Exclude a Business Transaction
- When you exclude a business transaction, the accumulated metrics for the transaction along with its underlying configuration is retained
- disables the business transaction for metric processing purposes;
- works even if the processing path that the business transaction represents remains active in the monitored application
Delete a business transaction
- the accumulated transaction metrics are removed.
- deleted transaction is rediscovered if the corresponding function in the application is used.
A business transaction can be considered stale in the following scenarios
- You have decommissioned an application, and you want to delete the historical data associated with business transactions that made up the application.
- You have changed business transaction discovery rules to either eliminate or reorganize business transactions and need to remove unwanted or otherwise obsolete business transactions.
automatic cleanup ignores the business transactions that are:
- Marked as Permanent
- Older than three days
Find the rules that apply to certain tier
Configuration => Transaction Detection => Tiers => Right Click
Business transaction lockdown
Configuration => Instrumentation => More
Add Rule, Rule configuration
- HTTP Request match criteria
- Split transactiohn using request data
- Split transaction using payload
How to track BT
GUID is associated with every request (global universal identified definition) - trace the operation path
Prioritization recommendations
- 5-10% of transactions are most important (load profit) => concentrate on them
Troubleshoot too many / slow DB calls
- identify BTs with performance issues
- Use a diagnostic session / developer mode (non-prod)
- Examine transaction snapshot / call graph
- Check number, duration and nature of SQL statements
Diagnose too many / slow DB calls
- Snapshots => drill down => Call graph => Backend calls
- Snapshots => Slow calls and graphs => Slowest DB and Remote calls
capture Snapshots with the Preview Business Transactions Feature
only for servile
Business transaction discovery session
- interactive tools to help to create an optimal set of transaction detection rules.
- can preview the effects of all transaction detection rules on the node, without effect on prod
During the discovery session you can
- edit java agent transaction detection rules and preview BTs (JAVA only)
- Identify entry points from uninstrumented code
- browse classes/methods to identify entry points
Preview Busoeness transaction
JAVA only
Business transaction discovery tools
- Uninstrumented code
- Classes/Methods
Capture Snapshot during the Business transaction discovery is only available for
Servelet
Can start a live preview session for a new custom match rule on:
- Servelet
- POJO
Live preview mode
streams data from an active node, providing real-tome data for the following configurations:
- all transaction detection rules that apply
- A single custom match rule applied to a node
Limits for a live preview
- 100 session on the controller
- 20 sessions on an account
- 10 sessions on a business application
