New Relic APM identifies many transactions that serve your end users and other systems. Some of these transactions are more important than others, and Key Transactions are a great way to focus on the ones that matter most to your business. In addition, Key Transactions provide you with specialized Apdex thresholds, alert conditions, and X-Ray Sessions.
In the past you could make Key Transactions only out of Web transactions, but now it is possible to create them for any type of transaction. This completes the unification of transaction types that started in February.
A message queue example
Message queues are commonly used to communicate between processes and manage workloads. The New Relic Java agent identifies taking a message from a queue using JMS as a transaction. Here is what a JMS transaction looks like as a Key Transaction:
This Key Transaction was created from an automatically identified JMS transaction. You can set a specific Apdex threshold, choose a specific Alert Policy, and name the Key Transaction whatever you would like.
If the Key Transaction is having trouble, you can get a burst of additional insight into the problem by running an X-Ray Session on it.
Key Transactions for any transaction is available today with the Java Agent version 3.10 and above. Support for any Key Transaction will be released for other languages over time.
If you are using the Java agent for non-Web workloads, this is a great time to upgrade and try out the new functionality.