Inverse Watch Docs
AppLanding
  • Overview
    • Home
    • Governance
      • Proposal 7
      • Proposal 25
      • Proposal 52
      • Proposal 107
      • Proposal 147 - S1
      • Proposal 189 - S2
  • Products
    • Inverse Alerts
      • See on Twitter
    • Inverse Chatbot
      • /doc
      • /imagine
      • /data
      • /graph
    • Inverse Subgraphs
      • See inverse-subgraph on Mainnet
      • See inverse-governance-subgraph on Mainnet
    • Inverse Watch
      • Go to App
  • User Guide
    • Quickstart
    • Alerts
      • Setting Up an Alert
      • Adding New Alert Destinations
      • Customize Alert Template
      • Multiple Column Alert
    • Queries
      • Creating and Editing Queries
      • Querying Existing Query Results
      • Query Parameters
      • How to Schedule a Query
      • Favorites & Tagging
      • Query Filters
      • How To Download / Export Query Results
      • Query Snippets
    • Visualizations
      • Cohort Visualizations
      • Visualizations How-To
      • Chart Visualizations
      • Formatting Numbers in Visualizations
      • How to Make a Pivot Table
      • Funnel Visualizations
      • Table Visualization Options
      • Visualizations Types
    • Dashboards
      • Creating and Editing Dashboards
      • Favorites & Tagging
      • Sharing and Embedding Dashboards
    • Data Sources
      • CSV & Excel Files
      • Google Sheets
      • JSON (API)
      • Python
      • EVM Chain Logs
      • EVM Chain State
      • GraphQL
      • Dune API
    • Machine Learning
      • Data Engineering
      • Regressors
        • Linear Regression
        • Random Forest
        • Ada Boosting
        • Gradient Boosting
        • Neural Network (LSTM)
      • Training and Predicting
      • Metrics & Overfitting
      • Examples
        • Price Prediction
          • Data Preprocessing
          • Model Creation & Training
          • Metrics Evaluation
          • Back Testing
          • Visualizing
        • Liquidation Risk
  • Admin & Dev Guide
    • Setup
    • Redash
    • Integrations & API
    • Query Runners
    • Users
      • Adding a Profile Picture
      • Authentication Options
      • Group Management
      • Inviting Users to Use Redash
      • Permissions & Groups
    • Visualizations
  • Cheat Sheets
    • Snippets
    • Contracts
  • More
    • Deprecated Apps
    • Github : inverse-flaskbot
    • Github : inverse-subgraph
    • Github : inverse-watch
Powered by GitBook
On this page
  • 1. Creating a Dashboard
  • 2. Picking Visualizations
  • 3. Adding Text Boxes
  • 4. Dashboard Filters
  • 5. Managing Dashboard Permissions
  • 6. Dashboard Refresh

Was this helpful?

  1. User Guide
  2. Dashboards

Creating and Editing Dashboards

PreviousDashboardsNextFavorites & Tagging

Last updated 1 year ago

Was this helpful?

1. Creating a Dashboard

A dashboard lets you combine visualizations and text boxes that provide context with your data.

You can create a new dashboard by clicking the New Dashboard button from the Dashboard section.

After naming your dashboard, you can add widgets from existing query visualizations or by writing commentary with a text box. Start by clicking the Add Widget button. Search existing queries or pick a recent one from the pre-populated list.

You can also add a Textbox by clicking the Add Textbox button. The Textbox supports basic . In the example below, a link to the Inverse Watch Website has been added (read more about the Textbox further below).

i. Dashboard URLs

When you create a dashboard, the application automatically assigns it an id number and a URL slug. The slug is based on the name of the dashboard. For example a dashboard named “Example” could have this URL:

https://app.inverse.watch/dashboards/23-example

If you change the dashboard name to “Account Over (Old)”, the URL will update to:

https://app.inverse.watch/dashboards/23-account-over-old-

The dashboard can also be reached using its ID:

  • https://app.inverse.watch/dashboards/23

The dashboard can also be reached using a slug. Example:

  • https://app.inverse.watch/dashboards/20-transfer_dola/account-overview

Dashboard ids are guaranteed to be unique. But multiple dashboards may use the same name (and therefore slug). If a user visits /dashboard/account-overview and more than one dashboard exists with that slug, they will be redirected to the earliest created dashboard with that slug.

2. Picking Visualizations

3. Adding Text Boxes

You can include static images on your dashboards within your markdown-formatted text boxes. Just use markdown image syntax:![]( <url for image > )

4. Dashboard Filters

When queries have filters you need to apply filters at the dashboard level as well. Setting your dashboard filters flag will cause the filter to be applied to all Queries.

1. Open dashboard settings:

2. Check the “Use Dashboard Level Filters” checkbox:

5. Managing Dashboard Permissions

By default, dashboards can only be modified by the user who created them and members of the Admin group. But the application includes experimental support to share edit permissions with non-Admin users. An Admin in your organization needs to enable it first. Open your organization settings and check the “Enable experimental multiple owners support”

Now the Dashboard options menu includes a Manage Permissions option. Clicking on it it will open a dialog where you can add other users as editors to your dashboard.

Please note that currently the users you add won’t receive a notification, so you will need to notify them manually.

6. Dashboard Refresh

Even large dashboards should load quickly because they fetch their data from a cache that renews whenever a query runs. But if you haven’t run the queries recently, your dashboard might be stale. It could even mix old data with new if some queries ran more recently than others.

To force a refresh, click the Refresh button on the upper-right of the dashboard editor. This runs all the dashboard queries and updates its visualizations.

If you want this to happen periodically you can activate Automatic Dashboard Refresh from the UI by clicking the dropdown pictured below. Or you can pass a refresh query string variable with your dashboard URL. The allowed refresh intervals are expressed in seconds: 60, 300, 600, 1800, 3600, 43200, and 86400.

On public dashboards there is no Refresh button. You can add refresh to the query string. And for dashboards with parameters you can trigger a refresh by changing a parameter value and clicking Apply Changes.

By default, query results are shown in a table. At the moment it’s not possible to create a new visualization from the “Add Widget” menu, so you’ll need to open the query and add the visualization there beforehand ().

Add a text box to your dashboard using the Text Box tab on the Add Widget dialog. You can style the text boxes in your dashboards using .

Automatic Dashboard Refresh occurs as part of the the application frontend application. Your refresh schedule is only in-effect as long as a logged-in user has the dashboard open in their browser. To guarantee that your queries are executed regularly (which is important for alerts), you should use a instead.

instructions
Markdown
Scheduled Query
Markdown
creating a dashboard
dashboard refresh