The error "dial tcp 74.125.206.108:587: i/o timeout" suggests that your
container can't even make an outbound network connection. Try logging into
the container and running "telnet smtp.gmail.com 587" or "nc
smtp.gmail.com:587". You should get a banner back like this:
220 smtp.gmail.com ESMTP
Hi,
We are facing the same issue, do we have a solution to manage multiple
regions?
One is global/us-east-1 for Cloudfront and other region for services like
RDS.
We are facing issue to configure both in a single config file?
On Sunday, 23 October 2022 at 14:30:12 UTC+5:30 Søren Valentin
Hello everyone,
I have currently have an eks cluster running on AWS. I installed helm chart
to setup prometheus and grafana. All metrics I need for EKS(deployments,
services, pods etc.) are totally fine. So I wanted to centrally use that
grafana for other AWS services that I use and that's why
We are considering converting from application insights to Prometheus. We
have used nlog to send our trace data.
Does anyone know if it is possible to target prometheus from nlog?
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To
On 19/04/2023 14:52, Uğurcan Çaykara wrote:
Hello everyone,
I have currently have an eks cluster running on AWS. I installed helm
chart to setup prometheus and grafana. All metrics I need for
EKS(deployments, services, pods etc.) are totally fine. So I wanted to
centrally use that grafana for
I have grafana and prometheus running on localhost and trying to run a
sample app to get some graphs within grafana. This is my first dip into
prometheus.
I am running a simple fastapi server
from fastapi import FastAPI
from prometheus_client import make_asgi_app, Gauge
# Create app
app =
On 19/04/2023 15:19, Thomas Coakley wrote:
We are considering converting from application insights to Prometheus.
We have used nlog to send our trace data.
Does anyone know if it is possible to target prometheus from nlog?
Assuming that is traces (as in spans containing call durations &
Hey all,
I was wondering if it is a bad idea to aggregate histograms that have
different bucket boundaries. If so, why?
Or can Prometheus handle this and produce reliable metrics like quartiles?
I want to dynamically resize buckets boundaries in a histogram based on
observed data but still be
I'm testing to trigger alert manager to send email but It doesnt work logs
that I got from the pod of alert manager
ts=2023-04-18T17:35:15.453Z caller=dispatch.go:352 level=error
component=dispatcher msg="Notify for alerts failed" num_alerts=1
I'm testing to trigger alert manager to send email but It doesnt work logs
that I got from the pod of alert manager
*ts=2023-04-18T17:35:15.453Z caller=dispatch.go:352 level=error
component=dispatcher msg="Notify for alerts failed" num_alerts=1
Hi Everyone
We are considering consolidating our monitoring under prometheus. In that
regards, what is the best solution/exporter/combo of exporters that can be
used for synthetic monitoring purposes, like getting response time of a
user journeys in an application / per action, for example:
Hi all:
I'm new to use the Prometheus, I send data by Pushgateway and
display data by Grafana.
I find I lose data for 3 minutes when I see grafana in two days. I think I
send the data and the network is ok.
How to debug this case?
these versions:
#
Hello All,
I am seeing a weird behavior on the graph being plotted by prometheus.
We are using a gauge which is always a non-decreasing value.
When we query the gauge from the DB, it is showing an always increasing
value across time intervals.
16800906600 vsdptas1pcar-tas01.tc.corp
We are using Prometheus for displaying several gauge type metrics. This
specific gauge would always be increasing as it demonstrates total value.
>From the query we could able to retrieve value that shows always in the
increasing order across several intervals of 10s.
16800906600
Hi all:
I'm the new to Prometheus. I send data to Prometheus by Pushgatway,
and I display data by Grafana. I find I lose data for 3 minutes. How to
debug it ? I think the client which send data is OK, I check the log. And
the network between the client and Pushgatway is alwyas OK.
I
I'm looking for a way to deal with a situation where we end up with null
characters trailing some label values: `count({ifDescr=~".*\x00"}) != 0`.
The source of the problem seems to be with `ifDescr` returned as a
`Hex-String` instead of what the MIB says should be a `DisplayString`...
for
I have a Prometheus server which scrapes data from my API metrics endpoint
that is populated using Prometheus.net library . the scraping interval set
to 15 seconds. I'm publishing a request duration summary metric to it. this
metric is published at random times to the endpoint. but the scrape
Hello everyone
New to prometheus and I'm just trying to install it on Rocky9. Following an
online guide, I installed epel-release and created repo file, adding the
lines below to it.
curl -s
https://packagecloud.io/install/repositories/prometheus-rpm/release/script.rpm.sh
| sudo bash
I'm looking for a way to deal with a situation where we end up with null
characters trailing some label values: `count({ifDescr=~".*\x00"}) != 0`.
The source of the problem seems to be with `ifDescr` returned as a
`Hex-String` instead of what the MIB says should be a `DisplayString`...
for
I have a Prometheus server which scrapes data from my API metrics endpoint
that is populated using Prometheus.net library . the scraping interval set
to 15 seconds. I'm publishing a request duration summary metric to it. this
metric is published at random times to the endpoint. but the scrape
On 25/04/2023 10:50, ofir y wrote:
I have a Prometheus server which scrapes data from my API metrics
endpoint that is populated using Prometheus.net library . the scraping
interval set to 15 seconds. I'm publishing a request duration summary
metric to it. this metric is published at random
On 21/04/2023 13:53, Arunprasadh PM wrote:
Hi,
We are facing the same issue, do we have a solution to manage multiple
regions?
One is global/us-east-1 for Cloudfront and other region for services
like RDS.
We are facing issue to configure both in a single config file?
You would need to
> 16800906600 vsdptas1pcar-tas01.tc.corp see-1 cap_tcapProvider1
NEXUS_CAP_SERVICE_VOICE cap_tcapProvider1 *18646863*
That's not a prometheus-format metric. Where are you seeing that?
And those graphs aren't from prometheus either: it would show the metric
name as
23 matches
Mail list logo
