Skip to main content

Techdocs Library > White papers >

Routing Linux and UNIX SYSLOG data to IBM Operations Manager for z/VM



Document Author:
Additional Author(s):

Michael Sine
Tracy Dean


Document ID:

WP101379


Doc. Organization:

Advanced Technical Sales


Document Revised:

12/20/2012


Product(s) covered:

IBM Operations Manager for z/VM







Abstract: IBM Operations Manager for z/VM provides the DEFTCPA statement to establish a TCP/IP connection to Operations Manager. This configuration statement allows Operations Manager to collect and process syslog data or file input from local or remote systems. Many customers centralize log management to Operations Manager for z/VM, to meet log management best practices. The syslog or file data is processed in the same manner as SECUSER or OBSERVER data from a monitored console. This means that rules can be written to automatically take an action if a specified message appears in the syslog data. In addition, once this data is collected by Operations Manager, it can be viewed using the VIEWCON command, the same way console data is viewed. This whitepaper will document the steps required to route local and remote syslog data to Operations Manager and to configure Operations Manager to receive it, using the DEFTCPA configuration statement. Examples using Linux syslogd, syslog-ng, rsyslog, and UNIX syslogd are provided.

Routing Syslog to OpsMgr Version Dec2012 Final.pdfRouting Syslog to OpsMgr Version Dec2012 Final.pdf



Classification:

Software

Category:

Operational Management




Platform(s):

Cross-Platform; IBM System z Family

S/W Pillar(s):

Tivoli; IBM System z Software

O/S:

AIX; HP-UX; Linux; VM

Keywords:

Operations Manager for z/VM, syslog, syslog-ng, rsyslog, centralized syslog, centralized log management, DEFTCPA

The Techdocs Library
Is this your first visit to Techdocs (the Technical Sales Library)?

Learn more


Techdocs QuickSearch

: