mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
2ad38df5cd
## Summary Reverting #179048 because it creates a false expectation that environment vars and config will be merged. This is true for the RUM agent. However, the NodeJS agent reads the environment vars and discards any provided config, leading to inconsistent behavior between both agents. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) |
||
|---|---|---|
| .. | ||
| src | ||
| index.ts | ||
| jest.config.js | ||
| kibana.jsonc | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
@kbn/apm-config-loader
Configuration loader for the APM instrumentation script.
This module is only meant to be used by the APM instrumentation script (src/apm.js)
to load the required configuration options from the kibana.yaml configuration file with
default values.
Why not just use @kbn-config?
@kbn/config is the recommended way to load and read the kibana configuration file,
however in the specific case of APM, we want to only need the minimal dependencies
before loading elastic-apm-node to avoid losing instrumentation on the already loaded modules.