DocumentaciónHelp

Instrument on IBM i and legacy systems

How to bring IBM i Java applications into APM, what's possible with RPG, COBOL and CL, and the guide for systems that can't be modified.

On this page

APM also receives data from IBM i (AS/400) and older systems. The guides are in Settings → APM → API key and SDK, section SDK by language and other ways to send, Legacy and IBM i tab.

Before you start

IBM i · Java

Java applications on IBM i (IBM Technology for Java or OpenJ9, Java 8 or later) use the same official agent. Queries to DB2 for i over JDBC (JTOpen/jt400) appear as database dependencies.

  1. Copy the agent to the IFS, for example with scp or from QSH:

mkdir -p /QOpenSys/opt/otel
curl -L -o /QOpenSys/opt/otel/opentelemetry-javaagent.jar \
  https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar
  1. Start the JVM with the agent (in QSH or in the job that starts it). The parameters are the usual ones, as Java properties:

java -javaagent:/QOpenSys/opt/otel/opentelemetry-javaagent.jar \
  -Dotel.service.name=mi-servicio \
  -Dotel.exporter.otlp.endpoint=https://URL_DE_INGESTA \
  -Dotel.exporter.otlp.protocol=http/protobuf \
  -Dotel.exporter.otlp.headers=Authorization=Bearer%20jtk_TU_TOKEN_DE_SERVIDOR \
  -Dotel.resource.attributes=deployment.environment.name=produccion,host.name=AS400PRD \
  -jar app.jar
  1. If IBM i has no internet access, point to the Collector on your network, for example -Dotel.exporter.otlp.endpoint=http://collector.interno:4318.

IBM i · RPG, COBOL and CL

RPG, COBOL and CL have no runtime that OpenTelemetry can instrument on its own. The guide suggests, from most to least detail:

  1. Instrument their callers: the Java, Node or Python API that uses DB2 over JDBC or ODBC, or that calls programs with JTOpen.

  2. Instrument the Linux bridge server that publishes the website or API in front of IBM i (see the next section).

  3. Send spans manually from RPG or COBOL with embedded SQL, using the QSYS2 HTTP functions (IBM i 7.4 TR5 or 7.3 TR11 and later). The guide includes the full example with QSYS2.HTTP_POST to the ingest URL.

  4. Send IBM i logs (syslog, QHST or exported spool) with a Collector on a bridge server. The guide includes the Collector configuration.

Systems that can't be modified

The No code changes tab includes a guide for OBI (OpenTelemetry eBPF Instrumentation), a tool from the OpenTelemetry project installed separately, in a container, on a Linux server (kernel 5.8 or later with BTF, or RHEL 8). It observes the HTTP, gRPC and SQL requests of any process, including third-party binaries, and sends traces to ARGUNIS with your token.

OBI needs kernel privileges: use it only with authorization and in a separate container. It's still a 0.x version, so pin a specific version in production. ARGUNIS doesn't yet have its own agent that instruments without code changes; this guide uses the OpenTelemetry tool.

What happens next

Each program or service appears in APM → Services with the name you gave it. If you used host.name, ARGUNIS links it to that inventory server when it exists.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close