Skip to content

Releases: Comcast/connvitals

py4.3.2

30 Aug 16:27
Compare
Choose a tag to compare

Fixes #7 by offering true IPv6 support.

py4.3.1

13 Aug 14:21
Compare
Choose a tag to compare

This patch provides the ability to ping sequentially, rather than in threads. Sacrifices a small amount of accuracy for scaling performance gains.

py4.3.0

07 Aug 14:34
Compare
Choose a tag to compare

This Python release exposes a new API (without deprecating the old one) that uses context-manageable objects for each collection task. It's now possible to do e.g. with ping.Pinger(*args) as pinger:.... This allows things like connvitals-monitor to easily re-use sockets for long-lived tasks.

py4.2.0

31 Jul 15:16
Compare
Choose a tag to compare

Changes the API of collectors in what shouldn't be a breaking way - introduced the config.Config class which can optionally be passed to a collector.Collector initializer to set configuration on a per-host basis. By default, the initializer uses the global configuration, which is now contained in config.CONFIG rather than just at the config module level.

py4.1.0

16 Jul 15:46
Compare
Choose a tag to compare

This release addresses some issues with the command line and plaintext output.
It also now adds identifying information to traceroute packets to avoid collisions with other hostnames/ips that resolve to the same machine.

py4.0.2

11 Jul 17:21
Compare
Choose a tag to compare

Bugfix release, closes issues #1, #2, and #3.

Open Source Python Release

30 May 17:13
Compare
Choose a tag to compare

It might be confusing that connvitals's version history starts at 4.0.1, but that's because this was developed at Comcast for several months before being approved as an open-source project.

Open Source Go Release

30 May 17:25
Compare
Choose a tag to compare

connvitals's golang branch starts at version 3.0.0. Prior to this release, connvitals was developed as an internal tool at Comcast, and has now been approved for open-source release.

Note that the versions of connvitals written in Python and Go need not (and rarely - if ever - will) match, but should still be considered to be at feature parity with one another