Upgrade environment variable logic using new Pipeline API for logtail environment configuration management #1282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* add common param extractor * add input_file * add input_observer_network * add flusher_SLS * add global config module * improve pipeline def
yyuuttaaoo
approved these changes
Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit introduces an enhanced file discovery mechanism by transitioning from the old configuration API to the new Pipeline configuration API for ilogtail. With this upgrade, users will experience a change in the way recursive directory scanning is handled.
Previously, the recursive discovery of files within a directory was implied. However, to align with the new API's capabilities and to provide users with explicit control, the recursive behavior must now be explicitly specified in the path configuration.
To enable recursive file discovery within a directory, users should add
/**/at the point in the path where recursion is desired. This syntax will trigger a recursive scan with a maximum depth of 10 levels. If a non-recursive file discovery is required, users should use a single/in the path configuration.Example usage:
/var/log/myapp/**/app.log/var/log/myapp/app.logPlease note that if you rely on the recursive file discovery feature, you'll need to update your configuration to continue using this functionality with the new Pipeline API.