BigData Intelligence Session domain
Reports on Client/Server database session. This topic describes the domain's entities and attributes.
Available to roles: all.
This domain is available in Guardium systems that have a defined datasource of type GBDI.
BigData Intelligence Session Entity
| Attribute | Description |
|---|---|
| Access Id | Uniquely identifies the access period. |
| Analyzed Client IP | Applies only to encrypted traffic; when set, client IP is set to zeroes. Analyzed Client IP has a map for CEF source. If the query used for the CEF does NOT contain the Client IP but contains the analyzed client IP, the analyzed client IP is used for the source. If both are included in the query, then the Client IP takes precedence. |
| Client Host Name | Client Host Name |
| Client Port | Client port number |
| Database Name | Name of database for the session (MSSQL or Sybase only). For Oracle, Database Name may contain additional and application specific information such as the currently executing module for a session that has been set in the MODULE column of the V$SESSION view. |
| DB User Name | User that connected to the database, either local or remote. |
| Guardium Appliance | Host name of collector that reported this data. |
| Ignored Flag | |
| Login Succeeded | |
| Network Protocol | Network protocol used (for example, TCP, UDP. For K-TAP on Oracle, this displays as either IPC or BEQ). |
| OS User | OS user account for the interaction. |
| Sender IP | Sender IP |
| Server Host Name | Server Host Name |
| Server IP | Server IP |
| Server Port | Server port number |
| Server Type | For example: DB2, Oracle, Sybase... |
| Service Name | Service name for the interaction. In some cases (AIX® shared memory connections, for
example), the service name is an alias that is used until the actual service is connected. In those
cases, once the actual service is connected, a new session is started - so what the user experiences
as a single session is logged as two sessions. For Teradata, Service name contains the session logical host id value. |
| Session End | Date and time the session ended. Session End is also a Main Entity. Access this secondary entity by clicking on the Session primary entity. |
| Session End Date | Date only from the Session End. |
| Session ID | Uniquely identifies the session. |
| Session Ignored | Indicates whether or not some part of the session was ignored (beginning at any point in time). |
| Session Start | Date and time session started. Session Start is also a Main Entity. Access this secondary entity by clicking on the Session primary entity. |
| Session Start Date | Date only from the Session Start. |
| Source Program | Source program for the interaction. |
| Uid Chain | For a session reported by Unix S-TAP (K-Tap mode only), this shows the chain of OS users,
when users su with a different user name. The values that appear here vary by OS platform; for
example, under AIX the string IBM IBM IBM may appear as a prefix. For Solaris Zones, user ids may be reported instead of user names in the Uid Chain. |
| UTC Offset | The time difference between UTC time and the time of the collector that reported that data. |