Understanding dashboards
A scenario is a representation of application logic, but without any defined user interaction. You add a dashboard to a scenario to enable end-users to:
Create a new scenario instance. This might include entering the initialization values for the scenario.
Monitor the status of all scenario instances. For example, to see when a pattern has been detected, and some action taken.
Manually intervene in the execution of a scenario instance. For example, to take some action in response to an alert.
Change the configuration of a running scenario instance.
Deactivate a scenario instance.
In an Apama application, a dashboard is a a real-time, business cockpit for controlling and receiving real-time updates from running scenarios. Deployed dashboards connect to one or more correlators through a dashboard data server. As the scenarios (or data views — see below) in a correlator run, and their variables or fields change, the correlator sends update events to all connected dashboards. When a dashboard receives an update event, it updates its display in real time to show the behavior of the scenario (or data view). User interactions with the dashboard, such as creating an instance of a scenario, result in control events that the dashboard data server sends to the correlator.
See
Introduction in
Building Dashboards.
If your application uses EPL rather than (or in addition to) scenarios you can create data views, which are table structures that specify event fields that you choose. You can then use these data views to create dashboards.
Alternatively, you can use the MemoryStore correlator plug-in in EPL applications. The MemoryStore creates data views for you.