Enable or Disable Signals
When you disable signals, the aggregation jobs are deleted, but the _signals and _signals_aggr collections are not, your legacy signal data remains intact.
|
Using the UI
When you create a collection using the Fusion UI, signals are enabled and a signals collection created by default. You can also enable and disable signals for existing collections using the Collections Manager.
-
In the Fusion workspace, navigate to Collections > Collections Manager.
-
Hover over the primary collection for which you want to enable signals.
-
Click Configure to open the drop-down menu.
-
Click Enable Signals.
The Enable Signals window appears, with a list of collections and jobs that are created when you enable signals.
-
Click Enable Signals.
-
In the Fusion workspace, navigate to Collections > Collections Manager.
-
Hover over the primary collection for which you want to disable signals.
-
Click Configure to open the drop-down menu.
-
Click Disable Signals.
The Disable Signals window appears, with a list of jobs that are created when you enable signals.
-
Click Disable Signals.
Your
_signals
and_signals_aggr
collections remain intact so that you can access your legacy signals data.
Using the Collection Features API
Using the API, the /collections/{collection}/features/{feature}
endpoint enables or disables signals for any collection:
Check whether signals are enabled for a collection
curl -u USERNAME:PASSWORD http://localhost:{api-port}/api/collections/COLLECTION_NAME/features/signals
Enable signals for a collection
curl -u USERNAME:PASSWORD -X PUT -H "Content-type: application/json" -d '{"enabled" : true}' http://localhost:{api-port}/api/collections/COLLECTION_NAME/features/signals
Disable signals for a collection
curl -u USERNAME:PASSWORD -X PUT -H "Content-type: application/json" -d '{"enabled" : false}' http://localhost:{api-port}/api/collections/COLLECTION_NAME/features/signals