brancz

14 ms·

121.
by brancz 5y ago
In that case I recommend using client-go directly. In my admittedly limited experience with operator sdk (which was created long after the Prometheus operator), it tries to abstract a lot of things to make things like working with operator
122.
by brancz 5y ago
If it has to be about operator sdk then it’s not the best example because it doesn’t use operator sdk, it uses the lower level client-go directly (I’m just commenting this because the original post was asking about operator sdk). I personal
123.
by brancz 5y ago
Thanks, that’s a great question! The eBPF part is quite similar. One difference is that we strongly believe the component needs to be open source for security reasons, since anything that uses eBPF essentially needs root. Aside from open so
124.
by brancz 5y ago
Great question! This new storage allowed us to implement a really powerful label-based data model, much like labeling and selection of time-series in Prometheus[1]. This is incredibly powerful when slicing and dicing data to find exactly wh
125.
by brancz 5y ago
Thanks! Yeah, naming is hard. I think it did come up when we were searching for a name. For clarification, the name is a play on the Program for Arctic Regional Climate Assessment (PARCA), where "ice core profiling" was performed
126.
by brancz 5y ago
Hey! Thanks for posting! One of the creators here. Happy to answer any questions! Along with the open source project we also announced our seed funding today: https://www.polarsignals.com/blog/posts/2021/10&#x
127.
by brancz 5y ago
Hey! Founder of Polar Signals here! We are super excited to be announcing Parca[1] an open source continuous profiling storage and query engine as well as an eBPF based profiler. Oh, and also we got funded! Polar Signals was founded almost
128.
by brancz 5y ago
Hey! Founder of Polar Signals here! We are super excited to be announcing Parca[1] an open source continuous profiling storage and query engine as well as an eBPF based profiler. Oh, and also we got funded! Polar Signals was founded almost
129.
by brancz 5y ago
You’re absolutely right, though none of these transfer labels by default (neither does the example Prometheus config in the prometheus repo). Prometheus, including Prometheus operator require you to allow-list them. (I should have mentioned
130.
by brancz 5y ago
Unless you explicitly allow them (via a flag) in your kube-state-metrics deployment, Kubernetes labels and annotations are not translated into Prometheus labels.
131.
by brancz 5y ago
I love this idea. It has worked extremely well for Observability data, and more generally I’ve realized this really works for any append-only workload. I’d love to understand more what is going on under the hood. I imagine cache oblivious d
132.
by brancz 5y ago
I’m personally a fan of products like this especially for early product development before there is a dedicated UI engineer on a team, I think it’s perfectly fair to pay a small amount of money like this. I’ll give you the same feedback as
133.
Demystifying Pprof Labels with Go(polarsignals.com)
6 points by brancz 6y ago|0 comments
134.
Perfessor – Continuous Profiling Without Instrumentation(polarsignals.com)
3 points by brancz 6y ago|0 comments
135.
Polar Signals Continous Profiler Cumulative Metrics(polarsignals.com)
2 points by brancz 6y ago|0 comments
136.
by brancz 6y ago
The sharing feature you can use today at https://share.polarsignals.com/ For the Continuous Profiling features just send me an email (my email is in my profile) or fill out the form on the website and we'll invite you
137.
Show HN: Polar Signals Continuous Profiler – Systematic Performance Profiling(polarsignals.com)
44 points by brancz 6y ago|4 comments
138.
by brancz 6y ago
Hey HN! A few months ago I announced that I founded Polar Signals, and today we are super excited to announce our first product (in private beta) as well as a first publicly available feature! Polar Signals Continuous Profiler is a tool we