- Site Collector Features
- Site Collector Features Introduced in 2024
- Site Collectors 2.4 (November 2024)
- Site Collectors 2.3 (October 2024)
- Site Collectors 2.2 (September 2024)
- Site Collectors 2.1 (August 2024)
- Site Collectors 2.0 (July 2024)
- Site Collectors 1.20.0 (June 2024)
- Site Collectors 1.19.0 (May 2024)
- Site Collectors 1.18.0 (April 2024)
- Site Collectors 1.17.0 (March 2024)
- Site Collectors 1.16.0 (February 2024)
- Site Collectors 1.15.0 (January 2024)
- Site Collector Features Introduced in 2023
- Site Collectors 1.14.0 (November 2023)
- Site Collectors 1.13.0 (October 2023)
- Site Collectors 1.12.0 (September 2023)
- Site Collectors 1.11.0 (August 2023)
- Site Collectors 1.10.0 (July 2023)
- Site Collectors 1.9.4 (June 2023)
- Site Collectors 1.8.0 (May 2023)
- Site Collectors 1.7.0 (April 2023)
- Site Collectors 1.6.0 (March 2023)
- Site Collectors 1.5.0 (January 2023)
- Site Collector Features Introduced in 2022
- Site Collector Features Introduced in 2024
- Site Collector Known Issues
- Addressed Issues in Site Collector
- Site Collector 2.4: Addressed Issues
- Site Collector 2.3: Addressed Issues
- Site Collector 2.2: Addressed Issues
- Site Collector 2.1: Addressed Issues
- Site Collector 2.0: Addressed Issues
- Site Collector 1.20: Addressed Issues
- Site Collector 1.19: Addressed Issues
- Site Collector 1.18: Addressed Issues
- Site Collector 1.17: Addressed Issues
- Site Collector 1.16: Addressed Issues
- Site Collector 1.15: Addressed Issues
- Site Collector 1.14: Addressed Issues
- Site Collector 1.13: Issues Addressed in October 2023
- Site Collector 1.11: Issues Addressed in August 2023
- Site Collector 1.9.4: Issues Addressed in June 2023
- Site Collector 1.8: Issues Addressed in May 2023
- Site Collector 1.6: Issues Addressed in March 2023
- Site Collector 1.5: Issues Addressed in January 2023
- Site Collector Issues Addressed in December 2022
- Vulnerability Remediation Policy
Site Collector Known Issues
Issue ID | Description |
---|---|
NGSCL-1517 | Site Collector installation fails on RHEL 9 because of lack of network support for TLS v1.3 more secured ciphers, without a clear warning. |
NGSCL-1558 | A Site Collector instance occasionally produces an |
NGSCL-2447 | The search filters on the Site Collectors Overview page are case sensitive. Currently, search results are not displayed if you do not match the case with the collector instance name for the key words that you use for searching for collector instances. |
NGSCL-2569 | While editing a Site Collector instance, in Advanced Settings, the Timezone field after initial configuration displays the first city name of the time zone such as UTC/PST on the user interface instead of the exact city name which you selected. |
NGSCL-3674 | While upgrading a Site Collector instance to its latest version, the Windows Event Log agent collector pulls duplicate logs when historic log fetch is enabled. |
NGSCL-3961 | After upgrading a Site Collector instance from version 1.x to 2.x, the server side collectors Splunk, Oracle, MySQL, MSSQL, QRadar, and EStreamer start to fetch historical data based on an old start fetch timestamp. Workaround – If you are using Site Collector version 1.x with the server side collectors installed, and want to upgrade to 2.x version, ensure that you update the Start Fetch Date for the Splunk collector and Iterator column initial value for Oracle, MSSQL, and MySQL collectors to the current time or to the value based on the iterator you defined. Alternatively, you can choose to wait to upgrade the Site Collector instance from 1.x to 2.x version until this issue is fixed. |