Actually,
the readiness probe is failing . GET "http://x:3000/api/health":dail
tcp x:3000:connect connection refused
On Thu, Aug 26, 2021 at 10:45 PM James S wrote:
> The grafana pod is in CrashLoopBackOff state.
> Event: Back-off restarting failed container
>
>
>
> On Thu, Aug 26,
The grafana pod is in CrashLoopBackOff state.
Event: Back-off restarting failed container
On Thu, Aug 26, 2021 at 10:13 PM James S wrote:
> Hi,
>
> we have installed Prometheus, node-exporter, alertmanager,
> kube-state-metrics & Grafana with this helm chart
>
Hi,
we have installed Prometheus, node-exporter, alertmanager,
kube-state-metrics & Grafana with this helm chart
https://github.com/helm/charts/tree/master/stable/prometheus-operator
we installed extracting the yamls from the Helm template as we do not have
HELM on our clusters.
now I have
for the node-eporter
info ts=2021-08-25T21:12:10.546Z caller=node_exporter.go:115
collector=diskstats
info ts=2021-08-25T21:12:10.546Z caller=node_exporter.go:115 collector=edac
info ts=2021-08-25T21:12:10.546Z caller=node_exporter.go:115
collector=entropy
info ts=2021-08-25T21:12:10.546Z
image: quay.io/prometheus/node-exporter:v1.2.1
args:
-
--collector.filesystem.ignored-mount-points=^/docker/(overlay2|containers).*/(shm|merged)
-
What errors?
On 26 August 2021 19:27:41 BST, James S wrote:
>But I am running into errors when I upgrade to the latest versions, for
>Prometheus, node-eporter and grafana
>
>On Thursday, August 26, 2021 at 2:24:46 PM UTC-4 sup...@gmail.com wrote:
>
>> Yes, just updating the image versions is
But I am running into errors when I upgrade to the latest versions, for
Prometheus, node-eporter and grafana
On Thursday, August 26, 2021 at 2:24:46 PM UTC-4 sup...@gmail.com wrote:
> Yes, just updating the image versions is good enough. Prometheus
> guarantees pain-free upgrades in major
Yes, just updating the image versions is good enough. Prometheus
guarantees pain-free upgrades in major versions. Any 2.x will update to the
latest 2.x.
On Thu, Aug 26, 2021 at 7:33 PM James S wrote:
> Hi,
>
> we have installed Prometheus, node-exporter, alertmanager,
> kube-state-metrics &
Hi,
we have installed Prometheus, node-exporter, alertmanager,
kube-state-metrics & Grafana with this helm chart
https://github.com/helm/charts/tree/master/stable/prometheus-operator
we installed extracting the yamls from the Helm template as we do not have
HELM on our clusters.
we have not
Hi guys, were you able to validate the host's username and password?
Em sexta-feira, 16 de julho de 2021 às 12:59:05 UTC-3, somn...@optit.co
escreveu:
> Hi
>
> Could you please help with prometheus.yml example configuration for the
> basic auth ?
>
> I tried with your updated config in
On 8/26/21 06:14, Dorian Jaminais-Grellier wrote:
> Now the naive way is to create a gauge for the sensor and expose it all
> the time. The problem is that this makes it impossible for me to
> distinguish between the temperature staying constant and the sensor not
> reporting any metrics anymore.
In the docs there's a warning on potential performance issues in high load
situations when running NE with tcpstat collector. Anyone using it in
production environments? Seen actual problems?
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users"
Hi Team,
I configured snmp exporter on prometheus.
SNMP exporter not retrieving ay metrics and showing error "server returned
request 400"
Please help me out in fixing the issue.
Regards,
Jivraj Singh
--
You received this message because you are subscribed to the Google Groups
"Prometheus
I cannot formulate the questions in more detail. I try to find a contact
who can help with issues.
Stuart Clark a következőt írta (2021. augusztus 26., csütörtök, 8:03:31
UTC+2):
> On 26/08/2021 06:57, Henriett Braunné Bokor wrote:
> > Hi,
> > The trouble is, we’re halfway through the pilot
On 26/08/2021 06:57, Henriett Braunné Bokor wrote:
Hi,
The trouble is, we’re halfway through the pilot test and these are our
fixed questions and we don’t have a connection, so I don’t know
who to look for. Do you have a direct relationship?
The suggestion of speaking to someone
Hi
I just copy those alerts
https://awesome-prometheus-alerts.grep.to/rules#kubernetes
I not wish to modify the individual alert (query). I wish to exclude
globally some namespaces and pods.
Is it possible to exclude some stuff, but not modify the individual
query I got from upstream?
16 matches
Mail list logo
