Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt

Released on July 29thAugust 4th, 2016.

New Features

  • Help widgets and tools for building your own dashboardsThe "Reset Dashboard" New Additions to the Dashboard Toolbox: We’ve expanded the dashboard toolbox with some new features and widgets:
    • Reset Dashboard – this widget can be placed anywhere on a dashboard and allows you to reset any search filters
    Struggling to test
    • Browser Detection - this makes light work of testing your dashboard with different web browsers
    , such as Internet Explorer 10 in Compatibility mode? The "Browser Detection" custom widget will make your life easier...Catch clicks on
    • Click Capture – capture the clicks on your timeline and word-cloud widgets and handle them
    with
    • in your own
    custom
    • JavaScript code
    Ability to switch query for
    • Query Edit - Change the query behind a widget on the fly
    Expose widget
    • Widget Property Page Visibility - the property pages
    in the APIGreater performance when loading data -
    • of widgets are now exposed via the custom widget API so you modify them programmatically 
    • Modifier Key Handling - We reintroduced this to Facet Tables give you more control in your code
  • Data Loading Performance: Expect more when loading data – you can now split the search index to allow separate indices for reading and writing.


Improvements

  • UI
    • Reintroduce modifier key handling for Facet Table
    • Implement v2 of type ahead design
    • Typeahead return more data
  • Search
    • Allow Indexing Performance Tuning by explicitly allowing fields to be analysed
    • Limit Elasticsearch query time
    • Cannot create Project with custom index is ES cluster state is yellow
    • Adjust elasticsearch pkg to use the default elasticsearch user
  • Backend
    • Add missing _internal/status resource to cluster service
    • Report Status of SQL and Redis Followers
    • Improve resilience of mysql migration scripts
    • Add monitoring and self-repair for broken mysql replication
    • Autodetection and self-healing for duplicate mysqld instances

Bug Fixes

  • Type Ahead Update: The search type-ahead suggestions are now cleaner and easier to read and indicate how many results match each suggestion
  • Indexing Performance Tuning: Explicitly identify which fields you want to analyse for type-ahead, alphabetical sorting and searchability
  • Operator Override: you can create new projects while the Elasticsearch cluster is in 'yellow' state (if you explicitly enable this behaviour in the Squirro configuration). With great power comes great responsibility...
  • Elasticsearch Default: Squirro now defaults to use the 'elasticsearch' user to run Elasticsearch instead of the 'elastic' user. This conforms to the 'norm' when working with Elasticsearch
  • Cluster Transparency: the cluster service now provides the _internal/status resource allowing you to query its state and we added the status of MySQL and Redis so it’s easier to get an overview of the cluster state.
  • Migration Resilience: We improved the MySQL cluster node migration process to make it more resilient to specific error conditions.
  • Self-Repair MySQL: We also added monitoring and self-repair in case MySQL replication breaks or the MySQL process stops


Bug Fixes

  • Fixed: Sort gets reversed when editing bookmarks, after query #13, on IE11
  • Fixed: IE11/IE10 CompatCompatability: Focus is not released from search bar
  • Fixed: Custom Facet Table headers lose sorting indicators
 

Fresh Installation Instructions

Please follow the regular installation steps.

Upgrade Instructions

Warning

To upgrade to version 2.4.3 of Squirro, please ensure that your current version is at least version 2.3.2 or higher. This is because this version contains a new major version of ElasticSearch. If you are on a version older than 2.3.2, please contact support.

Note

Additionally if you are using Squirro in a Box, additional steps are involved. In this case we also ask you to contact support.

From versions 2.4.x, 2.3.2 or 2.3.3

1. Upgrade Storage Nodes and Cluster Nodes collocated on the same machine/VM

Code Block
languagebash
[squirro@singlenode ~] sudo yum update squirro-storage-node-users
[squirro@singlenode ~] sudo yum update squirro-cluster-node-users
[squirro@singlenode ~] sudo service elasticsearch stop
[squirro@singlenode ~] sudo yum downgrade elasticsearch
[squirro@singlenode ~] sudo yum update squirro-storage-node
[squirro@singlenode ~] sudo yum update

2. Upgrade Storage Nodes (separate from Cluster Nodes)

Upgrade all storage nodes one at a time by running:

Code Block
languagebash
[squirro@storagenode01 ~] sudo yum update squirro-storage-node-users
[squirro@storagenode01 ~] sudo service elasticsearch stop
[squirro@storagenode01 ~] sudo yum downgrade elasticsearch
[squirro@storagenode01 ~] sudo yum update

3. Upgrade Cluster Nodes (separate from Storage Nodes)

Code Block
languagebash
[squirro@clusternode01 ~] sudo yum update squirro-cluster-node-users
[squirro@clusternode01 ~] sudo yum update