[Feature] dbt-cli better highlighting of which model is running and for how long
- Dominant language
- Rust
- Stars
- 13.8k
- Forks
- 2.6k
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 56
Description
### Is this your first time submitting a feature request?
- [x] I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
- [x] I have searched the existing issues, and I could not find an existing issue for this feature
- [x] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
### Describe the feature
When I run fairly big projects that have a combination of small, fast models and big ones, I find it difficult to know what each thread is doing and at which model currently it's at and for how long.
Yes we do have "START" line in the logs but after 30+ lines it's not that readable. I wish we had a line that says "PROCESSING" and configure to see that line even repeated after a certain interval.
The projects don't always execute in the same order, which means when things take time, I'm not exactly sure which model causes the delay. Of course I know it later, at the end of the run, or if I go line by line and match every START with OK CREATED.
### Describe alternatives you've considered
_No response_
### Who will this benefit?
_No response_
### Are you interested in contributing this feature?
_No response_
### Anything else?
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.