gouthamve

7 ms·

31.
Sampling at Scale with OpenTelemetry(gouthamve.dev)
2 points by gouthamve 3y ago|0 comments
32.
by gouthamve 3y ago
Hi! Author of the PR here. As a project, Prometheus would like to become more OTel native and this is only the first of changes that are coming. I’d be happy to answer any questions you have.
33.
by gouthamve 3y ago
I see that shipping to Europe is not yet supported. Do you have plans soon?
34.
by gouthamve 4y ago
It’s in the getting started guide here: https://github.com/grafana/faro-web-sdk/blob/main/docs/sourc...
35.
by gouthamve 4y ago
It should work with OpenSource. You should be able to use the Grafana Agent to write to your Loki and Tempo backends on-prem as well. Faro JS library —> Grafana Agent —> Loki/Tempo
36.
by gouthamve 4y ago
Currently Phlare supports pprof which exposes profiling data on a http endpoint. 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 Promethe
37.
by gouthamve 5y ago
Hey, you can also point your Telegraf directly at GrafanaCloud Prometheus if you're interested in using Prometheus. See: https://grafana.com/docs/grafana-cloud/how-do-i/push-from-te... Our Graphite hosti
38.
by gouthamve 6y ago
https://status.twitterstat.us/ is disappointing.
39.
Buoyant Cloud and Cortex: Standing on the Shoulders of Linkerd and Prometheus(cortexmetrics.io)
1 points by gouthamve 6y ago|0 comments
40.
by gouthamve 6y ago
See some more details around the motivations and history here: https://gouthamve.dev/tempo-a-game-of-trade-offs/ It will be easier and cheaper to manage compared to Jaeger but doesn't yet have any ability to searc
41.
Grafana Tempo (distributed tracing solution): A game of trade-offs(gouthamve.dev)
2 points by gouthamve 6y ago|0 comments
42.
Grafana Labs Raises $50 Mil to Accelerate R&D Investments in OSS Observability(grafana.com)
48 points by gouthamve 6y ago|0 comments
43.
by gouthamve 7y ago
The only one I know with "non-experimental" local-storage is VictoriaMetrics. But the big thing there is that data in VM is not replicated, so when you lose a disk/node, you lose that data. Having said that, both Thanos and C
44.
by gouthamve 7y ago
Yes, it was created at Weaveworks, but it was later donated to CNCF and now the community is much bigger! Having said that Weaveworks is still a major contributor!
45.
by gouthamve 7y ago
Yes, you're running the Prometheus server. But what Cortex is a Prometheus API compatible service that horizontally scales and has multi-tenancy and other things built in.
46.
How Gojek Is Leveraging Cortex to Keep Up with Its Ever-Growing Scale(cortexmetrics.io)
2 points by gouthamve 7y ago|0 comments
47.
The Future of Cortex: Into the Next Decade(grafana.com)
1 points by gouthamve 7y ago|0 comments
48.
by gouthamve 7y ago
Hey we've been using ksonnet since before kustomize existed and we've just rewritten it to be more flexible with much more focus. Further we use jsonnet a lot (including generating dashboards) and in general found it much more pow
49.
by gouthamve 7y ago
Interesting, this is similar to jsonnet. Does it support deep merging? 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
50.
by gouthamve 7y ago
Which extensions are you talking about? Do you mean CRDs? Then it take plain JSON or you can write a function to generate those.
51.
by gouthamve 8y ago
1. Yes, you can. We initially targeted Kubernetes because that's what we use and packaging for it is simple. We'll soon release packages for all distros, support syslog/journald etc. 2. Hmm, please open an issue regarding thi
52.
by gouthamve 8y ago
Simple answer: Cost. 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 depl
53.
by gouthamve 8y ago
Yes, we have an internal doc where we compared with more providers (including loggly) where we got the pricing right. The line currently mentioned in the doc is a typo. The rationale still holds and one of the primary reasons we built Loki
54.
by gouthamve 8y ago
Yes, you're correct. We'll correct the mistake in the doc.
55.
by gouthamve 8y ago
The good thing about this is that the grepping can be parallelised and distributed on to several nodes. Having said that, once you select the relevant metadata right, you should be able to narrow it down enough for the queries to be snappy
56.
by gouthamve 8y ago
Hi, we don't index the values, but rather we index metadata about the logstream, for example, service name, instance ip, and things like that and not the actual contents of the log lines. Inside kubernetes the metatadata would be podna
57.
by gouthamve 8y ago
Hi, the promtail code is also available in the repo. See: https://github.com/grafana/loki/tree/master/cmd/promtail and https://github.com/grafana/loki/tree/master&#x2F
58.
by gouthamve 8y ago
Hi please see the design doc for more inspiration as to why we built it: https://docs.google.com/document/d/11tjK_lvp1-SVsFZjgOTr1vV3... We're soon coming out with a blog post explaining the motivations and a
59.
by gouthamve 8y ago
Hi, we're currently only exposing an API that we wrote. But we have plans to integrate with other agents such as fluentd for log collection. If the use-case has enough support, we might even be supporting a REST API.
60.
by gouthamve 8y ago
I work with Tom on Loki. When we said we wanted to focus on Kubernetes, we meant we wanted to correlate metrics with logs and focusing on Kubernetes lets us do that well. Having said that, this will work for any logs as long as you can tag

More ›