tilt-dev / tilt-dev/tilt

View for only (global) logs

Open
#5,381 7 comments 0 reactions 1 assignee View on GitHub

@milas is already working on this.

Since Jan 21, 2022.

enhancement
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Describe the Feature You Want

I have added some neat buttons to my tilt configuration, and I want to comfortably observe/focus on the results of clicking those buttons.

Current Behavior

As I understand it, the only way to view the logs from things like local_resource (edit: I'm not actually sure what this is called) commands, are to open the All Resources page, which is overwhelmed by other garbage reported from my services (something I can't control the output of).

This leads to a very confusing and disgusting experience where I want to just run something like a migration revert or a code generation, but I may very easily miss an error that occurs when these are run.

Why Do You Want This?
  • I want to know when my commands fail
  • I want to observe the outputs of those commands even if they succeed (such as in the case for a sanity check command)

Additional context

This potentially has overlap with https://github.com/tilt-dev/tilt/issues/1815 (but that feature looks a little more comprehensive, and has been around for a while).
Perhaps this pain point would be addressed by the mentioned feature, but that doesn't do us much good if that feature remains in a design-consensus phase. So, I'm suggesting that there must be some way to do something simpler in order to relieve this major pain point.

About us:

  • We're a team of 4 using tilt for the same project.
  • Our project is about two years old, and we incorporated tilt about 5 months ago.
  • Our entire platform spins up in tilt very similarly to how our platform will work in prod k8s
  • We have written several helpers in our Tiltfile so far
  • Our codebase is written for Node.js (TypeScript) + Browser (TypeScript) + Rust
  • We use Honeycomb for observability in our dev environments.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.