CAS Host History domain
Tracks CAS host events, including servers or clients going in or out of service. This topic describes the domain's entities and attributes.
Available to roles: all
Host Entity
Identifies a CAS host (a database server) and the current status of CAS (online/offline). A CAS Host entity is created the first time that CAS is seen on a database server host. It is updated each time that the online/offline status changes. The Host entity is available in the CAS Host History domain and the CAS Config domain.
| Attribute | Description |
|---|---|
| Host Id | Host ID |
| Host Name | Database server host name (might display as IP address) |
| IP | Host IP |
| Is Online | Online status (Yes/No) when record was written |
| OS Type | Operating system: UNIX or WIN |
Host Event Entity
Date and time of an event in the CAS client/server relationship. A host event entity is created each time an event is detected or signaled (see the event types) by CAS.
| Attribute | Description |
|---|---|
| Audit Host Event Id | Identifies the host event entity |
| Audit Host Id | Identifies the host |
| Event Time | Date and time that the event was recorded |
| Event Type | Identifies the event being recorded: Client Up - CAS started on database server host Client Down - CAS stopped on database server host Failover Off - A server is available (following a disruption), so CAS data is being written to the server Failover On - The server is not available, so CAS data is being written to the failover file Server Down - The database server stopped Server Up - The database server started |
| Original Timezone |
The UTC offset. This is done in particular for aggregators that have collectors in different time zones and so that activities that happened hours apart do not seem as if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |
| Timestamp | Timestamp for creation of the entity |