StreamLab is a web application development environment that automatically generates streaming SQL, which are known as "StreamApps". Using StreamLab's graphical interface, you can set up input streams for data, apply built-in analytics to this data, and create sinks for data for output to external locations.
For a StreamLab tutorial, please see Tutorial 1 - Introduction to StreamLab.
This page features the following subtopics:
StreamLab is a browser-based interface for ingesting, parsing, analyzing, displaying and delivering data streams.
StreamLab lets you:
To use StreamLab, you need one of the following browsers: Microsoft Internet Explorer 11 (or later), Google Chrome 31 (or later), Mozilla Firefox 17 (or later), or Apple Safari 7 (or later).
StreamLab includes demonstration applications in the StreamLab gallery. These include an application based on global weather sensors, an application based on a content delivery network, and an application based on bus data from Sydney, Australia.
StreamLab uses its Scrutinizer to make guesses about incoming data, and in turn offer suggestions on this data. You can manage the Scrutinizer to affect how it performs.
The StreamLab menu lets you switch between StreamLab projects and dashboards, as well as managing your StreamLab account and project settings. It is available in the upper right corner of StreamLab.
Many of the tables used in forms in StreamLab now have a clipboard icon in the upper left corner. Pressing this opens a dialog with the contents of the table, as text in CSV format. The user can then copy, paste, or edit this; when saved, the table will be updated. To use the clipboard:
In a form containing rows, click the clipboard icon.
In the dialog box that opens, you can copy, paste, or edit the text. To update the columns, close the dialog box.
Before you can analyze and present data in StreamLab, that data needs to be made available in s-Server. Local log files are an exception to this rule, in that you can add these to StreamLab directly through the StreamLab interface.
The workflow for StreamLab includes the following steps:
For all projects, you can view the SQL generated by the project, as well as the SQL for individual pages. To do so, click the SQL Script Log button in the upper right corner of StreamLab.
The s-Server SQL Log window lists the following:
You can remove all or part of a project by using the Removal Script. The removal script consists of the commands to remove everything created by the project from s-server's catalog, and can be exported separately, or executed to clean up after a project.
To run a project's Removal Script:
The Goals and Scripts page opens.
Click the The Project's Removal Script tab. The Removal Script page opens.
The Removal Script runs.
Goals guide you through the process of getting a script ready to execute. If a page or project has unmet goals, it will return errors. For all projects, you can goals for the entire project and for each page. To do so, click the Goals and Scripts button in the upper right corner of StreamLab (/images/sl/sl_guide_goals_script_button.png). The Goals and Scripts window lists the following:
StreamLab generates a set of artifacts in its repository. You can move project and dashboard files from one installation of StreamLab to another. Older versions of StreamLab may not run projects generated in newer versions of StreamLab. With some exceptions, new versions of StreamLab will run projects generated in older versions.
To more a StreamLab project, you simply copy files from one repository to another. You can also move StreamLab dashboards to either a machine running s-Dashboard or a machine running another instance of StreamLab.
Files are located in the following directory:
To move files, copy files from this location to the same location on another user's machine. Once you do so and start StreamLab, these projects will be available on the Projects page.
Dashboard files are located in the following location:
These are the dashboards the user has created via StreamLab. Each dashboard is two files, *.json and *.json.rose.