Open MikeShi42 opened 11 months ago
You guys also need a single docker image that I can simply use in our docker compose file. Something similar jaeger/all-in-one
This would make me so happy 😁
On top of other suggestions so far, some ideas:
Just adding my 👍 on this, ref Discord.
We have a wonderful "clone & 1-command to spin everything up" dev env, but HyperDX requires some manual configuration.
ENV
vars, but not critical.docker-compose.yml
+ .env
+ ./docker
(maybe only partially needed?)HYPERDX_APP_PORT
to anything but 8080 (I tried, but HyperDX got stuck in a loading state; setting it back worked again)I'd also recommend making the use-case of excellent local logging in dev mode a featured use-case on the docs site.
Awesome project, btw, I'm loving what I see so far! 👏
Hey all! We shipped our first version of local mode, which is a single container, no-auth required version and includes port customization OOTB without rebuilding.
If anyone wants to try it out, it should only take a few seconds to boot:
docker run -p 8000:8000 -p 4318:4318 -p 4317:4317 -p 8080:8080 -p 8002:8002 hyperdx/hyperdx-local
And more docs are here. Would love to get any/all feedback!
Often times even locally you need access to traces, metrics, logs, or at least have the ability to preview the telemetry you may be implementing without pushing to prod.
We already do this with our own HyperDX workflow, and it seems like it's been brought up a few times in our HN launch as well for being useful for other people's workflows.
We should figure out what requirements should be part of making HyperDX local-friendly, a few things on the top of my mind:
Kicking off this issue to collect any other requirements and stub out additional tickets along the way.
HYP-37