Important considerations in product configuration

Integration Server logs scale based on the logger configuration. For example, if you are running services in Integration Server, the file size of the session log or the file size of the service log is governed by Integration Server and not by End-to-End Monitoring.

Self-hosted transactions are not tested with End-to-End Monitoring collector. Do not route your self-hosted transactions to the collector to avoid a transaction overload on the collector.

Note: End-to-End Monitoring currently supports OTLP/HTTP that uses Protobuf payloads encoded either in binary format or in JSON format. Regardless of the encoding the Protobuf schema of the messages is the same for OTLP/HTTP. Support for OTLP or gRPC is planned in future releases.

Currently unsupported capabilities

If you have an existing hybrid monitoring agent setup that is installed by using the IBM® webMethods Installer and IBM webMethods Update Manager-based fixes, use the following steps to install an IS package-based hybrid monitoring agent.

  • Uninstall the existing End-to-End Monitoring setup by using the IBM webMethods Installer.
  • Remove the custom_wrapper.conf changes previously configured during the IBM webMethods Installer based setup.
  • Remove any copied JAR file or packages from integration or lib folders that are previously configured during the IBM webMethods Installer based setup.
  • Read the Setup that uses Integration Server (IS) package section to install a hybrid monitoring agent by using package-based approach.