chore: added proper logging for config module

[aryamohanan]

No description provided.

[abhilash-sivan]

I could see a duplicate log:

{"level":20,"time":"2026-05-04T10:42:49.871Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
The App is using the following preload flags: --require ./instana-collector-5.4.1/src/immediate.js
{"level":30,"time":"Mon, 04 May 2026 10:42:49 GMT","pid":29873,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T10:42:49.872Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
{"level":30,"time":"2026-05-04T10:42:49.874Z","threadId":0,"name":"@instana/collector","msg":"PID Store starting with pid 29873"}

here [config] env:config.tracing.useOpentelemetry: true is logged twice. Please check

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[abhilash-sivan]

I have

I could see a duplicate log:

{"level":20,"time":"2026-05-04T10:42:49.871Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
The App is using the following preload flags: --require ./instana-collector-5.4.1/src/immediate.js
{"level":30,"time":"Mon, 04 May 2026 10:42:49 GMT","pid":29873,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T10:42:49.872Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
{"level":30,"time":"2026-05-04T10:42:49.874Z","threadId":0,"name":"@instana/collector","msg":"PID Store starting with pid 29873"}

here [config] env:config.tracing.useOpentelemetry: true is logged twice. Please check

I tested the same on main as well.

Currently, we don’t have logging for this in main, but I added a log and verified it locally. The log appears twice because the entry file invokes this twice, and the normalisation runs in both. That’s why the log is printed twice.

We should look into a more graceful way to handle this.

{"level":20,"time":"2026-05-04T15:06:05.250Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}
The App is using the following preload flags: noFlags
{"level":30,"time":"Mon, 04 May 2026 15:06:05 GMT","pid":32652,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T15:06:05.252Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}

[aryamohanan]

I have

I could see a duplicate log:

{"level":20,"time":"2026-05-04T10:42:49.871Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
The App is using the following preload flags: --require ./instana-collector-5.4.1/src/immediate.js
{"level":30,"time":"Mon, 04 May 2026 10:42:49 GMT","pid":29873,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T10:42:49.872Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
{"level":30,"time":"2026-05-04T10:42:49.874Z","threadId":0,"name":"@instana/collector","msg":"PID Store starting with pid 29873"}

here [config] env:config.tracing.useOpentelemetry: true is logged twice. Please check

I tested the same on main as well.

Currently, we don’t have logging for this in main, but I added a log and verified it locally. The log appears twice because the entry file invokes this twice, and the normalisation runs in both. That’s why the log is printed twice.

We should look into a more graceful way to handle this.

{"level":20,"time":"2026-05-04T15:06:05.250Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}
The App is using the following preload flags: noFlags
{"level":30,"time":"Mon, 04 May 2026 15:06:05 GMT","pid":32652,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T15:06:05.252Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}

I have

I could see a duplicate log:

{"level":20,"time":"2026-05-04T10:42:49.871Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
The App is using the following preload flags: --require ./instana-collector-5.4.1/src/immediate.js
{"level":30,"time":"Mon, 04 May 2026 10:42:49 GMT","pid":29873,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T10:42:49.872Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
{"level":30,"time":"2026-05-04T10:42:49.874Z","threadId":0,"name":"@instana/collector","msg":"PID Store starting with pid 29873"}

here [config] env:config.tracing.useOpentelemetry: true is logged twice. Please check

I tested the same on main as well.

Currently, we don’t have logging for this in main, but I added a log and verified it locally. The log appears twice because the entry file invokes this twice, and the normalisation runs in both. That’s why the log is printed twice.

We should look into a more graceful way to handle this.

{"level":20,"time":"2026-05-04T15:06:05.250Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}
The App is using the following preload flags: noFlags
{"level":30,"time":"Mon, 04 May 2026 15:06:05 GMT","pid":32652,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T15:06:05.252Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}

I have

I could see a duplicate log:

{"level":20,"time":"2026-05-04T10:42:49.871Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
The App is using the following preload flags: --require ./instana-collector-5.4.1/src/immediate.js
{"level":30,"time":"Mon, 04 May 2026 10:42:49 GMT","pid":29873,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T10:42:49.872Z","threadId":0,"name":"@instana/collector","msg":"[config] env:config.tracing.useOpentelemetry: true"}
{"level":30,"time":"2026-05-04T10:42:49.874Z","threadId":0,"name":"@instana/collector","msg":"PID Store starting with pid 29873"}

here [config] env:config.tracing.useOpentelemetry: true is logged twice. Please check

I tested the same on main as well.

Currently, we don’t have logging for this in main, but I added a log and verified it locally. The log appears twice because the entry file invokes this twice, and the normalisation runs in both. That’s why the log is printed twice.

We should look into a more graceful way to handle this.

{"level":20,"time":"2026-05-04T15:06:05.250Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}
The App is using the following preload flags: noFlags
{"level":30,"time":"Mon, 04 May 2026 15:06:05 GMT","pid":32652,"hostname":"Abhis-MacBook-Pro.local","msg":"Server is running on http://localhost:3000"}
{"level":20,"time":"2026-05-04T15:06:05.252Z","threadId":0,"name":"@instana/collector","msg":"INSTANA_DISABLE_USE_OPENTELEMETRY is set to "true", disabling OpenTelemetry integration."}

I think we can proceed with the current logging approach. Some configuration options in the main setup already result in duplicate logs—for example, INSTANA_TRACING_DISABLE=true. When debug mode is enabled, logs may appear twice.

This happens because coreConfig.normalize() is invoked twice during collector initialization. If any configuration value changes between those calls, it may be logged again as a separate update. This behavior is intentional for now and can be revisited later if necessary.

Overall, these configuration logs are quite required, especially when troubleshooting or diagnosing issues.