Skip to content

Commit

Permalink
standardize folder names
Browse files Browse the repository at this point in the history
  • Loading branch information
kapunahelewong committed Jul 8, 2021
1 parent 2242649 commit 287caa6
Show file tree
Hide file tree
Showing 27 changed files with 2 additions and 159 deletions.
157 changes: 0 additions & 157 deletions content/en/docs/Origins/multi-origin.md

This file was deleted.

File renamed without changes.
Expand Up @@ -24,9 +24,9 @@ This setup may benefit situations where you have one ore more a static file serv

For Time Series Dashboard acceleration, this is a good configuration to use when you have a single dashboard that displays data about multiple redundant clusters (each with its own TSDB), or when you have a single dashboard representing information about many different kinds of systems. For example, if you operate a "Dashboard as a Service" solution under which many teams use your Dashboard system by designing their own dashboard screens and bringing their own databases, a single Trickster endpoint can be used to accelerate dashboards for all of your customers.

You will need to configure each Trickster-to-TSDB mapping separately in your dashboard application as a separately named TSDB data source. Refer to the [multi-origin](./multi-origin.md) documentation for configuring multi-origin support in Trickster and Grafana.
You will need to configure each Trickster-to-TSDB mapping separately in your dashboard application as a separately named TSDB data source. Refer to the [multi-origin](/docs/origins/multi-origin/) documentation for configuring multi-origin support in Trickster and Grafana.

In this configuration, be aware that the default 'memory' cache may be underpowered depending on the number of customers, as well as the size and number of queries that need to be cached by each customer. Refer to the [caches](./caches.md) document to select and configure the caching layers as needed to meet your specific situation.
In this configuration, be aware that the default 'memory' cache may be underpowered depending on the number of customers, as well as the size and number of queries that need to be cached by each customer. Refer to the [caches](/docs/caching/caches/) document to select and configure the caching layers as needed to meet your specific situation.

## Multi-Trickster

Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 comments on commit 287caa6

Please sign in to comment.