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 Apache Flink will be delivered by IBM Confluent.

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

Attention: This version of Event Streams has reached End of Support. For more information about supported versions, see the support matrix.

Gathering logs

To help IBM support troubleshoot any issues with your Event Streams installation, run the log gathering script as follows. The script collects the log files from available pods and creates a compressed file. It uses the component label names instead of the pod names as the pod names could be truncated.

  1. Download the get-logs.sh script from GitHub.
  2. Ensure you have installed the Kubernetes command line tool and the IBM Cloud Private CLI as noted in the installation prerequisites.
  3. Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
    cloudctl login -a https://<cluster-address>:<cluster-router-https-port>

  4. Run the script as follows:
    ./get-logs.sh -n <namespace> -r <release-name>

    If you do not specify a namespace, the script retrieves logs from the default namespace as requested in the cloudctl login. If you do not specify a release name, the script gathers logs for all releases.