Integrating Instana with OMEGAMON Data Provider
To integrate Instana® with OMEGAMON® Data Provider, you configure the OMEGAMON Data Connect component of OMEGAMON Data Provider to send data to Instana using one of two output methods: HTTP or TCP.
Optionally, you can also configure OMEGAMON Data Provider to send just the data that Instana specifically supports, such as particular OMEGAMON attribute groups.
This documentation provides an overview of configuring OMEGAMON Data Provider to send data to Instana. For additional hints and tips, including details of the corresponding prerequisite OMEGAMON historical data collections, see the Instana configuration topics on GitHub.
For details of the Instana architecture and how to configure Instana to ingest data from OMEGAMON Data Provider, see the IBM® Instana Observability on z/OS® documentation.
Overview of Instana integration with OMEGAMON Data Provider
Instana can ingest data from two output methods of OMEGAMON Data Provider:
- TCP
- OMEGAMON Data Provider sends data in JSON Lines format over TCP to a port on which Instana is listening.
- HTTP
- OMEGAMON Data Provider sends data in JSON format in HTTP POST requests to an Instana HTTP endpoint.
For details on which output to use for your environment, see the Instana documentation.
OMEGAMON historical data collections
Historical data collections are a prerequisite for using OMEGAMON monitoring agents as a data source for OMEGAMON Data Provider. Before configuring OMEGAMON Data Provider, you need to create a historical collection for each attribute group supported by Instana.
For details of the attribute groups supported by Instana, see the Instana documentation.
To create historical collections, you use the OMEGAMON enhanced 3270 user interface (e3270UI) or the Tivoli® Enterprise Portal (TEP). For more information about creating historical collections, see the OMEGAMON documentation for e3270UI and TEP.
OMEGAMON Data Provider configuration members
Two configuration members specify which OMEGAMON attributes OMEGAMON Data Provider sends, and to where.
- RKANPARU(KAYOPEN)
- Specifies which attribute groups to send to OMEGAMON Data Broker.
OMEGAMON Data Broker forwards attributes to OMEGAMON Data Connect.
The
getting started
task Configuring OMEGAMON monitoring agents as a data source describes editing the KAYOPEN member.For KAYOPEN entries that match the attribute groups supported by Instana, see the Instana documentation.
- connect.yaml
- Specifies where OMEGAMON Data Connect sends attributes, such as
Instana.
The
getting started
task Configuring OMEGAMON Data Connect describes editing connect.yaml. When you reach that step, specify a TCP output or an HTTP output for Instana.Here is the typical format of a TCP output for Instana:
connect: output: tcp: enabled: true sinks: # One or more sinks (destinations) instana: # Each sink has a unique name of your choice enabled: true hostname: <instana_host> port: <instana_port>
Here is the typical format of an HTTP output for Instana, with an HTTPS URL, corresponding SSL/TLS configuration parameters, compressed request bodies, and multiple records per request (batching):
connect: output: http: enabled: true endpoints: # One or more endpoints (destinations) instana: # Each endpoint has a unique name of your choice enabled: true url: https://<instana_endpoint> ssl: enabled: true protocol: TLSv1.2 enabled-protocols: TLSv1.2 key-store: <jks_file_path> key-store-type: JKS key-store-password: <password> trust-store: <jks_file_path> trust-store-type: JKS trust-store-password: <password> compression: true batching: enabled: true
These are typical examples only. For details of the specific configuration required for your environment, such as SSL/TLS, see the Instana documentation.