...
If you want to profile the CoreOne Suite you can simply activate the appropriate tracing in the configuration. F
Table of Contents | ||
---|---|---|
|
Step 1 -
...
Prepare your OpenTelemetry infrastructure
...
You will need an Open Telementry Collector and a data visualization tool such as ELK-stack and APM.
Step 2 -
...
Configure OpenTelemetry in CoreOne
Frontends
Each of the frontends front-ends has an application configuration file in . I.e C:\ProgramData\itsense\Configuration
when installed as a Windows Services.
These are the files that matter:
Application Part | File |
---|---|
AuthCoreOne Authentication Services |
|
Selfservice CoreOne Self-Service Portal |
|
CoreOne Admin UIUser Interfaces |
|
Admin UI v2CoreOne Admin User Interfaces 2.0 |
|
...
Simply enable OpenTelemetry and configure the appropriate endpoints, headers and the protocol.
Please note that OpenTelemetryCollectorHeaders
contains how we authenticate to the telemetry system. This can be a Bearer Token, Basic Auth or an API key. It may also be empty if no authentication is needed.
...
...
In order for changed settings to take effect, the corresponding App Pool needs to be recycled! See https://itsense.atlassian.net/wiki/spaces/IKB/pages/2811527209/How-to+enable+application+tracing#Step-3---Restart
Backend
For the backend, the settings are stored in the database.
Code Block |
---|
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 for settings to take effect
After you have applied the settings, you will need to restart the corresponding parts:
...