ERi/LOGR Modernization Guide

ERi/LOGR provides an API for applications to log events to the z/OS System Logger, even if those applications are not authorized to directly access the logger. It also includes tools to view and access those logs.

ERi/LOGR is primarily a tool set, providing APIs and utilities for application logging and log access. It acts as middleware between applications and the z/OS System Logger.

Organizations that need to ensure comprehensive logging of application events on z/OS, especially when some applications lack direct authorization to the System Logger, benefit from ERi/LOGR.

Consider ERi/LOGR when you need a centralized and secure way to manage application logs on z/OS, particularly when dealing with applications that have varying levels of authorization.

Alternatives include native z/OS logging facilities, other SMF data collection tools, or custom-built logging solutions. However, ERi/LOGR provides a specific API and access control layer.

ERi/LOGR runs on z/OS and is dependent on the z/OS System Logger. It typically runs within an LPAR.

ERi/LOGR requires the z/OS System Logger to be active and configured. Applications must be able to call the ERi/LOGR API.

ERi/LOGR provides an API for applications to write log data. It also provides APIs and facilities to read log data.

The specific API endpoint patterns and method names are vendor-defined. Consult the ERi/LOGR documentation for the exact syntax and parameters.

ERi/LOGR provides a centralized and controlled way to manage application logs, ensuring that important events are captured and accessible for auditing, troubleshooting, and compliance purposes.

Without ERi/LOGR, organizations might struggle to maintain consistent and secure logging practices across all applications, potentially missing critical events or exposing sensitive data.

ERi/LOGR can help organizations meet regulatory requirements related to data logging and auditing by providing a secure and auditable logging solution.

ERi/LOGR controls access to the z/OS System Logger through its API, allowing only authorized applications and users to write or read log data.

ERi/LOGR likely supports standard z/OS authentication methods. Consult the vendor documentation for specifics.

ERi/LOGR provides audit logging capabilities to track access to log data and changes to the system configuration.

ERi/LOGR is typically deployed on-premise within the z/OS environment.

Implementing ERi/LOGR requires z/OS systems programming expertise and familiarity with the z/OS System Logger.

Ongoing operational requirements include monitoring the health of the ERi/LOGR components, managing user access, and ensuring sufficient storage for log data.