You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ If you answered yes to one or more of these questions, then SuzieQ is a tool tha
17
17
18
18
SuzieQ does multiple things. It [collects](https://suzieq.readthedocs.io/en/latest/poller/) data from devices and systems across your network. It normalizes the data and then stores it in a vendor independent way. Then it allows analysis of that data. With the applications that we build on top of the framework we want to demonstrate a different and more systematic approach to thinking about networks. We want to show how useful it is to think of your network holistically.
19
19
20
-
**An enterprise version of SuzieQ is also available**. It has been deployed in production by multiple customers, and the company behind SuzieQ, (Stardust Systems)[https://stardustsystems.net] was named a "Cool Vendor" by Gartner for making network automation easy for enterprises.
20
+
**An enterprise version of SuzieQ is also available**. It has been deployed in production by multiple customers, and the company behind SuzieQ, [Stardust Systems](https://stardustsystems.net) was named a "Cool Vendor" by Gartner for making network automation easy for enterprises.
21
21
22
22
## Quick Start
23
23
@@ -42,7 +42,7 @@ To start collecting data for your network, create an inventory file to gather th
42
42
43
43
### Using Python Packaging
44
44
45
-
If you don't want to use docker container or cannot use a docker container, an alternative approach is to install SuzieQ as a python package. It is **strongly** recommended to install suzieq inside a virtual environment. If you already use a tool to create and manage virtual environments, you can skip the step of creating a virtual envirobment below.
45
+
If you don't want to use docker container or cannot use a docker container, an alternative approach is to install SuzieQ as a python package. It is **strongly** recommended to install suzieq inside a virtual environment. If you already use a tool to create and manage virtual environments, you can skip the step of creating a virtual environment below.
46
46
47
47
SuzieQ requires python version 3.7.1 at least, and has been tested with python versions 3.7 and 3.8. It has not been tested to work on Windows. Use Linux (recommended) or macOS. To create a virtual environment, in case you haven't got a tool to create one, type:
48
48
@@ -86,7 +86,7 @@ The CLI supports the same kind of analysis as the explore page. 
89
+
SuzieQ has the ability to show the path between two IP addresses, including the ability to show the path through EVPN overlay. You can use this to see each of the paths from a source to a destination and to see if you have anything asymmetrical in your paths. 
90
90
91
91
## Asserts
92
92
@@ -132,4 +132,4 @@ We've also been adding screencasts on [Youtube](https://www.youtube.com/results?
132
132
133
133
# SuzieQ Enterprise
134
134
135
-
SuzieQ also has a commercial offering, SuzieQ Enterprise. To know more about this and contact us, please visit the Stardust Systems (website)[https://stardustsystems.net].
135
+
SuzieQ also has a commercial offering, SuzieQ Enterprise. To know more about this and contact us, please visit the Stardust Systems [website](https://stardustsystems.net).
Copy file name to clipboardExpand all lines: docs/config_file.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,7 @@ coalescer:
53
53
| rest.logsize | maximum size of the REST logfile in bytes | 10000000 | no |
54
54
| rest.log-stdout | log everything on the standard output instead of a file | False | no |
55
55
| rest.no-https | if True, the REST server doesn't use SSL. Highly discouraged in production. | False | no |
56
+
| rest.cert-verify | if False the certificate will not be verified.<br>If True the certificate will be verified.<br>If a path, that will be checked as CA. | True | no |
56
57
| poller.logging-level | logging level for the poller.<br/> Choices: INFO, WARNING, ERROR | WARNING | no |
57
58
| poller.logfile | log file for poller | /tmp/sq-poller.log | no |
58
59
| poller.log-stdout | log on standard output instead of file | False | no |
Copy file name to clipboardExpand all lines: docs/release-notes.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,25 @@
1
1
# Release Notes
2
2
3
+
## 0.24.0 (May 7, 2025)
4
+
5
+
This release adds several new capabilities and important bug fixes. Notably, it includes more flexible filtering options, improvements to REST engine parameter handling, support for certificate verification settings, and new integrations with the VMWare's vCenter and Junos IPv6 neighbor discovery. These changes are backward-compatible.
6
+
7
+
***Filter devices by address**
8
+
You can now filter devices based on one or more IP addresses using the `address` argument in the CLI.
9
+
10
+
***Set certificate verification mode**
11
+
Added support for the `cert-verify` parameter in configuration. You can set it to `True`, `False`, or a path to a CA certificate. This controls whether and how certificates are verified when connecting over HTTPS.
12
+
13
+
***REST engine parameter update fix**
14
+
When switching to `engine='rest'`, the engine parameters (`rest-server-ip`, `rest-server-port`, `rest-api-key`, `rest-use-https`) are now correctly updated instead of keeping defaults. This avoids inconsistent behavior when switching between engines.
15
+
16
+
***Add VMWare's vCenter source for inventory**
17
+
Introduced support for `vcenter` as an inventory source. This enables automatic discovery of VMs and their IPs based on custom attributes. Configuration includes support for authentication and SSL settings.
18
+
Dependency added: `pyvnomi`.
19
+
20
+
***Collect IPv6 neighbor data on Junos**
21
+
Extended `arpnd` data collection to include IPv6 neighbors for Junos devices. This complements the existing IPv4 support and provides a more complete view of network neighbors on Junos platforms.
22
+
3
23
## 0.23.0 (May 27, 2024)
4
24
5
25
This has some useful features added, and a bunch of important bug fixes, most of them in the parsing logic, all of which are ports from the enterprise version. Some of these changes resulted in a few breaking changes, all to fix inconsistencies in parsing output. Fixing these inconsistencies should make writing logic using this info much simpler. Existing scripts that used this logic need to be fixed.
0 commit comments