fix: Update feature parsing for app checks and secure_light #22
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 `configuration.security=light` support into the config parser * Optimize the flow of configuration parsing for both Monitor and Secure * Re-work the layout of the `features.monitoring.app_checks` block to utilize `enabled` and `applications` fields. This is needed because the app checks are handled differently than the other configurations in the agent in that the `app_checks` key in the agent configuration does not have a nested `enabled` key, but instead leveraged a separate, top level parameter called `app_checks_enabled`.
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.
configuration.security=lightsupport into the config parserfeatures.monitoring.app_checksblock to utilizeenabledandapplicationsfields. This is needed because the app checks are handled differently than the other configurations in the agent in that theapp_checkskey in the agent configuration does not have a nestedenabledkey, but instead leveraged a separate, top level parameter calledapp_checks_enabled.