You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

Many aspects of the functionality of Redash can be changed with settings. Settings are read by redash.settings from environment variables which (for most installs) can be set in /opt/redash/.env. When developing with Docker, create the .env file in the root directory. The follow is a list of settings and what they control: Name Description Default Value

Create a New Visualization Once your query has finished running for the first time, you can add a visualization by clicking the “New Visualization” button above the results table. Edit A Visualization You can modify the settings of an existing visualization from the query editor screen. Click the visualization on the tab bar and you’ll see an Edit Visualization option beneath each visualization. C

The Query Results Data Source (QRDS) lets you run queries against results from your other Data Sources. Use it to join data from multiple databases or perform post-processing. Redash uses an in-memory SQLite database to make this possible. As a result, queries against large result sets may fail if Redash runs out of memory. The QRDS doesn’t work with results from queries that use parameters. If yo

Setup The Datasource Create a Service Account Open the Service accounts page. If prompted, select a project. Click Create service account. In the Create service account window, type a name for the service account, and select Furnish a new private key. When prompted, select JSON key file type. Then click Create. Your new public/private key pair is generated and downloaded to your machine; it serves

These instructions are for users of our new Docker-based instance. If you run our older instances (or the old bootstrap script) check the legacy guide. We recommended you upgrade your Redash instance to the latest release so you can benefit from new features and bug fixes. This document assumes you used our images to set up your instance of Redash. For best results you should upgrade Redash by one

The instructions below are for the legacy images. If you use the new Docker based images, see the following guide: https://gist.github.com/arikfr/64c9ff8d2f2b703d4e44fe9e45a7730e If you used the provided images or the bootstrap script, to start using SSL with your instance you need to: Update the nginx config file (/etc/nginx/sites-available/redash) with SSL configuration (see below an example). M

Create an Instance For basic deployments we recommend a minimum of 4GB of RAM and reasonable amount of CPU allocation. As usage grows you might need additional RAM and CPU power to support increased number of background workers and API processes. To create an instance, you have the following options: AWS EC2 AMI Google Compute Engine Image Other Docker We have not updated our official images for V

Knowledge BaseUser GuideGetting StartedQueryingVisualizationsDashboardsAlertsUser, Groups, & PermissionsIntegrations and APIData SourcesSetup & QueryingFAQGeneralTroubleshootingHosted Redash End of LifeOpen Source & Self HostedSetting up a Redash InstanceAdmin GuideDeveloper Guide

These instructions are not relevant for those who use our Docker based instances and should be updated. We will appreciate your help with updating this guide. Configuration and Logs The supervisor config can be found in: /etc/supervisor/conf.d/redash.conf if you’re using the new images that install Supervisor with a system packages. Otherwise, you can find it at /opt/redash/supervisord/supervisord

Redash helps you make sense of your dataConnect and query your data sources, build dashboards to visualize data and share them with your company. “Redash is as essential as email to my company. We love data but accessing the data is a pain without Redash. Any company I go to, I get them hooked on Redash. It’s an easy sell :)” by Ben Dehghan, Co-Founder of Data Miner Read what our users say → Write