9 ms·
> Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight D
by e12e 3y ago
> Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight DID and it also came with error monitoring + session replays.
Where did you find this? Did you self-host or go with hosted?
On the docs for ingesting data, I only found some guides for things like aws - not k8s?
And there's just some Docker guides and an open issue regarding hosting:
https://github.com/highlight/highlight/issues/4390 https://github.com/highlight/highlight/issues/4390
Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs).
- Syntaf 3y agoWe're using the hosted option, and since we run on rails all we needed was the ruby SDK [1]. Essentially, we just have an additional logger attached to our stdout logger which ships logs over to highlight using their OpenTelemetry implementation. No infrastructure required, pretty simple. [1] https://www.highlight.io/docs/getting-started/backend-sdk/ruby/rails https://www.highlight.io/docs/getting-started/backend-sdk/ru...
- e12e 3y agoAh, I interpreted your comments as if you had automated logging from all k8s nodes/pods to go to highlight via some kind of automation like a sidecar or something (ie not just specific application logs).
- vadman97 3y ago> Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs). We're planning to support k8s (openshift etc.) in the next 3-6 months. If you have another platform you'd like to see supported, please commented on the issue you linked.