Download page Use Auto-Instrumentation with an On-Premises Controller.
Use Auto-Instrumentation with an On-Premises Controller
The .NET Core and Node.js applications support certificates signed by a certificate authority (CA) only. The applications do not support self-signed certificates.If your Controller is using a self-signed certificate, then only auto-instrumentation for Java applications is supported.
To support auto-instrumentation with an on-premises Controller, configure the Cluster Agent customSSLSecret property to set the SSL certificates that the Cluster Agent uses to communicate with the on-premises Controller. See Configure the Cluster Agent to Use SSL for On-Premises Controllers. The Cluster Agent copies the certificates to the auto-instrumented pods where they are used by App Server Agents to establish connections with the on-premises Controller.
Configuration for Node.js and an On-Premises Controller
In addition to configuring the Cluster Agent customSSLSecret property, you must perform these steps for auto-instrumented Node.js applications that use an on-premises Controller.
Create a file named shim.js that sets the certificateFile property used by the Node.js Agent. See Node.js Settings Reference.
The Cluster Agent updates the Node.js workload spec which recreatesthe pods and copies the certificate file to the pods. The certificate file is referenced by the Node.js Agent through the NODE_OPTIONS environment variable and shim.js file.