feat: monitoring for the vulnz cli (#230) #236
Merged
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.
1.) To better monitor the vulzn CLI, a scheduler has been implemented that writes metrics to the htdocs folder. These metrics can be read by a Prometheus system, for example. Metrics are only written if the vulzn CLI is also running. This feature is disabled by default and can be enabled via the ENV variable
METRICS_ENABLE=true
. This is used for better analysis of memory issues. The metrics can be accessed via HTTP at /metrics. This additional metrics file does not affect the OWASP dependency check. To achieve this, new dependencies had to be added to the project. Currently, only the standard JVM metrics are being written, but it can also be extended to include custom metrics.2.) As an additional improvement to track version changes based on the log, the banner was extended to include the version number.
3.) .gitattribute added for building the docker image under Windows OS, because of CRLF and LF problems
4.) readme.md Configuration extended with missing ENV vars.