Enabling/Disabling Features

Some features are not enabled by default within LogScale and must be switched on.

This can be achieved in two ways:

Using Configuration Settings

You can enable feature flags within the configuration file for LogScale using the INITIAL_FEATURE_FLAGS variable. To enable a feature, you must prefix it's name with a + and to disable use -. For example:

ini files
INITIAL_FEATURE_FLAGS=+UserRoles,-UsagePage

Using Mutations

Using a mutation to enable the feature means that the configuration and service do not need to be restarted to gain access to the new feature. IT is good practice if you find the feature useful to enable it in the configuration file in addition to the mutation.

To enable a particular feature, you can submit the following request through your chosen API tool or the API Explorer.

logscale
mutation {
  enableFeature(feature: SessionManagement)
}

The response will confirm the feature has been enabled:

json
{
  "data": {
    "enableFeature": true
  }
}

Features can be disabled with a different mutation:

logscale
mutation {
  disableFeature(feature: SessionManagement)
}

Which returns a confirmation that the item has been disabled:

json
{
  "data": {
    "disableFeature": true
  }
}

Using humioctl

Features can be enabled and disabled using humioctl.

To enable a feature, use the feature-flags option. Depending on the feature you may be able to enable the feature globally, for a user, or an entire organization.

For example, to enable SessionManagement globally:

logscale
humioctl feature-flags enable --global SessionManagement

Which returns confirmation:

logscale
Enabled feature "SessionManagement" globally

To disable a feature:

logscale
humioctl feature-flags disable --global SessionManagement

Which returns confirmation:

logscale
Enabled feature "SessionManagement" globally