The system environment variable @NX_EVENT_LOG_EXCLUDE, which is set in the NX.env file and requires a restart of the CA SDM services, lets you control the amount of data that is stored in the event log (event_log table). This variable lets you store only the events you want to track, report on, and use as part of the Recent Activity that can be launched as a button from the Quick Profile page.
In this variable, commas separate list items (for example, @NX_EVENT_LOG_EXCLUDE = FAQ,KD_OPEN). For example, if you use the LOGIN,LOGOUT events from the following table (@NX_EVENT_LOG_EXCLUDE value of LOGIN,LOGOUT), the product does not record login and logout events.
Refer to the following information when customizing data to store in the event log using this variable:
Event |
Enum |
By |
Sets |
Comments |
---|---|---|---|---|
LOGIN |
1 |
CA SDM |
|
Specifies that the User logs in to the system. |
LOGOUT |
2 |
CA SDM |
numdata1 |
Specifies that the User logs out, where numdata1=logout reason: |
CR_CREATE |
3 |
CA SDM |
sd_ob_type, sd_obj_id, |
Indicates that the User creates a request, where numdata1=id of affected end user. |
ISS_CREATE |
4 |
CA SDM |
sd_ob_type, sd_obj_id, |
Indicates that the User creates a change order, where numdata1=id of the affected end user. |
CHG_CREATE |
5 |
CA SDM |
sd_ob_type, sd_obj_id, kd, numdata1 |
Indicates that the User creates an issue, where numdata1=id of the affected end user. |
|
6 |
Knowledge Management |
kd |
Specifies that the Analyst emails a document. |
LINK |
7 |
Knowledge Management |
kd, sd_obj_type, sd_obj_id |
Indicates that the User accepts a solution, and links it to a ticket. |
UNLINK |
8 |
CA SDM |
sd_id, sd_obj_type, |
Specifies that the User unlinks a solution from a ticket. |
SEARCH |
9 |
Knowledge Management |
numdata1, |
Indicates that the User searches knowledge, where numdata1= |
FAQ |
10 |
Knowledge Management |
numdata1 |
Indicates a FAQ search, where numdata1= |
DT_ |
11 |
Knowledge Management |
kd, |
Indicates that the User navigates a decision tree, where numdata1= textdata1=path. |
KD_ |
12 |
Knowledge Management |
kd |
Indicates that the User bookmarks a KD. |
KD_ |
13 |
Knowledge Management |
kd, |
Indicates that the User adds a comment to a KD, where numdata1= |
KD_CREATE |
14 |
Knowledge Management |
sd_ob_type, sd_obj_id, kd |
Specifies that a User creates a document. CA SDM IDs are used when a KD is created using submit knowledge from a request or an issue. |
KD_OPEN |
15 |
Knowledge Management |
kd, |
Indicates that a User opens a KD, where numdata1=BU_TRANS ID. |
KD_RATE |
16 |
Knowledge Management |
|
Indicates that a User rates a KD, where numdata1=BU_TRANS ID. |
KD_NEW |
17 |
Knowledge Management |
numdata1 |
Specifies that a User clicks on the New Documents folder in the Knowledge tab. |
NX_ATTACH_ AUDIT_TO_NEW_TICKET
|
18 |
CA SDM |
|
When a User opens a new ticket, all events for the current session appear by default on the Event Log tab of the ticket. 0—Only events relevant to the ticket appear on the Event Log tab. 1—All events for the current session appear on the Event Log tab of the ticket. |
TICK_OPEN |
19 |
CA SDM |
|
Indicates that the ticket was viewed. |
TICK_SEARCH |
20 |
CA SDM |
|
Indicates the user who searched for tickets and links the number of searches. |
KD_PRNT |
21 |
Knowledge Management |
kd |
Indicates the knowledge document was printed. |
Copyright © 2013 CA.
All rights reserved.
|
|