r0b3r4

5 ms·

1. 1.▲
   Show HN: FlyQL: query language to filter data or generate SQL(github.com)

   3 points by r0b3r4 4mo ago|0 comments
2. 2.▲
   Show HN: Telescope now queries Kubernetes logs directly(github.com)

   9 points by r0b3r4 7mo ago|0 comments
3. 3.▲
   by r0b3r4 9mo ago

   You can also check out this one https://github.com/iamtelescope/telescope
4. 4.▲
   Show HN: Telescope web-based log viewer update(docs.iamtelescope.net)

   4 points by r0b3r4 1y ago|0 comments
5. 5.▲
   by r0b3r4 2y ago

   Thanks!
6. 6.▲
   by r0b3r4 2y ago

   That sounds great! Do you have a link? I'd love to check it out. For me, the most challenging parts are still ahead - live tailing and a plugin system to support different storage backends beyond just ClickHouse. Those will be interest
7. 7.▲
   by r0b3r4 2y ago

   Telescope is focused purely on viewing logs for existing data. It doesn’t enforce any specific ingestion setup or schema and doesn’t support traces or session storage. You can think of it as just one part of a logging platform, where a full
8. 8.▲
   by r0b3r4 2y ago

   Well, if you're happy with ELK, you should definitely use it! As I mentioned earlier, I’m not trying to sell anything or convince people to switch from their current solutions - just offering an alternative perspective on how things ca
9. 9.▲
   by r0b3r4 2y ago

   Nice idea! However, I’m not experienced enough with Vue (and frontend) development to properly design an exportable component. So, at least for now, I don’t think I’ll be able to make it happen myself.
10. 10.▲
    by r0b3r4 2y ago

    Despite the fact that Telescope is focused on application log data, it could be used for any type of data as long as it's stored in ClickHouse and has some time fields. At the moment, I have no plans to support arbitrary data visualiza
11. 11.▲
    by r0b3r4 2y ago

    Thanks! I haven't tested the new JSON format in ClickHouse yet, but even if something doesn't work at the moment, fixing it should be trivial. As for the video service, it wasn’t actually a service but rather a set of local tools:
12. 12.▲
    by r0b3r4 2y ago

    Telescope is primarily focused on log visualization, not on log collection or preparing ClickHouse for storage. The system does not currently provide (and I think will not ever) built-in mechanisms for ingesting logs from any sources. I wil
13. 13.▲
    by r0b3r4 2y ago

    Well, every single name I came up with was already taken and present in GitHub. So...
14. 14.▲
    by r0b3r4 2y ago

    To be honest, I was more inspired by DataDog :)
15. 15.▲
    by r0b3r4 2y ago

    Yes, this is exactly where Telescope can be useful (and actually, the way Grafana displays logs was my motivation for writing my own viewer) Telescope can work with any table in ClickHouse. Of course, not every single ClickHouse type has be
16. 16.▲
    by r0b3r4 2y ago

    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 ove
17. 17.▲
    by r0b3r4 2y ago

    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. Ho
18. 18.▲
    Show HN: Telescope – an open-source web-based log viewer for logs in ClickHouse(github.com)

    172 points by r0b3r4 2y ago|67 comments