netingle

11 ms·

61.
by netingle 8y ago
Of course! Everything is opensource, all apache licensed: https://github.com/grafana/loki/tree/master/pkg/promtail
62.
by netingle 8y ago
There is a REST API, yes [0]. Currently you send snappy-compressed protobufs[1] containing yours log to a HTTP endpoint. We initially started using fluentd as the agent, but we found its metadata "enrichment" facilities weren&#x2
63.
by netingle 8y ago
Exactly! In fact, we're moving to use some of mtails libraries and functionality [0]. The main difference is we do centralise, scalable persistence of the logs themselves, wheres IIUC mtail just processes them and exports metrics. Tha
64.
by netingle 8y ago
Thats a really good question. I feel like its pretty well covered in the design doc[0], and you should also read about OKlog[1] which really championed this idea. To be clear: Loki indexes metadata about the streams, and the streams themse
65.
by netingle 8y ago
> Is this logging already available on Grafana Cloud ? Because someone I know is looking for a hosted logging solution and was looking at ELK till now. There is a free preview right now: http://grafana.com/loki We'l
66.
by netingle 8y ago
Thats fair; the logo was a last minute thing, we'll work on a new one...
67.
by netingle 8y ago
If all you use ELK for us simple process/container logs then yes! That’s the whole idea. But Loki is not a replacement for Elastic - we don’t have any complex query support, and we don’t do full text search. Elastic is great for analyt
68.
by netingle 8y ago
I'm just a really bit Marvel fan though - he did redeem himself in the last film, no?
69.
by netingle 8y ago
Agreed - Loki was heavily influenced by OKLog. We really like its ease of use and simplicity - hopefully we managed to get some of that right with Loki. OTOH we felt like we needed a little bit of metadata and index to help find the right
70.
by netingle 8y ago
>Looks like a good light-weight alternative for setting up a full elasticsearch cluster for some light log insights. Exactly! Elastic is a really powerful system but I think there is growing sentiment that its overkill for container log
71.
by netingle 8y ago
Loki is design to compliment Prometheus; as such we envisage you using Prometheus metrics to isolate the service and time range exhibiting the anomalous behaviour (by looking at latency and error metrics, for instance) and then "pivot&
72.
by netingle 8y ago
Its there: https://grafana.com/cloud#features And Cortex is now a CNCF project: https://github.com/cortexproject/cortex https://www.cncf.io/sandbox-projects/
73.
by netingle 8y ago
This is a continuation of our ideas from Kausal, yes! Really glad we joined Grafana as they have given us the time and resources to pursue this. And not shutdown at all! Everything we did at Kausal is now part of Grafana and Grafana Cloud
74.
by netingle 8y ago
It’s defiantly something that’s missing from the readme, and perhaps not that obvious in the grafana explore view either - but it is there! You can push a regexp match server side and have that distributed to each Loki node, giving you dist
75.
by netingle 8y ago
Author here! Really excited to release this at KubeCon; happy to answer any questions you might have.
76.
Cortex project, horizontally scalable Prometheus, added to CNCF(cncf.io)
3 points by netingle 8y ago|0 comments
77.
by netingle 9y ago
IIUC ENIs are limited to 2 per host on small instances, 15 per host on larger ones. Doesn't this approach limit the number of Pods per host? I'm already running about 20 pods per host, and I don't more containers per host i
78.
by netingle 9y ago
Particularly interesting, given that most of the software in the container space seems to be written in go: Docker, Kubernetes etc
79.
by netingle 10y ago
Best practices are not to use that for anything other then kubernetes components - it contains all your secrets in pain text, for example.
80.
Running Consul on Kubernetes and Monitoring It with Prometheus(weave.works)
14 points by netingle 10y ago|2 comments
81.
Turtles all the way down: HTTP over gRPC(weave.works)
10 points by netingle 10y ago|0 comments
82.
by netingle 10y ago
Cool - the key is making the source of truth for config a git repo, and providing tools to make that state match reality, and tool to check if it really does. This is why I like terraform, and to some degree tolerate ansible...
83.
How we run our upgradable Kubernetes clusters, using Terraform and Ansible(weave.works)
9 points by netingle 10y ago|3 comments
84.
by netingle 10y ago
> If you want to use Prometheus as a SaaS we recommend Weaveworks https://www.weave.works/solution/prometheus-monitoring/ Which is also open source! https://github.com/weaveworks/cortex
85.
by netingle 10y ago
There is an project we've just started: https://docs.google.com/document/d/1C7yhMnb1x2sfeoe45f4mnnKC... Hopefully have something to show for promcon.
86.
by netingle 10y ago
We are! And unsurprising it's a great fit given k8s is inspired by Borg and Prometheus is inspired by Borgmon.
87.
Announcing Weave Scope 'Cloud': hosted Docker visualisation early access program(blog.weave.works)
9 points by netingle 11y ago|1 comments
88.
Scope: visualisation for Docker. Big release, better UI and connection tracking(blog.weave.works)
7 points by netingle 11y ago|0 comments
89.
Weave 'Gossip' DNS – Service Discovery for Docker(blog.weave.works)
4 points by netingle 11y ago|0 comments