Skip to main content
Skip table of contents

Graph Filtering

Overview

Graph filtering is a feature that allows users to quickly find graphs of interest when they have many sites with graphs.

After selecting the Filter button you will be presented with a Graph Name drop down list.

GraphFilter.png

 

When the drop down list is selected, it will show a list of all graph names that are attached to all sites that the user has access to.

Simply select a graph name and click the apply filter button.

You don't have to select one of the options in the list. If you type part of a name in the dropdown list box then what you have typed will appear as an option in the list. You could use this to filter for graphs from sites with a certain name for example.

 

Best practice graph naming for ease of filtering

The list of graphs in the graph name filter drop down box does not repeat graphs with the same name.

If you have 10 graphs with the name "Temperature" then "Temperature" will only appear once in the list so that you can easily find all of these graphs.

This means that if you have some graphs named "Temperature" and some named "Temp" then there will be 2 entries in the drop down list. It may be preferable to rename your "Temp" graphs to "Temperature" in this situation.

Note: Only Admin users can rename graphs. Your Wildeye devices may be managed by a third party as a service.

Hashtags in graph names

If you would like your Site Name to appear in the Graph name (eg. "Lemon Ranch Temperature" then you can make use of the Hashtag #sitename.

Simply name your graph "#sitename Temperature" and the Site Name will appear at the beginning of the graph name. Hashtags do not appear in the filter dropdown list, so the list will still only show "Temperature" so that you can still filter for all temperature graphs.

You can also use the #sensorname hashtag to put the name of the sensor that appears in the graph into the graph name.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.