I feel like with AI, self-hosting software reliably is becoming easier so the incentives to pay for a hosted service of an OSS project are going down.
167 karma · joined June 19, 2015
gouthamve.dev
I feel like with AI, self-hosting software reliably is becoming easier so the incentives to pay for a hosted service of an OSS project are going down.
See: https://news.ycombinator.com/item?id=47692102 for the thread with this link
This is cool, but there is no LICENSE file putting this in DONT USE territory.
This has a license: https://github.com/skiptools/skipstone but it vendors the other repo according to the readme? I am super confused about how this would work.
I went from a 40" to a 52", and I'm just moving my head waaay too much and my shoulders hurt. It is curved, but very little imo, it's almost like it's flat. I'm going to try it for a week before making the call on whether to return it.
I feel like this needs a workflow where you do work in the middle and use the fringes for other applications that you rarely look at. Otherwise you're moving your head waaay too much and squinting a bunch.
> You are a Gen Z App, You are Pandu,you are helping a user spark conversations with a new user, you are not cringe and you are not too forward, be human-like. You generate 1 short, trendy, and fun conversation starter. It should be under 100 characters and should not be unfinished. It should be tailored to the user's vibe or profile info. Keep it casual or playful and really gen z use slangs and emojis. No Quotation mark
It might sound like a boring topic, but it's one of the best books I've read and something I recommend a lot.
There is an open source dedicated writer that just went on sale. It looks quite compelling and hackable.
I had to use UART to install the image to SSD but it works quite well and I am happy with it.
If you try to use Prometheus as a native push system and push directly, it'll work but you might not have the best experience. https://prometheus.io/docs/prometheus/latest/querying/api/#r...
I’d be happy to answer any questions you have.
Faro JS library —> Grafana Agent —> Loki/Tempo
We need to pull these profiles in at a regular interval by hitting the HTTP endpoint and we call this “scraping profiles”.
This is very similar to how Prometheus.io works.
Our Graphite hosting is also best in class and this makes me happy to see the good feedback!
PS: I work on Grafana Cloud Prometheus.
It will be easier and cheaper to manage compared to Jaeger but doesn't yet have any ability to search inbuilt (which is one of the reasons Jaeger is expensive).
Having said that, both Thanos and Cortex have experimental local-storage modes that are pretty good. You could also try them for now while they get production ready.
Further we use jsonnet a lot (including generating dashboards) and in general found it much more powerful and useful compared to plain YAML. From a customary glance, I can't find if kustomize supports jsonnet.
For example, in our case we do `default_deployment.libsonnet` to which we add arbitrary overrides like `default_deployment + dev` or `default_dep + us_central1_overrides` depending on the cluster. And in these case we don't need to pre-specify what can be overriden in the `default_deployment` which makes it really powerful (also can come bite you in the arse though).
2. Hmm, please open an issue regarding this with the use-case that prompted this? This is not a use-case we have but if this is important for more people, we'd be happy to support it!
3. You can only select based on the metadata, the metadata is just a set of kv pairs. Like {app=cassandra, namespace=prod, instance=cassandra-minion-0}
4. Yes, we used gzip. Please see the sheet referenced at the end of the design doc [0] to see what we compared with.
5. It's mainly protobufs right now [1] over HTTP, but we'll be adding more docs soon. Mind opening an issue for this so that we don't forget?
[0] https://docs.google.com/document/d/11tjK_lvp1-SVsFZjgOTr1vV3... [1] https://github.com/grafana/loki/tree/master/pkg/logproto
When debugging you'd want as much info as possible and you'd want to be able to simply tail + grep it. I've been told to log less because the amount I was logging would burn a hole in the pocket when deployed to production. Sometimes, at scale people only send WARN (maybe even only ERROR) and above in production which is sometimes not enough when trying to debug a system on fire.
While ELK does a great job of indexing the contents, and if you depend on it for BI, you should definitely still keep it for use-cases where just select+grep won't suffice. But for just storing logs, and being able to select, stream and grep laaarge quantities of logs, Loki will come in handy.