Known Issues for Protegrity Analytics

A list of known issues with their solution or workaround is provided here. The steps provided to resolve the known issues ensure that your product does not throw errors or crash.
  • Known Issue: Client side validation is missing on the Join an existing Audit Store Cluster page.

    Issue:

    Log in to the ESA Web UI and navigate to the Audit Store > Cluster Management > Overview page >Join Cluster. When you specify an invalid IP, enter a username or password more than the 36-character limit that is accepted on the Appliance, and click Join Cluster, then no errors are displayed and the request is processed.

    Observation:

    The Join an existing Audit Store Cluster page request is processed without any client-side validation, hence, an invalid IP address or a username or password more than 36 characters does not display any error.

  • Known Issue: High memory usage on the ESA.

    Issue:

    When using the Audit Store, the memory usage is high on the ESA.

    Workaround:

    Reduce the memory usage by updating the memory allocated to the Audit Store on the ESA to 4 GB using the Set Audit Store Repository Total Memory CLI option.

    For more information about the Set Audit Store Repository Total Memory CLI option, refer here.

  • Known Issue: In Analytics, on the Index Lifecycle Management page, after exporting, importing, or deleting an index one of the following scenarios occurs:

    • The index operation performed does not appear in the other operation lists. For example, an exported index does not appear in the import index list.
    • Performing the same operation on the same index again displays an error message.
    • If the index appears in another operation list, performing the operation displays an error message. For example, an exported index appears in the delete index list and deleting the index displays an error.

    Issue: After performing an operation, the index list for the export, import, and delete operations does not refresh automatically.

    Workaround: Refresh the Index Lifecycle Management page after performing an export, import, or delete operation.

Last modified January 30, 2025