Embedded OTel Collector Config #1314
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This change allows a user to list paths to their own Otel configs, these are then merged with the default Agent collector config. The last config specified takes priority over the rest if they have the same values declared.
To make debugging easier the merged OTel config which OTel is running with is outputted to
/var/lib/nginx-agent/opentelemetry-collector-agent-debug.yaml
To make modifying the NGINX Receiver and NGINX Plus Receiver easier if there is only one instance running thee instance ID is no longer needed be needed for the name. This will make modifying the
collection_interval
setting for example using your own OTel config easier as you no longer need the instanceIDwill now be
Checklist
Before creating a PR, run through this checklist and mark each as complete.
CONTRIBUTING
documentmake install-tools
and have attached any dependency changes to this pull requestREADME.md
)