These socket summary tables aggregate timer and byte count information for socket operations:
socket_summary_by_event_name: Aggregate timer and byte count statistics generated by the
wait/io/socket/*instruments for all socket I/O operations, per socket instrument.
socket_summary_by_instance: Aggregate timer and byte count statistics generated by the
wait/io/socket/*instruments for all socket I/O operations, per socket instance. When a connection terminates, the row in
socket_summary_by_instancecorresponding to it is deleted.
The socket summary tables do not aggregate waits generated by
idle events while sockets are waiting for
the next request from the client. For
event aggregations, use the wait-event summary tables; see
Section 10.20.1, “Wait Event Summary Tables”.
Each socket summary table has one or more grouping columns to
indicate how the table aggregates events. Event names refer to
names of event instruments in the
EVENT_NAMEcolumn. Each row summarizes events for a given event name.
OBJECT_INSTANCE_BEGINcolumn. Each row summarizes events for a given object.
Each socket summary table has these summary columns containing aggregated values:
These columns aggregate all operations.
These columns aggregate all receive operations (
These columns aggregate all send operations (
These columns aggregate all other socket operations, such as
SHUTDOWN. There are no byte counts for these operations.
table also has an
EVENT_NAME column that
indicates the class of the socket:
server_unix_socket. This column can be
grouped on to isolate, for example, client activity from that
of the server listening sockets.
The socket summary tables have these indexes:
Primary key on (
Primary key on (
Index on (
TRUNCATE TABLE is permitted for
socket summary tables. Except for
it resets the summary columns to zero rather than removing