Skip to content

Commit 333bbee

Browse files
committed
Updated release notes for 0.19.0
Signed-off-by: Dinesh Dutt <[email protected]>
1 parent 8b4533a commit 333bbee

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/release-notes.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,24 @@
11
# Release Notes
22

3+
## 0.19.0 (Aug 22, 2022)
4+
5+
The 19th release of SuzieQ contains bug fixes and improvements to key functionalities such as the REST API and endpoint tracker. Here's a detailed list of key features of this release:
6+
7+
* **Much improved Endpoint Tracker**: The endpoint tracker now displays endpoint movement accurately across all network OS. Its also faster. There are many other enhancements to endpoint tracking which we'll cover in a blog post separately.
8+
* **Vastly improved REST API performance**: Due to a bug in the code, the REST API handled only one request at a time. This has been fixed.
9+
* **EVPN VNI Assert Improved**: The EVPN VNI assert has been improved and cleaned up, and become faster too.
10+
* **Fix/improve VLAN filtering**: VLan filtering with interfaces such as ```interface show vlan="> 25"``` did not work correctly. This has been fixed, and coupled with support for in-between, allows for more powerful searching by VLAN
11+
* **In Between Semantics for Numeric Fields**: You can now use ">25 <50" to mean all numbers between 25 and 50 (not inclusive).
12+
* **Gather only connected routes for Junos MX**: Juniper MX devices have difficulty displaying the routing table (with JSON) in a short time when dealing with Internet size routing tables. This has led to some frustration on the part of users using SuzieQ to gather data from MX devices. For now, we only gather connected (or direct) routes on MXes to mitigate this problem. This is a **breaking change** if you're using SuzieQ with MX currently. Reach out over Slack if this is an issue for you, and we can tell you how to restore the old behavior for your specific setup.
13+
* **Netbox Multi-Tag Support**: We support the use of multiple tags (with complex OR/AND logic) to identify devices that SuzieQ should poll.
14+
* **Making string match consistent**: We use ! to signify not equal to. So, "!leaf01" means a string that's not equal to leaf01. When it came to regexp however, we used ~! to signify a not equal to of the regexp. To be consistent, we need to say !~. Now you can consistently use ! as in ifname="!Ethernet1/1" as well as ifname="!~Ether.*".
15+
* Poller Parser Fixes
16+
* **Handling router MAC in NXOS**: NXOS creates the same MAC addr/VLAN entry for both the SVI and the CPU. We didn't distinguish this case and so while we wrote both entries, the read displayed only one of them, and which of the two we did was unpredictable. This fix displays both entries with the flag "router".
17+
* Cumulus devices now recover from being dead
18+
* Updates to various libraries used, either because newer ones were available or due to security updates.
19+
20+
And many more bug fixes, new tests and test fixes.
21+
322
## 0.18.0 (June 21, 2022)
423

524
This 18th release of SuzieQ contains significant improvements to all the various NOS parsers, but especially IOSXE (more versions and more platforms supported now) and versions of NXOS older than 9.3.x. We've also added support for throttling the rate of requests SuzieQ poller issues to prevent overrunning AAA Servers. A more detailed list of features and critical bug fixes follows:

0 commit comments

Comments
 (0)