Skip to main content

Cogynt v2.16 Release Notes

· 8 min read

Cogility is delighted to announce that Cogynt version 2.16 is generally available for AWS customers as of December 2024. Please see what's new below.

For more information, or to have your Cogynt instance updated, please contact us.

DevOps​

  • When bootstrapping a Kubernetes cluster, the Cogynt Delivery Tool is now able to read from custom repositories in addition to ECR's image repository, which provides customers with greater flexibility.

  • Delivery Tool installations of Cogynt are now event based, and do not proceed to the next step until the current step is successful, creating a more reliable delivery process.

  • Cogynt can now deploy with multiple load balancers, which increases the flexibility of which applications will be exposed to a given network.

  • The Flink Kubernetes Operator has been upgraded to v1.10, which stabilizes autoscaling behavior.

  • Flink v1.20 Upgrade.

Authoring​

UI Updates​

  • The overlays for the Schema, Event Type, and Lexicons tables have been replaced with new modals.

  • The tables are now customized to show relevant information for the object, so users can find the object they want more efficiently without having to open the object.

  • Users can now filter by properties of Event Types within the Event Type modal, such as topic name, stream properties, lexicons and more, to help users better narrow their search for specific Event Types within a project.

  • New workflows for creation of Schemas, Event Types, and Lexicons.

  • Schema Discovery is removed from the project as a stand-alone feature, and replaced with the ability to extract schema from Kafka topics within the new Schema creation workflow, to make for a more streamlined Schema creation experience.

  • New and improved lexicon tree layout, lending itself to be a more lightweight experience when creating and exploring lexicons.

Partial Import​

  • Users can now selectively import components (and their dependencies) by type when importing from the component modal view.

Deployment Issues View​

  • Users are now able to see any deployment issues that have occurred in their running deployments via the UI.

  • When an issue / error is encountered, the deployment table's new “Issues” column provides a warning with a total issue count.

  • Clicking the Issues column brings up a dialogue with a list of errors or warnings that have been encountered within the deployment, so that the user does not have to open the Flink dashboard to look for error logs.

Improved Computations User Experience​

  • A loading wheel no longer appears between each action taken within the computation screen, making it much more streamlined for users while modeling in the computations screen.

  • Intermittent changes to the computations screen saved, so that work that has been drafted but not completed is not lost when navigating away from the computation screen.

HCEP​

Performance Optimizations​

  • Users should experience performance improvements, especially in high volume joins between IPs.

JDBC support for Lexicon Filters​

  • Users can now use lexicon filters on their database fields.

Workstation​

Events Explorer UX Enhancements​

  • Users may now drag an entire row on the Events Explorer widget to another widget. The previous "drag" icon that appeared on the left of each row has been removed.

  • An Actions menu has been added to each row, allowing users to send the row to a Object Details Viewer widget, open a new ODV widget, or perform manual actions.

  • A View button has been added to each event row. Clicking the view button behaves differently depending on how many ODV widgets are on the current workspace:

    • If there are no ODV widgets: Clicking the button opens a new ODV widget and sends the event row to it.
    • If there is exactly 1 ODV widget: Clicking the button sends the row to the single ODV.
    • If there is > 1 ODV widget, Clicking the button opens a menu that allows the user to decide which ODV to send the event to.

Events Explorer Filtering UX Changes​

  • A new filtering menu has been added to the Events Explorer widget. This can be used instead of the Search Facets filtering drawer now to filter your Events table.

Object Details Viewer​

  • Viewing an object has received a UX revamp that introduces a persistent header so that you always know which collection you are working on regardless of which tab you are working on. Objects include:

    • Collections
    • Events
    • Notifications

  • You may clear an object from the ODV by now clicking the "X" button.

Collections​

  • Collections now can be edited quickly by clicking the field to update rather than going into a dedicated "Edit" mode for the entire collection.

Custom Fields​

  • A new Multichip custom field has been added for better viewing and editing experience for scenarios in which there are many options users can pick from. Checkbox custom fields can be safely converted to Multichip and vice versa.

  • Descriptions can now be added for any Custom Field template, which appear on an Info tooltip on a collection.

Report Builder​

  • The Advanced Report builder's HTML helper has been augmented to force UTF8 encoding to better support the export of content that is copied and pasted into Custom Fields.

Other​

  • Fixed a bug in which the Event Detail Templates would periodically reset your work while building a template.

  • The current user now appears at the top of the list of users in areas where a user can be assigned to an item (collections and notifications).

  • Copying comments over to a rich text editor field no longer includes a dark background color.

Audit Viewer​

No noteworthy changes.

User Management​

  • A new API Key screen has been added, available only for super_admin users to create and manage API keys for external applications.

Known Issues​

Authoring​

  • Working in computations with multiple users may cause loss of progress due to users overwriting each other's work while in the same screen. As a workaround, limit teams to one active user of computations at a time.
  • Schema Discovery does not recognize JSON objects.
  • Authoring sometimes crashes when entering a \ character in the search bar of the project landing page.
  • Authoring crashes occasionally when adding a new outcome to a pattern. No data loss occurs in this instance. Refresh the page and resume work as normal.
  • Deployment artifacts (temporary jar files) can potentially fill up disk space and cause deployments to fail. As a workaround, occasionally clear the disk's temp folder. (There is a 3-day auto cleanup policy in place, but the rate of disk filling is dependent on the frequency of deployment.)
  • The right-click menu does not stay open on Windows machines. As a workaround, the same right-click menu options are also available on inspect panel and toolbars. Use those instead.

Data Management Tool​

  • S3 connectors currently fail to read files in JSON array file format. As a workaround, convert files to newline format wherever possible.
  • S3 connectors fail to read files in TSV format.

Workstation​

  • Event Data fields that possess the same name and type but a different path are not able to be filtered in the Events Explorer table. The only workaround today is to ensure event data fields with the same name and type have the same path, which requires deleting the events in Workstation and a redeploy of the models to force the schema change to be reflected.
  • When idle, the Workstation UI may display an error page. Refresh the page to solve the issue.
  • Performing a filter on an event for multiple data fields sharing the same field name but different paths fails to correctly return results. As a workaround, a modeler has to unify the paths for similar field names and redeploy. Dev delete may be required in Workstation so that Opensearch reindexes messages from schema change.
  • Workstation will not ingest events that have multiple data fields that are geo arrays.
  • The sort logic for Ascending and Descending order for the "Tag" option in the Notifications Explorer widget is inverted.
  • Sorting by Assignee on collections sorts users by ID rather than name.
  • In some circumstances, a retracted pattern solution on the Drilldown widget may change color between blue and gray. Retracted pattern solutions are intended to always be gray.