Metric Insights 6.1.0 is the General Availability release for our 6.x architecture.
The 6.x versions of Metric Insights represent a new era of modern container-based deployment (allowing for horizontal scaling) and support for significantly larger Datasets via Microsoft SQL Server (the metadata/application DB will remain in MySQL/MariaDB), and the introduction of the Data Processor and Remote Data Processor services (deployed as containers).
6.1.0 introduces improved column change management for Datesets, and several new features to assist with multi-tenant enterprise scale deployments (new privileges, new options for content migration). We're excited to welcome you into this new era.
- Docker-based deployment (originally introduced in 6.0)
- Container orchestration (including templates for Kubernetes and Amazon ECS)
- Rearchitected Data Processor (originally introduced in 6.0) and Remote Data Processor (replacing the Remote Data Collector)
- High-volume data loading via MS SQL Server Agent
- Smarter Dataset column management
- Easier scripted content migration
- New Power User Privileges and Permissions for JS and Email Templates
1. Docker: Deployment & Orchestration
The 6.x architecture is built from the ground up to be deployed in Docker with container orchestration. 6.1.0 ships with configurations for Kubernetes and ECS.
For help configuring your infrastructure-as-code tooling (e.g. Terraform, CloudFormation), contact email@example.com
1.1. Container Orchestration Options
1.2. Other Deployment Options
Network File Systems (NFS) are now a requirement for permanent storage in the 6.x architecture. In 6.1.0, we ship with configurations for the Kubernetes-focused Portworx storage and data management tool as an additional option.
2. High-Volume Data Loading
Larger Datasets with volumes in the tens of millions of rows (depending on the number of columns and the performance of your database instance/cluster) are supported via Microsoft SQL Server as of 6.0—in 6.1.0, we've introduced two methods of loading CSV data, either via a Shared Mount on the server, or an agent, for performant data loading into the SQL Server database.
2. On Data Storage Editor select “Shared Folder” and fill path for folder on MSSQL Server and path to folder in Data Processor - http://img.mtrc.in/91deaa0595e6 . Sample - https://stg60.metricinsights.com/admin/storage/edit/str/25
The agent must be deployed in the SQL Server environment in order to load large volumes of data. This means you will need SQL Server on a virtual or a baremetal machine where the agent can be deployed.
Please contact firstname.lastname@example.org if you plan to load high volumes of data into SQL Server and we can assist in the process.
3. Smarter Dataset Column Management
If a column is not being used in a Dataset, it can now be removed without causing any downstream issues.
If a column is being used in a meaningful way in any downstream object, you will be explicitly warned about the downstream objects impacted while doing things like editing a Dataset View.
4. Easier Scripted Content Migration
Building on Scripted Content Migration introduced in 5.6.1, the 6.1.0 release introduces the ability for content creators to select the content they would like to migrate on their own.
Ensure that the config variable DISPLAY_MIGRATION_OPTIONS is set to Y (the default is N)
- In the Element (or Category) Editor, select the "Include External Report..." option
- Wait until the next Scheduled Migration runs (this will depend on the script's schedule)
For further details, explore Scripted Migration via Category and Element Editors
For assistance, contact email@example.com
5. Power User Privileges & Permissions for JS and Email Templates
In support of multi-tenant deployments that require Admin-like Power Users, we've rounding out some of the final remaining areas wherein Power Users could not previously administer the system.
In 6.1.0, we now provide Edit Access Privileges to Power Users and allow them grant Permissions for:
6. Other Changes
- Alert Simulation no longer applies the Alert window to the simulation—this should remove an confusion when setting up an Alert.
- Data Storage changes can be tracked for auditing purposes. When Admins and Power Users with Edit Access use the Data Storage editor (for editing Data Storage integrations like Microsoft SQL Server), all meaningful changes are tracked.
- Dataset Validation can now be limited to a maximum number of rows during the data load process via the DATASET_VALIDATION_MAX_ROWS Config Variable.
- Content Discoverability functionality introduced in 5.6.1 can now be set as the default via the NEW_CONTENT_IS_DISCOVERABLE Config Variable.
- Access Request emails are now prettier (these are received by admins when an end-user requests access to content)