🚧

This feature is in BETA and available to selected users only.

Before creating a stream to start sending near real-time log data to the destination of your choice, consider the types of stream configurations available in DataStream:

• DataStream-managed. The new stream configuration type available in DataStream. Create and manage your stream directly in the DataStream interface or API. You can create a stream configuration on either an active or inactive property. Logs will start delivering once the property is activated, or if the property is already active when the stream is configured.
• Property Manager-dependent. This configuration requires creating a stream in DataStream and setting up the DataStream behavior in Property Manager before the stream starts streaming logs. Useful for logging only specific subsets of traffic.
• Hybrid. Streams logging data for multiple properties at the same time, some of them with and without the DataStream behavior configured in Property Manager.

📘

Stay updated

DataStream is a solution in constant development. We’re aiming to phase out Property Manager integration to improve workflow time, the user interface experience, and stream automation.

The DataStream-managed stream configuration is set to become the default type available in DataStream. It will gradually include features from Property Manager to the application.

See the Release notes to stay up to date with the latest developments.

DS-managed and PM-dependent streams

The DataStream dashboard shows if the stream is DS Managed, PM Dependent or Hybrid under the Integration Type category along with other stream metrics, including the number of datasets, destination, and stream status.

DataStream-managed streams may take less time to set up and start streaming logs, as you can configure each stream in the DataStream application. They offer improved support for automating resource creation, such as when using Terraform. You can configure features including logging midgress traffic and the data sampling rate when creating the stream, instead of setting them up in Property Manager.

Property Manager-dependent streams require additional property configuration, and may take longer to set up and start streaming logs, but allow leveraging the rule and match logic. This is particularly useful if you want to log only specific traffic segments on a property, compared to logging all traffic in DS-managed streams. You should also use PM-dependent streams if you want to apply different sampling rates for different properties monitored in the same stream.

See the table below for the breakdown of differences between both integration types:

Hybrid streams

In DataStream, each stream can collect and send log data for multiple properties with and without the DataStream behavior configured in Property Manager. The DataStream dashboard lists streams with multiple properties as Hybrid.

📘

In Hybrid streams, the settings configured in the DataStream behavior for each property in Property Manager (including logging midgress traffic and the sampling rate) always override the stream configuration from the DataStream interface or API.

Migrate a stream to DS-managed

DataStream now lets you quickly launch a DS-managed stream from scratch, but also change an existing stream configuration from PM-dependent to DS-managed.

For DS-managed streams, configure settings such as logging Midgress traffic and the stream's Sampling rate in the DataStream applications, and delete the DataStream behavior from your property configuration in Property Manager.

You can change your stream to DS-managed if you want to minimize configuration time and automate data collection in your stream.

How to

Migrating a stream to a DS-managed setup requires removing the DataStream behavior from your property configuration in Property Manager.

Let’s look at the couple of steps needed to migrate your stream:

1. Log in to Control Center using a User ID and Password configured for DataStream access.

2. Go to COMMON SERVICES > DataStream.

3. On the DataStream page, find the stream you want to edit. Click · · · in the Actions column and choose Edit to open the Edit stream wizard. See View and manage versions.

4. In Configuration, you can:

   • Edit the Name of your stream.
   • Edit the Contract ID for which you initially created the stream.
   • Depending on the stream's log type, edit the properties of the stream:
     • Use Include properties for delivery products.
     • Use Select properties for GTM.
     • Use Select zones for Edge DNS streams to choose which properties or zones to log data for.

5. Click Next to continue to the Data Sets screen, where you configure settings previously set up in the DataStream behavior in Property Manager:

   • In Data sets, edit the parameters the stream collects. In a DS-managed stream, you can choose to log Midgress traffic.

6. In Delivery, edit the destination where the stream sends logs and the delivery conditions for your log files. In a DS-managed stream, you can set the Sampling rate in the DataStream application.

7. In Summary, review your changes and decide whether to activate the edited stream.

8. Optional: Select Receive an email once activation is complete and provide email addresses for notifications when the stream is active on the production network.

9. If you're editing an active stream, click Save stream to activate the stream upon saving. For inactive streams, check the Activate stream upon saving box to activate the stream after clicking Save stream. If the box is unchecked, click Save stream to save the configuration and activate later.
   The stream edit wizard closes.

10. Go to Property Manager. Click ☰ > CDN > Properties or enter Properties in the search box.
    The Property Groups page opens.

11. Click the Property Name to access your property. Go to the latest Version of your configuration in Manage Versions and Activations.
    The Property Manager Editor appears.

12. Expand the Property Configuration Settings menu and click the trash icon to remove the DataStream behavior from any rules it may contain.

13. Click Save to return to the list of properties, then click Activate v# on Production to activate the version you just edited.

14. Close Property Manager.

15. If you chose to activate the stream upon saving, it takes about 60 minutes for the stream to activate. After this time, your stream is active on the production network. If you saved an inactive stream, activate it when ready.

From now on, use only the DataStream application or the API to edit an existing stream, including changes to the sampling rate, logging midgress traffic, or adding new properties for the stream to monitor.