Skip to main content

Logging & Monitoring

Lesson status

This lesson is a focused outline. Expand with the linked IBM docs.

DataPower generates rich logs and exposes detailed runtime status. The job is to route the right logs to the right place and watch the metrics that matter.

Log targets​

A log target is an object that captures log events matching a filter and sends them somewhere:

  • Filter by event category (auth, mpgw, ssl, xmlfirewall, …) and priority (debug → info → notice → warn → error → critical).
  • Send to files, syslog/TCP, SNMP, NFS, or off-box collectors.
  • In production, ship logs off-box (syslog/DPOD) so they survive restarts and can be searched centrally.

Status & monitoring​

  • Status providers: object op-state, CPU, memory, connection counts, TLS, queue depths — via WebGUI, CLI show, or REST.
  • Monitors: message monitors and service-level monitoring (SLM) enforce and observe rates/quotas.
  • DPOD aggregates logs/transactions/metrics across many gateways.

Outline: topics to expand​

  • The default log and the system log; adjusting log level safely in prod.
  • Creating a syslog log target and verifying delivery.
  • Correlating a transaction across logs via the global transaction ID.
  • Key metrics to alert on (memory, op-state down, TLS/cert errors).

Reference​

Knowledge Check

What does a log target do?