Find your way around the Cache Tester

The tabs, the connection rail, the database picker, and who can open which connection.

In short

The connection rail on the left lists your connections; the header shows the chosen one's tier, a database picker and a read-only tag. Four tabs do the work - Keys, Tests, Console and Server - with Audit under "More". "Connections", at the foot of the rail, lists the cache servers you can open.

Before you start

• Who: In an organization you need "Use Cache Tester" (a Member holds it, a Viewer does not). On a connection your level decides the rest. View sees tests, runs and history. Run runs saved tests. Edit works on the keys. Manage changes where it points and who it is shared with.
• Plan: Cache Tester is part of every plan, Free included. Your plan sets how many connections you keep and how many writing commands you may run an hour and a day; reads are free.
• First: add a connection (see /help/cache-tester/start-here).

Find your way around

1. Click a connection in the rail. The choice is remembered in this browser.
2. Pick the database (db0 to db15) in the header. It applies to every tab at once.
3. Open the tab you need: "Keys", "Tests", "Console" or "Server". "Audit" is under "More".

Which database has the keys? Open the Server tab: the Keyspace table lists every database that holds keys, and Browse on a row switches the picker to it.

Share a connection

1. Open the connection and press "Share" in its header, or press the Visible to line under its name.
2. Under "Who can open it", choose Private, Team, Team and below, Everyone or Read-only for others, and the team it is filed under.
3. Add a person, a team or a role at a level, with "Access until" if the share should end. Changes apply at once.

Good to know

• A connection belongs to you or to an organization: the workspace you are in when you save it decides. A personal connection is never shared.
• A new connection filed under a team starts open to that team; filed under no team it starts private, because it holds a credential.
• Below Edit, the Keys, Console and Server tabs say the server's keys are for people who work on this connection, with "Ask for more".
• On a Production connection, tests are run only by people who work on it, unless a manager turns on "Let the Run level run its tests on production". Production stays read-only either way.
• Opening another connection resets the picker to its default database. "Pin to top" keeps a connection at the top of your rail; nobody else sees your pins.
• No role opens every connection, and a site administrator's role opens none.

Deleting a connection takes its audit trail out of reach "Delete connection" makes {{brand}} forget how to reach the server. The server and its keys are untouched, but the connection's history goes with it.

If something goes wrong

• A connection is missing from the rail: check the active workspace, then ask whoever manages it.
• "You cannot give someone more than you hold on this connection yourself."
• "That person is not a member of this connection's organization."

Related

• /help/cache-tester/start-here
• /help/cache-tester/connection-tiers
• /help/organizations/sharing