I just finished watching the video series and would like to congratulate you. They are awesome. Especially the animations to explain how prometheus works. Really brilliant. Thank you very much for your effort.
Do you have a video that can help me with this: I have prometheus scraping data from 3 different Raspberry Pis. I want to show to visualize the data. How do I go about doing that for data that is very similar but sourced from different Pis.
If you are looking for host metrics, take a look at my Node Exporter video, especially the part at the end where I import the Node Exporter dashboard into Grafana, which then lets you select a host to show metrics for: ua-cam.com/video/dcb59H_iLj4/v-deo.html. If it's other metrics, the approach would be similar in terms of using template variables in Grafana to allow you to select the specific host / IP to show metrics for, so you only need to create one dashboard for all hosts / Pis. You can also find more info on that in my Grafana training at training.promlabs.com/.
Hi, may I ask for some help? I am using a kube-prometheus-stack. Federating 2 remote prometheus alerts into a central prometheus. I use externalLabels and they appear just fine. Problem is, the metrics/ alerts do not have on central prometheus the set externaLabels. How to fix that?
For target relabeling, the impact is usually negligible since targets are not rediscovered / recreated at super high frequency. For metric relabeling there can be a bigger hit since the relabeling rules are applied to every sample coming from a target (which might be a lot) on every scrape. Still, you'd have to measure how impactful that really is. Similar for remote write and alert relabeling.
Thanks for the overview I want to add condition so that alerts should be dropped before reaching Alertmanager. The alert should visible in Prometheus but not in alert manager is it possible? Thank you
Yes, if you do it via alert relabeling, you could drop those alerts and they will only be visible on the Prometheus side and not in the Alertmanager. However, it's more common to still send all alerts to the Alertmanager, but set some label (like severity="info") and then just configure Alertmanager to not route them to anywhere urgent.
@@PromLabsthank you I have added like this to prom configuration (Prometheus.yml) but I can still see that alert in alert manager alerting: alert_relabel_configs: - action: drop source_labels: [severity] Regex: “info” alertmanagers: - static_configs: - targets: # - alertmanager: 9093
Hi sir. I have a question. I have successfully installed Prometheus, and it is running on port 9090. After that, I also successfully installed Grafana, but when I add Prometheus as a datasource in Grafana, it cannot be found. What could be the issue? Thank you very much.
Hi! For concrete support questions like that, I recommend using the open community channels (see prometheus.io/community/). There, many people can help and benefit from the answers, and it's also easier to give enough relevant context to a question. E.g. I'm not sure what "it cannot be found" means - do you mean that Grafana reports a connection error when you try entering localhost:9090/ as the Prometheus datasource URL? In case you are running Grafana in a Docker container, you may have to specify the host's IP (not localhost), since localhost within the Grafana Docker container will be namespaced and separate from the host where Prometheus is running.
@@PromLabs Thank you sir, for fixing that issue. Could you please create more videos about Prometheus + Grafana + Alertmanager? I think it would be very helpful. Thank you so much.
I just finished watching the video series and would like to congratulate you. They are awesome. Especially the animations to explain how prometheus works. Really brilliant. Thank you very much for your effort.
Wonderful course..Thanks for creating and sharing..
Thanks for this video. Very clear and helpful for the start in relabeling.
Thanks. So useful!
Do you have a video that can help me with this: I have prometheus scraping data from 3 different Raspberry Pis. I want to show to visualize the data. How do I go about doing that for data that is very similar but sourced from different Pis.
If you are looking for host metrics, take a look at my Node Exporter video, especially the part at the end where I import the Node Exporter dashboard into Grafana, which then lets you select a host to show metrics for: ua-cam.com/video/dcb59H_iLj4/v-deo.html. If it's other metrics, the approach would be similar in terms of using template variables in Grafana to allow you to select the specific host / IP to show metrics for, so you only need to create one dashboard for all hosts / Pis. You can also find more info on that in my Grafana training at training.promlabs.com/.
Hi, may I ask for some help?
I am using a kube-prometheus-stack. Federating 2 remote prometheus alerts into a central prometheus. I use externalLabels and they appear just fine. Problem is, the metrics/ alerts do not have on central prometheus the set externaLabels. How to fix that?
Is there any performance drawbacks when using relabeling?
For target relabeling, the impact is usually negligible since targets are not rediscovered / recreated at super high frequency. For metric relabeling there can be a bigger hit since the relabeling rules are applied to every sample coming from a target (which might be a lot) on every scrape. Still, you'd have to measure how impactful that really is. Similar for remote write and alert relabeling.
Thanks for the overview I want to add condition so that alerts should be dropped before reaching Alertmanager. The alert should visible in Prometheus but not in alert manager is it possible?
Thank you
Yes, if you do it via alert relabeling, you could drop those alerts and they will only be visible on the Prometheus side and not in the Alertmanager. However, it's more common to still send all alerts to the Alertmanager, but set some label (like severity="info") and then just configure Alertmanager to not route them to anywhere urgent.
@@PromLabsthank you I have added like this to prom configuration (Prometheus.yml) but I can still see that alert in alert manager
alerting:
alert_relabel_configs:
- action: drop
source_labels: [severity]
Regex: “info”
alertmanagers:
- static_configs:
- targets:
# - alertmanager: 9093
Hi sir. I have a question. I have successfully installed Prometheus, and it is running on port 9090. After that, I also successfully installed Grafana, but when I add Prometheus as a datasource in Grafana, it cannot be found. What could be the issue? Thank you very much.
Hi! For concrete support questions like that, I recommend using the open community channels (see prometheus.io/community/). There, many people can help and benefit from the answers, and it's also easier to give enough relevant context to a question. E.g. I'm not sure what "it cannot be found" means - do you mean that Grafana reports a connection error when you try entering localhost:9090/ as the Prometheus datasource URL? In case you are running Grafana in a Docker container, you may have to specify the host's IP (not localhost), since localhost within the Grafana Docker container will be namespaced and separate from the host where Prometheus is running.
@@PromLabs Thank you sir, for fixing that issue. Could you please create more videos about Prometheus + Grafana + Alertmanager? I think it would be very helpful. Thank you so much.
make a video about json exporter please and make more demos using various exporters