Skip to Content

Enabling and analyzing logs

For BMC Helix Telco Extensions, capture the following log files to debug issues:

Log file

Description

Reference

Filter log

The filter log file shows all of the filters that were checked during an operation. If a filter was executed, the log also provides a list of the operations performed.

Active Links log

The following information is generated when an active link is executed:

  • Name
  • Transaction ID (only for PWA)
  • Start, end, and elapsed time (to 1/10,000 of a second)
  • Operation that fires the active link
  • Execution order
  • Form applied to
  • Linked to which field (if applicable)
  • Mode (for example, Query, Modify, Submit)
  • User's name
  • Qualification and if it passes or fails
  • Actions generated:
    • Action number
    • Type (for example, Set Fields, Set Characteristics, Push Fields)
    • Name, new characteristics, and value of affected fields, if applicable.

API log

The API log traces all API calls run on the server, regardless of their origin.

SQL log

The SQL log is similar to the filter log, but the SQL log file consists of a series of SQL commands (one per line), each of which contains the information listed in the Log entry format.

(For impact analysis related to an incident only)

Audit log and Notification log

After you run an impact analysis for an incident, you can view the log files related to the impact analysis process.

To open the log information, from an existing incident, click More > Logs.

Impact analsysis Notification log_25.1.00.png


Processes to be reviewed in the log files

Review the following processes in the log files identified above:

  • Alarm Management
    • AM-Incident - Create
    • AM-Incident - Handle Secondary Alarms
    • AM-Incident - Resolution
  • Related Parties
    • RP-Help Desk Append Related Party
    • RP-Help Desk Update Related Party

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Telco Extensions 25.3