이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.
This check monitors IBM i
remotely through the Datadog Agent.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates
for guidance on applying these instructions.
The IBM i check is included in the Datadog Agent
No additional installation is needed on your server.
The IBM i check uses the IBM i ODBC driver to connect remotely to the IBM i host.
Download the driver from the IBM i Access - Client Solutions
page. Click on Downloads for IBM i Access Client Solutions and login to gain access to the downloads page.
Choose the ACS App Pkg package for your platform, such as ACS Linux App Pkg for Linux hosts. Download the package and follow the installation instructions to install the driver.
The IBM i check queries an IBM i system remotely from a host running the Datadog Agent. To communicate with the IBM i system, you need to set up the IBM i ODBC driver on the host running the Datadog Agent.
Once the ODBC driver is installed, find the ODBC configuration files: odbc.ini and odbcinst.ini. The location may vary depending on your system. On Linux they may be located in the /etc directory or in the /etc/unixODBC directory.
Copy these configuration files to the embedded Agent environment, such as /opt/datadog-agent/embedded/etc/ on Linux hosts.
The odbcinst.ini file defines the available ODBC drivers for the Agent. Each section defines one driver. For instance, the following section defines a driver named IBM i Access ODBC Driver 64-bit:
[IBM i Access ODBC Driver 64-bit]
Description=IBM i Access for Linux 64-bit ODBC Driver
The name of the IBM i ODBC driver is needed to configure the IBM i check.
IBM i check
Edit the ibm_i.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your IBM i performance data. See the sample ibm_i.d/conf.yaml
for all available configuration options.
Use the driver name from the obdcinst.ini file.