In this video, learn how you can improve productivity and pipeline throughput with the SnapLogic Intelligent Integration Platform May 2019 release updates.
In this video, I will show you a few of the upcoming features from the SnapLogic Intelligent Integration Platform release.
First, I will show you the Snap Disable feature. This feature lets you disable a Snap. There is a Snap Execution label. One of the three options is Validate and Execute. Prior to this release, there was a checkbox called ‘Execute during Preview’. So when that checkbox was checked, it was, in essence, the same as the ‘Validate and Execute’ option. If you uncheck the ‘Execute during Preview’ checkbox, the behavior is similar to that of ‘Execute only’. So only when you do a full run with the Snap, (execute the pipeline), the pipeline will insert data into the database.
Now, with the Snap Disable feature, you can disable the Snap altogether. When you do this, it disables the current Snap and the downstream Snaps. Here is gow it works. ‘Service 1’ is set to execute on preview, so you see the preview data here. Now when I change the ‘Snap Execution’ to ‘Execute Only’, I hit save, then the Service 1 snap will not get preview data. If I do the full run, it will execute. Then snap execution is disabled, and you will see the UI show a strike through the Service 1 snap. You will also see that the downstream snaps to Service 1 are disabled so they do not execute during preview or the full execution.
We created the Snap Disable feature for some of our customers who have large SnapLogic pipelines – for example, pipelines with 50 or more Snaps – and who need to disable a Snap and/or a branch. The ability to disable a Snap or a branch is useful if you are doing a join and need to process more records to get a successful join. It’s also helpful if you are troubleshooting a certain branch and need to see the data coming through.
Historically, you would have to copy a branch out from one pipeline to another or delete them and bring them back. But now we give you the ability to disable the Snap altogether, making it easy for you to troubleshoot the pipelines.
It’s important to note that if you were to call this pipeline and expect one output, like in the case of a triggered task, you could actually invalidate the pipeline. That’s because when I disable the Service 1 Snap, I now have two outputs, instead of one – one from Copy and the other from Service 2. So just be aware of that possibility.
The second thing I want to show you is the preview window. I am in the Twitter Snap and am searching for #Acme and this is the data that I get. Before, you could only view Preview data in a spreadsheet format. But now, we’ve rolled out a new DataViz option that allows you to visualize your data using different charting types.
For a pie chart, if you pick language code as the Visualization key, you can see the different language codes of twitter. You can hover over and see that ‘en’ is 70% of the total, ‘ca’ is 2% of the total, ‘jp’ is 8% of the total, and so on.
You can also see a pie chart with fromUser as the visualization key to see what users tweeted in this chunk, as well as the percentage. Jibberjaber has 12%, AcmeEssex has 14%. You can also do a Line Chart, a Bar Chart, or a Scatter Chart.
So if I select Bar Chart as the type and select Group Key as retweetCount this is the chart that I get.
The last thing I want to show you is the alerts. We added a few more alerts to the Notifications. Now within a Snaplex Node, you can get an alert on CPU or memory. So it will be based on a percentage threshold between 50 and 100. You put in the actual name of the Snaplex and the email address of the recipient. So you create the notifications at the Snaplex level and the alerts will trigger at the individual node level.
So if Node A hits 51% and Node B hits 52%, you will get two alerts. It will alert at the individual node level.
Similarly, CPU Load average can also be used to create a new notification. We look at the load average of 15 minutes so that users are alerted only when the average CPU load over the last 15 minutes exceeds the specified threshold.
Thank you for watching this video.