JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Dynamic Tracing Guide     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  About DTrace

2.  D Programming Language

3.  Aggregations

Aggregating Functions

Aggregations

Printing Aggregations

Data Normalization

Clearing Aggregations

Truncating aggregations

Minimizing Drops

4.  Actions and Subroutines

5.  Buffers and Buffering

6.  Output Formatting

7.  Speculative Tracing

8.  dtrace(1M) Utility

9.  Scripting

10.  Options and Tunables

11.  Providers

12.  User Process Tracing

13.  Statically Defined Tracing for User Applications

14.  Security

15.  Anonymous Tracing

16.  Postmortem Tracing

17.  Performance Considerations

18.  Stability

19.  Translators

20.  Versioning

Printing Aggregations

By default, multiple aggregations are displayed in the order they are introduced in the D program. You can override this behavior using the printa function to print the aggregations. The printa function also enables you to precisely format the aggregation data using a format string, as described in Chapter 6, Output Formatting.

If an aggregation is not formatted with a printa statement in your D program, the dtrace command will snapshot the aggregation data and print the results once after tracing has completed using the default aggregation format. If a given aggregation is formatted using a printa statement, the default behavior is disabled. You can achieve equivalent results by adding the statement printa(@{_}aggregation-name{_}) to a dtrace:::END probe clause in your program. The default output format for the avg, count, min, max, and sum aggregating functions displays an integer decimal value corresponding to the aggregated value for each tuple. The default output format for the lquantize and quantize aggregating functions displays an ASCII table of the results. Aggregation tuples are printed as if trace had been applied to each tuple element.