Notifications

179 views

Description

Increasing the Max Length of the sa_discovery_log.log and sa_discovery_log_history.log fields in the Dictionary does not resolve the "Discovery log is too large and could not be saved" Horizontal Discovery Pattern Log error. The limit remains as 4096000 bytes. For some devices, such as large Switches, Routers or Load Balancers, that limit is not big enough.

The Discovery Log in the Discovery Status will show an error like:

Failed Exploring CI Pattern, Pattern name: <Pattern>, To Check Pattern Log Press Here
Discovery log is too large and could not be saved. Log length: <actual size>, Max length: 4096000."

Steps to Reproduce

  1. Discovery something using the "Netscaler Load Balancer SSH" pattern for example.
  2. Increase the max length of the sa_discovery_log.log  and sa_discovery_log_history.log fields in the Dictionary.
  3. Rediscover, and the error remains the same.  The back-end java class responsible for the error message does not honor the length specified in the dictionary.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

The fix allow increasing the Max Length in the Dictionary to work, but does not do that for you. Customers will still need to modify the Dictionary if these fields need increasing to handle >4MB Pattern logs.

These fields can handle up to 16M while still keeping the same mysql medium text data type and so no actual database change is required when doing this.

  1. As an admin user, Open System Definition -> Dictionary
  2. Filter the list for Table is sa_discovery_log OR sa_discovery_log_history, AND column name is log
  3. Personalize the list layout to include the Max Length column
  4. Set the value of the 2 fields to Max Length = 16777215 


Related Problem: PRB1341094

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Qradar SIEM Integration - Madrid 2019 Q1
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response Flow Designer Content - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Fixed In

Madrid Patch 9
New York Patch 3
Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-06-30 03:54:08
Published:2020-05-25