From mobile apps to enterprise payment systems, digital business services depend upon fast and seamless exchanges of electronic business transactions. When transaction performance lags, business suffers. AutoPilot for Transactions tracks, analyzes, and visualizes the status and integrity of every transaction, from end-to-end, enabling fast problem resolution before users are affected.
- See Your Business Performance – real-time message and transaction flow visualization provides instant awareness of any emerging performance issues that can negatively impact your business.
- Cut Costs By Reducing Incidents – slash the frequency, duration, and impact of incidents with real-time monitoring and automated trending that eliminates false alarms and detects issues before users notice them.
- Understand How Transaction Flows Affect Your Business in Real-Time – discover and track transactions, “stitching” or correlating them together in real-time across distributed systems, mainframes and corporate firewalls.
- Rapid Root-Cause Analysis – when problems do occur, instantly uncover the root-cause of problems with tracking that provides the visibility and detail necessary to begin immediate remediation.
The life of a payment transaction
AutoPilot stitches together complete end-to-end transactions across the enterprise correlating user transactions with applications and middleware, from mobile to mainframe.
AutoPilot monitors your transaction performance at every stage, compares results to benchmarks established for user-defined service level agreements (SLAs), and generates alerts when specified thresholds are breached—or trending towards breach.
- A high-performance Complex Event Processing (CEP) engine correlates transactional and operational data to answer “what happened” and “why it happened” questions when problems occur.
- Determines root-cause for problems with drilldown to the offending component, SQL query, method call, or message payload.
- Stitches end-to-end transactions together across Web and legacy tiers: Web Services, Java, .NET, MQ and CICS.
- Ability to map transaction topology to business processes and evaluate compliance of execution vs. business objectives.
- User-defined, rule-based policies for real-time monitoring and automatic notification of abnormal behaviors or conditions.
- Tracks failed, in-flight, completed,and missed transactions.
- Follows complex transactions spanning many hops, where they split and morph.
- Generates reports about transaction activity on a daily, weekly, monthly basis.
- Collects, aggregates, filters and correlates metrics and events from infrastructure systems with data from external sources such as RSS, news feeds, and email messages. It can transmit alerts over private Twitter networks.
- Ability to track long-running asynchronous transactions even when the parent has terminated.
- Real-time measurement of transaction volume, in-flight transactions, violations, violation rate, failures, failure rate, latency, duration (total, maximum, avg.), and more.
- Extracts message payload (e.g., important attributes such as transaction value and correlation IDs) to stitch transaction components together into a coherent whole.
- Can track and store 100 percent of transactions 100 percent of the time without additional external tools like Dynatrace+Splunk, AppDynamics+Splunk, etc.
- Automatically discovers applications and system components, transaction flow and application interdependencies.
- Stores all of the performance-related information in a searchable SQL database.
- Discovers transactions without manual mapping or path definitions (e.g., BMC).
- Audit trail for everything including message payload, http headers, and SQL queries.
- API available using REST as well as Java.
AutoPilot for Transactions provides charting and reports that show the continuous performance of transactions as they run. In addition, real-time queries can be invoked to see historical performance.
Example of AutoPilot transaction topology view showing relationships, queues, and simple statistics
The Importance of Mastering Your Transaction Flow
Because transactions range from simple synchronous message exchanges between point-to-point application connections to much more complex asynchronous communications, a sophisticated tracking and monitoring solution is required.
In the latter instance, long-running, multi-step asynchronous transactions transit your IT infrastructure and sometimes cross one or more corporate firewalls. They frequently involve a broker routing the messages associated with a single transaction to many discrete destinations (DBs, servers, apps, mainframes, etc.). And because a message broker is involved, these complex transactions defy standard tracking and analysis via tagging or statistical sampling techniques.
AutoPilot stitches together complete end-to-end transactions by examining method calls and individual message payload contents, correlating them and presenting intuitive visualizations of any pending or existing breaches in expected behavior and performance.
Example of a financial transaction failure involving SWIFT messages and the Calypso Trading System
(red color bars flag problem areas for the user)
With today’s extreme emphasis on customer experience, fast problem resolution is more critical than ever before. A 360-degree awareness of the IT processing events underlying every transaction, plus the ability to instantly pinpoint, diagnose, and repair issues before end users sense any service degradation, is absolutely essential.
With AutoPilot for Transactions, view your world of transactions with clarity, across your entire infrastructure, in real-time. With automatic discovery, flagging, and tracking of flows as they traverse your IT infrastructure, AutoPilot provides the real-time visibility IT pros need to track messages and transactions wherever they go—across distributed systems, mainframes, and beyond firewalls.
This deep transaction visibility, down to the method level and the exact contents of individual message payloads, is what enables fast problem resolution.
If you are interested in additional, in-depth material on transaction tracking topics, we suggest the following from the Nastel Library: