Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Flink will be delivered by IBM Confluent Platform.

For more information, see the support lifecycle transition and software ordering completion announcement.

Configuring trace logging

When requested by IBM support, trace logging can be configured in Event Processing to add more troubleshoot logging. This is useful for attempting to debug the system, as it captures additional details about what precisely is happening in the product code.

Note: Different levels of trace logging are permitted. However, the most relevant levels to use when you configure troubleshooting are trace or debug.

Configure trace logging for the Event Processing or IBM Operator for Apache Flink instances as follows.

For the Event Processing instance

Trace logging can be configured for an Event Processing instance by editing the EventProcessing custom resource. This enables trace logging that can be observed from the pod logs. To enable trace logging, update your EventProcessing custom resource to set the TRACE_LEVEL and TRACE_SPEC environment variables:

kind: EventProcessing
[...]
spec:
  authoring:
    template:
      pod:
        spec:
          containers:
            - env:
                - name: TRACE_LEVEL
                  value: "<VALUE>"
              name: ui
            - env:
                - name: TRACE_SPEC
                  value: "<VALUE>"
              name: backend
  [...]

Note: <VALUE> is provided by IBM Support.

It is possible to configure trace logging for an IBM Operator for Apache Flink instance by editing the FlinkDeployment custom resource. This enables trace logging that can be observed from the Flink pod logs.

To enable trace logging, update your FlinkDeployment custom resource to include the logging configuration:

kind: FlinkDeployment
[...]
spec:
  logConfiguration:
    log4j-console.properties: >
      <VALUE>
  [...]

Note: <VALUE> is provided by IBM Support.

See also the FlinkDeployment Logging Configuration documentation.