Every time you edit or patch a stream, you create a version. This lets you quickly adapt your existing streams to collect logs for different properties, modify data set parameters they monitor, or change destinations where they send log files. See the Edit a stream and Patch a stream operations.

Activation status

When you edit or patch an inactive stream, you can set the the activate member's value to true to activate the stream upon the request. Set the value to false to save the stream version and activate it later.

When editing or patching an active stream, you have to set the activate member to true as you can't deactivate an active stream while editing. As a result, editing or patching an active stream moves the new version into the ACTIVATING status on the production network, and it becomes active after about 90 minutes. If you need to activate or deactivate a stream without editing or patching, see Activate a stream and Deactivate a stream for steps.

📘

Managing activating and deactivating streams

If you want to patch or edit a stream that is either ACTIVATING or DEACTIVATING, wait until the activation or deactivation process is over and the stream is ACTIVATED or DEACTIVATED. You cannot manage activating or deactivating streams.

Each version that you activate becomes a default version for a stream with the same activation status as its base version. For example, when editing or patching version 1 of an active stream, you create an activating version 2 that replaces the previous version on the production network, and becomes active after 90 minutes. Conversely, by editing or patching version 1 of an inactive stream, you create an inactive version 2 of this stream that overwrites the previous version, unless you set the activate member's value to true.

You can view and compare all configuration versions within a stream, but you can only manage the activation status of the latest version. You also can't revert a stream to any previous version. See View history.