tencent cloud

Connecting to Apps Written in Other Languages
Download PDF
Last updated: 2025-10-13 19:10:50
Connecting to Apps Written in Other Languages
Last updated: 2025-10-13 19:10:50
Download PDF
Application Performance Management (APM) follows the OpenTelemetry protocol standard and theoretically supports applications written in all languages. Users can obtain integration schemes from the open-source community and report monitoring data to the APM server. Based on the Tencent Cloud console and TencentCloud API, they can achieve distributed tracing and Application Performance Management.

Steps

Selecting an Access Solution

For different programming languages and frameworks introduced in applications, obtain corresponding integration schemes from the OpenTelemetry open-source community. For details, refer to the OpenTelemetry community API & SDK list. Regarding different languages, integration schemes provided by the OpenTelemetry community may vary. Ensure the selected integration scheme is compatible with the programming language and framework versions.

Getting Access Point and Token

1. Log in to the TCOP console.
2. In the left sidebar, select Application Performance Management, and then click Application list > Access application.
3. In the Access application drawer frame that pops up on the right, click any language, and select the region and business system you want to integrate.
4. Select OpenTelemetry as Access protocol type.
5. Select a Reporting method you want, and obtain your Access point and Token.
Note:
Report over private network: This reporting method requires your service to run in the Tencent Cloud VPC. The direct connection through VPC can help avoid the security risks of public network communication and save costs on reporting traffic.
Report over public network: If your service is deployed locally or in non-Tencent Cloud VPC, you can report data in this method. However, it involves security risks in public network communication and incurs reporting traffic fees.

Modify Access Configuration

Based on the access solution obtained from the community, modify the following configuration.
Access point: In the OpenTelemetry access solution, the access point is usually expressed by the endpoint field, representing the reporting address provided by the APM server, to be replaced with the one you get from the console.
Application name: In the OpenTelemetry access solution, the application name is usually expressed by the service.name field. Multiple application processes connecting with the same application name are displayed as multiple instances under the same application in APM. The application name can be up to 63 characters long, can only contain lowercase letters, digits, and the separator "-", and must start with a lowercase letter and end with a digit or lowercase letter.
Token: Imported as attributes of Resource, with the corresponding key as token. To be replaced with the Token you get from the console.
Instance name: Imported as attributes of Resource, with the corresponding key as host.name. For each connected application instance, the instance name is a unique identifier. Typically, it can be set as the IP address of the application instance. Some access solutions can automatically obtain the IP address as the instance name. You can decide whether to manually fill in the instance name based on the actual situation.
For OpenTelemetry standard Resource, refer to resource introduction. Taking OpenTelemetry-Python automatic access scheme as an example, modify the startup script after access configuration as:
opentelemetry-instrument \\
--traces_exporter otlp_proto_grpc \\
--metrics_exporter none \\
--service_name myService \\
--resource_attributes token=myToken,host.name=192.168.0.10 \\
--exporter_otlp_endpoint https://pl-demo.ap-guangzhou.apm.tencentcs.com:4317/ \\
python3 app.py

Connecting Applications

Guidelines based on community open source solution for service access. For non-automatic access scheme and frameworks/components not covered by automatic connection scheme, additional modification of related business code may be needed to perform manual event tracking.

Access Verification

After starting the application, the connected application will be displayed in APM > Application List in normal traffic cases. Click Application name/ID to go to the application details page, then select Instance Analysis to view the connected application instance. Since there is latency in the processing of observable data, please wait about 30 seconds if the application or instance does not appear in the console after connecting.

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback