#developing custom frontends

1 messages ยท Page 1 of 1 (latest)

ebon mist
#

You could pretty easily cook up a new frontend - frontend_pretty.go is a bit of a beast, but you can see the general skeleton in frontend_dots.go, and yoink parts of pretty.go over as needed

#

or, do you mean web UI?

winged folio
#

I was thinking of CLI first, then depending on how that goes, come back for guidance on web UI ๐Ÿ™‚

#

My goal is to grow my viz dev muscle (currently non-existent) so that eventually I can offer to pair on experiments, rather than being the "ideas guy who can't ship" in that area ๐Ÿ™‚

#

I really think we've only scratched the surface of what we can deliver, the potental is so huge. So, worth the time investment

ebon mist
#

ah nice lol. happy to help!

winged folio
#

I'm going to focus on logs (per my comment in other threads)

#

What I'd love to prototype is a heroku-style log viewer

ebon mist
ebon mist
winged folio
#

In this case I think it just means - more people on the team familiar with the code, and willing & able to try things themselves

#

So I'm trying to dogfood that approach on myself (easier said than done..)

#

cc @void jackal as we talked about the same... basically "fast and furious 2.0"

ebon mist
#

2 fast 2 furious

winged folio
#

๐Ÿ™‚

winged folio
# ebon mist or, do you mean web UI?

Actually how hard would it be for me to prototype something that is 1) CLI but also 2) querying cloud data? Is there an API I can hit that will get me all the telemetry data?

ebon mist
#

yeah - you could yoink bits and pieces from dagviz for that, can link to code in DMs

#

@hushed swallow had a pet project idea to bring that functionality into the CLI, like dagger replay <url> or something (throwaway name)

hushed swallow
#

it never materialized

ebon mist
winged folio
#

@ebon mist on the otel producer side, where did you end up on the new status API?

#

still room for suggesting ideas?

#

I'm thinking of an increased specialization of "statuses" between 1) tasks (beginning, end, error/success), 2) messages (no duration, no error/success), and 3) checks (a special case of task for tests, linting etc, which we could filter to produce reports etc)