pmlogger, pmproxy: archive "push" functionality #2214
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.
Extension to the pmlogger utility to allow remote PCP archive creation using a push mechanism, based on HTTP and a PMWEBAPI /logger API, instead of the traditional pmcd pull mechanism.
Archives can be pushed to a remote pmproxy server as they are being created by pmlogger, instead of (or as well as) written to local disk, using the -R/--remote option.
A pmlogpush(1) utility is added to perform this 'remote push' functionality for existing archives.
This commit includes libpcp_web improvements to its existing HTTP GET operation (incl. transition of existing PMDAs using this interface) and addition of a consistent POST operation, which is used by pmlogger and pmlogpush.
Resolves #2059