Transforming Logs into Transactions
Transactions provide you the ability to run aggregations on top of your logs across all other collected attributes within Middleware. This is useful for building a transactional view of your logs, selecting specific attributes to group by, and identifying broader patterns related to the log you are actively filtering.
Transactions work by compiling logs based on occurrences in a series of actions, like a user’s session or a request handled across your microservice architecture. Examples of transactions range from actions within a mobile app, to function calls and CPU instructions.
Transaction Measures
Measures allow you to add aggregations across your chosen grouping attribute:
| Measure | Description |
|---|---|
| Count | Tracks the total number of times the aggregated metric has been fired |
| Max | Displays the maximum value of the aggregated metric |
| Most Frequent | Identifies the most frequent value of the aggregated metric |
| Where | Adds additional aggregation layer to query |
| Contains | Filters log entry based on whether the specified field contains a particular string or subpattern |
| Does Not Contain | Filters log entry based on whether the specified field does not contains a particular string or subpattern |
| Greater Than | Aggregates metrics that are greater than a specified threshold or reference point |
| Smaller Than | Aggregates metrics that are less than a specified threshold or reference point |
Create a Transaction
Navigate to the logs page, select the Transactions tab, choose your desired aggregation metric, and add one or multiple measures to better understand your logs.
Transaction Examples
Aggregates the container_name across all logs and then a secondary aggregation is performed specifically on containers with names that contain the subpattern or string kafka
Next Steps
- Log Monitoring Overview
- Creating Log Filters
- Log Explorer
- Custom Metrics
- Creating Alerts
- Real User Monitoring (RUM)
Was this page helpful?