Live data from Hacker News

Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

github.com

11–20 of 75 posts

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#11

This one seems to be optimized for log viewing at the moment, are there any DataDog alternatives built on top of Clickhouse, which supports full range of OpenTelemetry features?

There are these guys which are based on OTEL: https://github.com/hyperdxio/hyperdx

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#13

Looks cool I might try it out! I need a central place, something simple where I can actually read the contents of the logs that are generated by the dozen of services that I run for clients, etc… instead of stupidly SSH’ing to every server. Does this fit the use case? I tried Loki once but it was painful to set up and more geared toward aggregating events and stats.

genuinely wondering if https://multiplayer.app would work for you.

note: I'm part of the Multiplayer team.

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#14

This one seems to be optimized for log viewing at the moment, are there any DataDog alternatives built on top of Clickhouse, which supports full range of OpenTelemetry features?

There is lumigo, also based on Clickhouse https://lumigo.io/

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#15

This one seems to be optimized for log viewing at the moment, are there any DataDog alternatives built on top of Clickhouse, which supports full range of OpenTelemetry features?

I think https://multiplayer.app would also fit your description.

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#16
post #8

Looks cool I might try it out! I need a central place, something simple where I can actually read the contents of the logs that are generated by the dozen of services that I run for clients, etc… instead of stupidly SSH’ing to every server. Does this fit the use case? I tried Loki once but it was painful to set up and more geared toward aggregating events and stats.

I’m curious to know what makes the Loki installation process so painful. I’m interested in learning more about the software installation experience.

Only problematic thing might be relatively frequent storage changes (like they like to deprecate primary storage driver), otherwise its IMHO easy to setup. I'm running it on several projects, because it doesn't needs beefy machine like Elastic or even ClickHouse.

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#17

Looks cool I might try it out! I need a central place, something simple where I can actually read the contents of the logs that are generated by the dozen of services that I run for clients, etc… instead of stupidly SSH’ing to every server. Does this fit the use case? I tried Loki once but it was painful to set up and more geared toward aggregating events and stats.

Thanks! Telescope is more focused on displaying logs and providing access to them rather than handling log ingestion. In the future, I plan to support various sources like Docker, k8s, and files to improve the local development workflow. However, it's unlikely that Telescope will support fetching logs from remote servers via SSH, as that's not its primary use case.

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#18
post #9

Unfortunate name choice, as @csh602 mentioned Viewer looks pretty good though. Reminds me of DataDog UI, but not as slow. Will play around more, thanks!

As we all know, naming is an unsolvable problem in IT :)

Regarding performance - 95% of Telescope's speed depends on how fast your ClickHouse responds. If you have a well-optimized schema and use the right indexes, Telescope's overhead will be minimal.

Re: Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse

#19

Looks cool I might try it out! I need a central place, something simple where I can actually read the contents of the logs that are generated by the dozen of services that I run for clients, etc… instead of stupidly SSH’ing to every server. Does this fit the use case? I tried Loki once but it was painful to set up and more geared toward aggregating events and stats.

Graylog is a pretty standard solution to your problems (I believe), although they've been closing down their licensing more and more as time goes on.
Post reply on HN