Skip to content

Releases: xtuml/munin

1.4.0: Merge pull request #235 from xtuml/1_4_0_release

24 Jun 20:05
79d0ecd
Compare
Choose a tag to compare

This release carries new functionality around Logging and Reporting.

Release notes are found here: https://github.com/xtuml/munin/blob/main/doc/notes/munin1.4.0.adoc

testing CI after domain removal

21 May 17:51
8bd4168
Compare
Choose a tag to compare
Pre-release

This is a pre-release to test the CI after AsyncLogger and AEReception have been removed.

logging and reporting

23 Apr 15:41
46c88b2
Compare
Choose a tag to compare
logging and reporting Pre-release
Pre-release

This revision makes changes to logging and reporting as well as architectural changes
in the logging and inter-process communication technologies. 'log4cplus' is now the
fundamental logging technology. This brings a great deal of configurability with directing
logging data to appenders of different types including rolling file appenders and Kafka
appenders.
The benchmarking probe is implemented as a (configurable) logger now. This lets us
turn it on and off as needed.
A back end 'dashboard' application is prototyped (metrics/pvstats.py).

Here is a list of changes in the usage:

  • The reception kafka topic is now called: Protocol_Verifier_Reception
  • JSON messages written to Protocol_Verifier_Reception no longer need to be prepended with a length. Compliant JSON is now received.
  • The logging folder hierarchy has been changed and documented in the 188 implementation note.
  • There are 2 new topics to which the Protocol Verifier publishes reporting information.
    • 'Protocol_Verifier_InfoWarn' carries the status of jobs. Job failures are reported as Warnings; job successes are logged as Information. Other errors and failures are reported on this topic. (This was formerly the Verifier.log.) In file-based mode, this information will go to pv.log.
    • 'Protocol_Verifier_Statistics' carries PV statistical information generated by Job Management. A key statistic here is the total number of assigned jobs. In file-based mode, this information will go to pv_jm.log.
  • The Benchmarking Probe is now configured as a logger. The contents of the messages are JSON. Only aeordering_event_processed and svdc_*_processed are posted to this topic. It is disabled by default. To enable it:
    • set the pv.benchmark logger to INFO.
    • See benchmark.py for an example of interrogating the probe data.
    • The messages are JSON.
  • The docker-compose files now refer to separate log-config files, one for file-based logging and the other for kafka-based logging.

Munin Phase 2 Stage 4

15 Mar 17:43
d1423ce
Compare
Choose a tag to compare

Munin Phase 2 Stage 3

14 Dec 18:46
5b64691
Compare
Choose a tag to compare

v1.1.1

06 Oct 15:20
9edc7dc
Compare
Choose a tag to compare
v1.1.1 Pre-release
Pre-release
Bump version to 1.1.1

Munin Phase 2 Stage 2

22 Sep 18:32
9165442
Compare
Choose a tag to compare

v1.1.0-beta1

18 Jul 19:23
4d42360
Compare
Choose a tag to compare
v1.1.0-beta1 Pre-release
Pre-release

Initial prototyping of inter-domain messaging with Kafka

Munin Phase 2 Stage 1

22 Jun 14:20
038e8b6
Compare
Choose a tag to compare
v1.0.0

Merge pull request #92 from xtuml/MUN_1_110_add_default_job_specific_…

Munin Phase 2 Stage 1 (midstage)

18 May 16:35
1d05ed9
Compare
Choose a tag to compare