Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Introduction

If you want to profile the CoreOne Suite you can simply activate the appropriate tracing in the configuration. F

Step 1 - Make your infrastructure ready

You will need an Open Telementry Collector and a data visualization tool such as ELK-stack and APM.

Step 2 - Application configuration

Frontends

Each of the frontends has an application configuration files. In that file, you can add the following settings:

  "UseOpenTelemetry": true,
  "OpenTelemetryCollectorEndpoint": "https://otlp-gateway-prod-eu-west-2.grafana.net/otlp/v1/traces",
  "OpenTelemetryCollectorMetricsEndpoint": "https://otlp-gateway-prod-eu-west-2.grafana.net/otlp/v1/metrics",
  "OpenTelemetryCollectorHeaders": "Authorization=Basic NjkyODA0...2prd01EUTVPSDA9",
  "OpenTelemetryCollectorProtocol": "HttpProtobuf"

Simple enable OpenTelemetry and configure the appropriate endpoints, headers and the protocol.

Backend

For the backend, the settings are stored in the database.

update config_setting_value 
set int_value  = 0
where config_setting_code_id = 54;

update config_setting_value 
set string_value = 'http://localhost:4318/v1/traces'
where config_setting_code_id = 55;


update config_setting_value 
set string_value = ''
where config_setting_code_id = 56;

update config_setting_value 
set string_value = 'HttpProtobuf'
where config_setting_code_id = 57;

update config_setting_value 
set string_value = 'http://localhost:4318/v1/metrics'
where config_setting_code_id = 58;

Step 3 - Restart

After you have applied the settings, you will need to restart the appropriate parts.

  • No labels