Hi , do u have experience with STF , collectd , Ceilometer and Openstack ?
@GuilhermePim-i8b11 күн бұрын
this was so helpful, thanks so much!!
@MikeDent24 күн бұрын
thanks for the useful info
@TheDiveOАй бұрын
totally missed the prom chrome plugin, great little gem her, thank you very much!
@TheDiveOАй бұрын
criminally under-rate'd
@佐々木千奈Ай бұрын
Thanks for the very informative video! When you calculated the percentile you had set 5m for the period to get the range vector. You said 5m is a general value, however, I saw a blog that recommended using $__interval or $__rate_interval, which are global variables in Grafana. Could you give me some advice on this? (e.g., what values to use in what cases, etc.).
@tomasprochazka6198Ай бұрын
The bloody Format button ... 🤦
@LittleBlueJugАй бұрын
Eww. Calling the container of a Cumulative Histogram a "bucket" instead of a "threshold" is pretty misleading.
@AbdallahAnalystАй бұрын
Thanks alot for sharing this with us but please how can we share our dashboard with others?
@EllaCEO-q4vАй бұрын
you are definitely the best fit to explain Prometheus & Grafana and you made it so simple. thank you
@debidattagouda9374Ай бұрын
Please make some discounts in your course it’s very expensive.
@tomhage4160Ай бұрын
Saw him blink at 0:52
@PromLabsАй бұрын
Proof that I'm human 🙌
@syedwaleedahmedshah8089Ай бұрын
HI I AM NOT ABLE TO RUN THE COMMAND ON MY WINDOWS TERMINAL, PLEASE GUIDE
@JonyElektroАй бұрын
Well... That was easier than I thought.
@andheriumАй бұрын
thank you so much my good sir!
@AlisiaMariaAlonsoАй бұрын
Very good structured video. Everything is on point. Thank you!
@fio_makАй бұрын
This guy is a AI backed robot. How can he not blink? I mean WTF. Nice videos BTW. Learning lots of things here.
@PromLabsАй бұрын
If you're not in front of a teleprompter with bright lights shining into your eyes every day, that can happen 😅 I think it got slightly better in my more recent videos, at least I tried to blink once or twice.
@RonyPlayerАй бұрын
Honestly, reading the prometheus documentation there's so many functions, its hard to know where to start at, but this video is a great start to know the most useful functions for a beginner.
@clavdamo9105Ай бұрын
I’d love to see how Grafana Alloy fits in to the equation, with examples on where it might be useful.
@canlakmin3581Ай бұрын
thank you it is so hit!!
@ibrahimosama5236Ай бұрын
If I pass my interview tomorrow on this, you are invited to Lunch in Cairo, Egypt.
@PromLabsАй бұрын
That's great to know, I was thinking of visiting there sometime :)
@ahmedhossamdev27 күн бұрын
Hey ibrahim, I hope you have passed the interview!
@realnight_bot25362 ай бұрын
How does grafana show data as a time series even if we select range as $_range for increase queries?
@PromLabsАй бұрын
If let's say you show a graph over a 1-hour period (making $__range == 1h) with a 1-minute query resolution, then what that means is that Prometheus will calculate the result of increase(foo[1h]) at each of the 60 1-minute steps over the 1-hour window. So it's like a very large sliding window, but producing an output point at every 1 minute. So in the end you see a (usually very smooth) time series.
@realnight_bot2536Ай бұрын
@PromLabs metric_name[$_range] So this $_range means grafana time range, that we change from drop down right?
@PromLabsАй бұрын
@@realnight_bot2536 Yes, see grafana.com/docs/grafana/latest/dashboards/variables/add-template-variables/#global-variables
@realnight_bot2536Ай бұрын
@@PromLabs So the calculation of 60 dots shown on the graph will be done as : Increase from 6.00 pm to 5.00 pm, Increase from 5.59 pm to 4.59 pm, Increase from 5.58 pm to 4.58 pm and so on... ? Even if I select $_range = 1hr, So this is what you are saying sir?
@vh1fo2 ай бұрын
You are a Gem. Thanks for the Tutorial
@pulithawanniarachchi79912 ай бұрын
I have a quick question to clarify. When we use the `increase` function in our queries, for the very first time a metric is reported, it will have a value of 1 in Grafana. However, the `increase` function returns zero in this case, causing the query to fail. Other functions, like `rate`, exhibit the same behavior. I believe this issue arises due to the calculation method used in the `increase` function(First time first and last data points are the same). However, starting from the second metric report onward, it works fine. Do you know the reason behind this behavior and how we can avoid this issue?
@PromLabs2 ай бұрын
Yes, when a counter metric just appears for the first time with a value of 1, the rate() and increase() functions do not know whether this was an actual increase, or whether the time series already had the value of 1, but was just temporarily absent for some reason (like a scrape failure or a too short rate window). That's why both functions currently require at least two samples to compare under the provided window. However, there is some work going on to start tracking the creation timestamps of counters, which could then be used in functions like rate() and increase() to handle these situations better. See for example this PromCon 2023 talk: kzbin.info/www/bejne/pIjJYXWchpp4e6M. And in this PromCon 2024 talk, there is more information about the possible future metadata store to store all kinds of metadata about metrics, including counter creation timestamps: kzbin.info/www/bejne/iqDVnmaDZ5iIr80
@pulithawanniarachchi79912 ай бұрын
@@PromLabs Thank you for the response. However, let’s say a second sample is received after one hour. When the rule is evaluated for the last five minutes at the time the second sample is received, it provides results. (even when I have only one data point). In my scenario, I need to trigger an alert if at least one failure is detected (I cannot use the sum function because I need to capture all labels as well). This is important because the next failure could occur after some time, as my service does not experience heavy traffic. I am monitoring metrics for the last 10 minutes.
@PromLabs2 ай бұрын
@@pulithawanniarachchi7991 "even when I have only one data point" -> No, both functions will return an empty result if they find only one sample under the requested window. What you are maybe seeing is that you do have multiple scraped samples under the window, but only one increment among those samples. In that case, yes, the functions will report that increment. If you want to detect whether there was any failure at all under a given window, the best course of action would be to either pre-initialize all relevant counter metrics to 0 upon startup (see also promlabs.com/blog/2023/09/13/dealing-with-missing-time-series-in-prometheus/) or use an expression that has a fallback in case of an empty rate result. For example, you could do something like: increase(mymetric[5m]) or (mymetric unless mymetric offset 5m) Meaning: give me the increase over "mymetric" over the last 5 minutes, and if it's not present, give me instead the value of "mymetric" right now, but only if it didn't exist already 5 minutes ago (should match the rate window length). Haven't tested it, but something like this.
@fio_mak2 ай бұрын
Basic question - how is tha alert option in graphana UI is different from alert in prom? and if one is using grafana for generating alerts, do one really needs to implement alertmanager in prom?
@2076145362 ай бұрын
hi thanks for this video. The metric created its type is untyped, how to make this metric gauge type?
@PromLabs2 ай бұрын
The Node Exporter takes the HELP and TYPE lines from the custom metric file if they are present, so for what you want, the following should be sufficient: # HELP my_metric_name My metric description # TYPE my_metric_name gauge my_metric_name 42
@2076145362 ай бұрын
@PromLabs thank you got it
@Carlos1979Mad2 ай бұрын
Thank you vey much Sir. I bough your training in PromLabs which so far has been very useful. For the histograms part in particular I struggled a bit until I took my time watching your video and trying thing on my own environment. This video was of great help and I think I got now the whole picture. Pls keep doing this. Thanks again
@erikchilders54962 ай бұрын
Thanks Julius!
@LikithBR-r6c2 ай бұрын
Julius i am not able to install Grafana in prometheus after watching video also i am facing problem can you help me please
@eopsss-f4e2 ай бұрын
iam wondering which linux distro and theme youre using. looks very clean!
@PromLabs2 ай бұрын
Thanks, it's just Arch Linux with the i3 tiling window manager :)
@culturadev2 ай бұрын
Thanks a lot Julius!
@jeyhunaze76282 ай бұрын
Great!!! Thank you for such wonderful video!!!
@cutecolt2 ай бұрын
Wonderful course..Thanks for creating and sharing..
@MatsAndersson2 ай бұрын
Wow. Didn't blink a single time. Quite impressive.
@PromLabs2 ай бұрын
Trained that for a long time.
@filipstojiljkovic47113 ай бұрын
Impressive, very nice.
@PromLabs3 ай бұрын
Now let's see Paul Allen's card... kzbin.info/www/bejne/ganRl5KDf5p8jdU
@filipstojiljkovic47113 ай бұрын
@@PromLabs ;D
@sorousheta70013 ай бұрын
Learning from the creator of a App, was a great blessing and an incredible opportunity that came our way. thank you Julius <3
@acmtix3 ай бұрын
Loving your videos very informative!
@PatrickGalbraith3 ай бұрын
Excellent video! What do you use for your diagrams? I am preparing to present at Open Source Observability day in a week and would love to have nice looking diagrams like yours.
@PromLabs3 ай бұрын
Thanks! For the diagrams I just used www.drawio.com/. For many of the animations in my latest videos I used motioncanvas.io/.
@cryoexn73073 ай бұрын
These videos are amazing! I have been transitioning from influx to otel, and Prometheus for custom metrics and these are super helpful Just a question from something i noticed in the video, isn’t the count always going to be equal to the +Inf bucket since it’s a cumulative histogram? Was wondering if there’s a reason they are separate other than to avoid confusion?
@PromLabs3 ай бұрын
Thanks! Yes, the count is always going to be the same as the +Inf bucket, but it's still useful to have both: when working with histogram_quantile(), it's easier to just pass in all the *_bucket time series. When working with just the count to get a normal request rate, it's easier to just work with the _count series.
@rafiraf15223 ай бұрын
Awesome video, thank you for posting it!
@NoBodyDroid3 ай бұрын
What software you use for these visualizations?
@PromLabs3 ай бұрын
motioncanvas.io/ mostly :)
@animeshkumar16063 ай бұрын
Great video, nicely explained
@edgarreis72264 ай бұрын
Very informative videos. Thanks a lot !
@LeoAlekseyev4 ай бұрын
What are the units in the "value" field of the tooltip? Like for your last example of the 333-499 bucket, the value displayed is 0.007. How do I interpret this number?
@PromLabs4 ай бұрын
I mention it a few seconds before that for the other bucket: it's requests per second. That's because each bucket series is a counter and we're taking the rate() of it, which always returns a per-second result. See also my histograms video (kzbin.info/www/bejne/r4rFiZShYpabm9k) and the one about rates and increases (kzbin.info/www/bejne/babckKylq9msp9k).
@parsahosseini42414 ай бұрын
Awesome video mate. Thanks a lot for sharing it.
@tanmaymishra924 ай бұрын
Awesome, huge fan of prometheus (still a beginner) , the simple architecture and the kind of services it can provide, too good
@UmutAkkaya-s8q4 ай бұрын
Julius. It was a great video thank you.
@IgorZubchenok4 ай бұрын
Hi @Julius, I wanted to share some feedback regarding the product decisions you made in Prometheus, specifically around the extrapolation of values, as highlighted at 8:21 in the video and earlier. While I appreciate the continuous effort to enhance the platform, I must express my concern over the implementation of extrapolated values and the introduction of arbitrary figures like the 1.1 factor. From my perspective, these changes have complicated the user experience for many developers. The rationale behind such decisions seems unclear, and they appear to contribute more to confusion than to clarity. This kind of over-engineering, especially in such a critical aspect as chart accuracy, undermines trust in the tool. In my experience, the reliability of charts is paramount. Rather than relying on extrapolation, I strongly recommend focusing on gathering more precise data within the range window. Displaying charts based solely on actual measurements before and after the range window would provide a much clearer and more trustworthy visualization. I hope you consider revisiting these decisions to align better with the needs of the developer community. Prometheus has always been a great tool, and with a bit more focus on core functionality, it can maintain that trust and reliability. Thank you for your attention to this matter.