Fix bug not finding latest checkpoint file

Full Changelog: v0.10.5...v0.10.6

See bug #107

More configurable p4 monitor parsing, update SSL certs

Full Changelog: v0.10.4...v0.10.5

• New metrics:

  • p4_monitor_cmds - P4 running (not I/B) processes count grouped by command patterns
  • p4_monitor_cmds_max_runtime - P4 running (not I/B) processes max runtime (seconds) grouped by command patterns
  • p4_monitor_cmds_runtime - P4 running (not I/B) processes total runtime (seconds) grouped by command patterns

• Upgrade to use new version of parsing library v0.14.4 #105

• Add default max repetitions for p4metrics with --dry.run and --debug combo specified #104

• Update saved data from p4 info

Fix issues with not collecting replica pull metrics

1. Ensure metric p4_pull_replication_error is written if pull fails
2. Produce pull metrics for non-SDP replicas

Fix problem with not collecting realtime (rtv.*) metrics

Change only for p4metrics - no other binaries affected.

Don't rotate log/journal if --dry.run specified

• Don't rotate log/journal if --dry.run specified
• Update the p4metrics.yaml config file with new log/journal attributes if necessary
• Only changes to p4metrics

Fix parsing of configure show values

Change for p4metrics - no change for other utilities.

p4metrics will rotate journal and logs if necessary

New features:

• p4metrics will rotate journal and logs if necessary
• new metrics:

• p4_journals_rotated and p4_logs_rotated
• p4_journal_size, p4_log_size, p4_logs_file_count

• Create a -C/--sample.config parameter for p4metrics

The sample config has new options (which all default to blank or zero, unless you run the install_p4prom.sh):

# ----------------------
# max_journal_size: Maximum size of journal file to monitor, e.g. 10G, 0 means no limit
# Units are K/M/G/T/P (powers of 1024), e.g. 10M, 1.5G etc
# If the journal file is larger than this value it will be rotated using: p4 admin journal
# This is useful to avoid sudden large journal growth causing disk space issues (often a sign of automation problems).
# Note that this is only actioned if the p4d server is a "standard" or "commit-server" (so no replicas or edge servers).
# The system will only rotate the journal if the user is a super user and the journalPrefix volume has sufficient free space.
# Leave blank or set to 0 to disable (see max_journal_percent below for alternative).
max_journal_size:

# ----------------------
# max_journal_percent: Maximum size of journal as percentage of total P4LOGS disk space, e.g. 40, 0 means no limit
# Values are integers 0-99
# Volume information is read using: p4 diskspace
# If the journal file is larger than this percentage value it will be rotated using: p4 admin journal
# This is useful to avoid sudden large journal growth causing disk space issues (often a sign of automation problems).
# Note that this is only actioned if the p4d server is a "standard" or "commit-server" (so no replicas or edge servers).
# The system will only rotate the journal if the journalPrefix volume has sufficient free space.
# Leave blank or set to 0 to disable (see max_journal_size above for alternative).
max_journal_percent: 	30

# ----------------------
# max_log_size: Maximum size of P4LOG file to monitor - similar to max_journal_size above
# Units are K/M/G/T/P (powers of 1024), e.g. 10M, 1.5G etc
# If the log file is larger than this value it will be rotated and compressed (using rename + gzip)
max_log_size:

# ----------------------
# max_log_percent: Maximum size of log as percentage of total P4LOGS disk space, e.g. 40, 0 means no limit
# Values are integers 0-99
# Volume information is read using: p4 diskspace
# If the log file is larger than this percentage value it will be rotated and compressed (using rename + gzip)
max_log_percent: 		30

ALPHA!! Release of p4logtail and p4plogtail only

Partial binary release only.
New additional utilities to parse p4d and p4p logs and produce JSON output - in realtime, tailing logs.

This DOES NOT INCLUDE (OR REPLACE!) p4prometheus and other binaries... - see previous (Release v0.9.8) to download latest of those!

Make p4metrics not stop when there are p4d server errors

Fix issue #87
Tweak non-SDP installer for monitor_locks systemd timer
No changes to p4prometheus

Add swarm_url config option for p4metrics

Useful when the URL to use on the server is not the same as in p4 property for users - e.g. when VPN is in use