-
Notifications
You must be signed in to change notification settings - Fork 323
How to: Filter events received by dashboards
Since 1.3.2 Smashing provides a way to filter the events that are sent to dashboards. Before this version, Smashing would send all the events for every dashboard. It could result in performance issues for your dashboard if you had many events and many dashboards.
In 1.3.3 some issues with this implementation were fixed, and then in 1.3.4 we added a flag to control whether the events are filtered or not. This flag is enabled by default, meaning we reduce the number of events sent to each dashboard.
You can control this setting by changing the value of Dashing.filterEvents = true|false
. This can be done in your application.coffee
or individual dashboard inline javascript.
If Dashing.filterEvents = false
, then the URL /events
will return the data for all the events in Smashing. Whereas with Dashing.filterEvents = true
dashboards will use a URL similar to /events?ids=synergy,buzzwords,abc
.
With this second URL, only data for these three events are received in the event stream, no matter how many events are being published by your Smashing jobs. This reduces the data sent via network, as well as the memory and processing time necessary in the browser.
- Home
- Dashing Workshop
- Installation
- Widgets
- Configuration
- Security
- Troubleshooting
- Deploying dashboards
- How Tos
- How to: post data to your dashboard and widgets
- How to: Define a data model and store history data to database
- How to: Prevent a job from overlapping with itself
- How to: Send HTML data to your widgets
- How to: Send mysql data to your widgets
- How to: Setup a Graph
- How to: Store data to and display from database
- How to: Update a Dashboard using a spreadsheet
- How to: update dashboard in Django
- How to: Update font awesome fonts from version 3 to 4
- How to: Use New Relic with Dashing
- How to: precompile assets
- Development