find a safe way to expose the cockroach console

Open
#38 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
databases, observability, security

Research direction

Start with the deployment setup for indexer_db:8080 and determine how the console is currently exposed. Define a safe access approach that preserves useful database metrics without making the console public; the issue is complete when that approach is documented and validated against the mainnet database constraints described here.

Written by the indexing model from the issue text.

Description

type_feature

this console can't be exposed publicly but will give valuable insights in how the db is behaving. There are some disk iops performance issues with mainnet db size or on slow disks, which we will make a ticket for soon. For that, good metrics will help a lot.

indexer_db:8080

Dominant language
Shell
Stars
3
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from threefoldtech/grid_deployment

All issues in threefoldtech/grid_deployment

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.