Defining
and Configuring a Target in Your Stream Analytics Pipeline
Before You Begin
This 10-minute tutorial shows you how to configure a target in
a Stream Analytics pipeline that lets you monitor public
transportation in the Atlanta area.
This is the fifth tutorial in Monitoring Public
Transportation Using Stream Analytics. Read them
sequentially.
Stream Analytics is a graphical tool with an intuitive
web-based interface that enables you to explore, analyze, and
manipulate streaming data sources in realtime.
This traffic management solution uses GPS fleet data. This data
is low cost, accurate, and it's created in real time. Its value
for government sector customers is that this fleet data reduces
congestion on roadways and enhances the traveling experience.
The general features represented in this solution are real-time
traffic analytics, speed violation tracking, and congestion
detection. These features are combined with GPS streaming sensor
feeds and historical trend data using map-based visualizations.
This solution uses enterprise-grade Spark Streaming, Kafka
open-source messaging, a highly scalable, extensible platform
built with Stream Analytics.
Some of the key benefits with this solution are low-cost
rollout with zero-road, network disruption, real-time
operational intelligence, which is essential for meaningful
congestion reduction, and an enhanced traveler experience, with
a leading streaming big data technology.
Go to Catalog, and under Show Me
click Pipelines,
and then click Tutorial.
On the pipeline tree, click SpeedViolation.
Select Add a Stage and the Target.
In the Create Target Stage dialog, enter
the name TutorialTarget and press Save.
In the Target Mapping drop-down list,
select TutorialTarget. The Target Mapping
table is populated with the target and output stream
properties.
Description
of the illustration t4_2.png
Review the Live Output Stream table to
ensure that the required data and analytics are flowing
through your pipeline deployed on the Spark/Kafka runtime. Description
of the illustration t4_3.png
Because you specified a 10-second window during the pipeline
development, in some cases, you may need to wait for at least
10 seconds before the live output stream is populated.