Discussion
Every time I look at OpenTelemetry in order to add instrumentation to @manyfold and @fedipub, I bounce off it because the server setup process, even for simple home experimenting, seems so overcomplicated.
I don't need a scalable stack of 4 different systems all with their own interfaces all doing different parts of the job, I just want somewhere simple to send my telemetry and then look at it.
"Setting up an OpenTelemetry server" isn't the problem I'm actually trying to solve here.
Advice?
@johnl thanks! I’ll check that out :)
@Floppy @manyfold @fedipub I went with an nhinx log basically... instances sending basic GET requests to a special endpoint, with data parameters.
That then (currently still) gets parsed into an ELK stack, but you could pull it into whatever you want or just leave it as a basic log.
Mid term I also want to get away from ELK...
See tracking.octoprint.org for some basic info.
@Floppy @manyfold @fedipub I think @fedify did integrate that just recently. Maybe they have some advice @hongminhee
@sabrinkmann @Floppy Two directions I know of. If a hosted service is fine, something like Sentry. For self-hosting, SigNoz is the only F/OSS option I know with easy OpenTelemetry ingestion; I don't know what else is out there. It has a paid cloud version too.
I think Sentry used to have an F/OSS edition. I'm not sure it still exists, or whether it accepts OTLP though.
@Floppy @manyfold @fedipub victoriatraces supports open telemetry ingestion and all the victoria services are easy to setup and trouble free once running: https://docs.victoriametrics.com/victoriatraces/data-ingestion/opentelemetry/
VictoriaTraces: Data ingestion: OpenTelemetry setup