litespeed: add support for different .rtreport format #7705
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
Manage this branch in SquashTest this branch here: https://lucasrolffmodify-litespeed-par-6ww6n.squash.io |
|
|
ilyam8
changed the title
ilyam8
approved these changes
Jan 10, 2020
|
@lucasRolff thanks! |
Ferroin
approved these changes
Jan 10, 2020
Saruspete
pushed a commit
to Saruspete/netdata
that referenced
this pull request
May 21, 2020
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.
Summary
Add support for different .rtreport format
Some .rtreport files do not contain
MAXCONNandMAXSSL_CONNvariables, but simply list the in use connections.This PR adds support for this by looking for lines starting with
PLAINCONN:as well.Component Name
python.d litespeed
Additional Information
I'm ops @ LiteSpeed Technologies