Thank you very much Brian.
On Monday, December 13, 2021 at 7:04:33 PM UTC+8 Brian Candler wrote:
> I think there's not much point continuing this discussion. Prometheus
> does not have exactly what you keep asking for, which is "to check"
> something externally before sending an alert to alert
É ASSASSINA E LESBICA: #MARINABERLUSCONI! É NAZI卍PEDOFILA KILLER MARINA
BERLUSCONI! COME SUO PADRE, IL FASCISTA, MAFIOSO, PEDOFILO, MEGA MANDANTE
DI OMICIDI E STRAGI: #SILVIOBERLUSCONI! E POI, IL FIGLIO DI PUTTANONA
#PIERSILVIOBERLUSCONI (ANCOR PIÚ..FIGLIO DI PEDOFILO MACELLA MAGISTRATI
SIL
> (I'm showing JSON rather than YAML as it's easier to type :-)
Swap those. Of course.
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to prometheus-users+unsu
> My concern is that since this is still for node_exporter port 9100 for
both jobs, I'll get duplicate scrapes ingested.
You will, but it's not really a problem, because they will have different
labels {job="se-linux-node-exporter"} and {"job=se-linux-XYZ-service"} and
therefore will be stored
On 13/12/2021 17:23, mcamm...@gmail.com wrote:
Hi Everyone,
We currently use an external tool to query our list of targets from an
internal database. We then use file based service discovery in
prometheus and provide it the list of targets in a .json file. Works
nicely. This is for the node_e
Hi Everyone,
We currently use an external tool to query our list of targets from an
internal database. We then use file based service discovery in prometheus
and provide it the list of targets in a .json file. Works nicely. This is
for the node_exporter job.
- job_name: 'se-linux-node-exporter
Hey,
for the kube-prometheus project the best place to find support and answers
would be the Discussions on GitHub:
https://github.com/prometheus-operator/kube-prometheus/discussions
It sounds like you found a lot of really good things!
If there are things in there that you think should be gene
I think there's not much point continuing this discussion. Prometheus does
not have exactly what you keep asking for, which is "to check" something
externally before sending an alert to alertmanager. All it can check is
what's in its timeseries database at that time.
However, you can achieve
if some one changes the status to in maintenance and performs a reboot ...
prometheus will notice this status update after 5 secs and during this time
it could generates fake alerts
On Monday, December 13, 2021 at 5:10:51 PM UTC+8 nina guo wrote:
> Thank you Brian.
>
> Let's assume the refresh
if some one changes the status to in maintenance and performs a reboot ...
prometheus will notice this status update after 3 min and during this time
it could generates fake alerts
On Monday, December 13, 2021 at 5:10:51 PM UTC+8 nina guo wrote:
> Thank you Brian.
>
> Let's assume the refresh i
Thank you Brian.
Let's assume the refresh interval is only 5 secs, but during 5 secs the
state might be changed. For exmaple, the target is changed to
maintence(which is not the state we want to monitor) and start a reboot,
but at this time point, prometheus doesn't know the state change, a fa
You can always read the inventory as often as you like. Read it every 5
seconds if you like. Write it to a new file like "targets.new", compare it
with the old "targets" file, and if they are different rename targets.new
to targets. Then prometheus will pick it up the new file immediately.
T
On Monday, 13 December 2021 at 05:25:07 UTC princ...@gmail.com wrote:
> Let's I want to make data available at the metric endpoint along with its
> timestamp(the time at which we got this data). B*ut the system time is in
> PDT and I also want the Prometheus dashboard x-axis with this PDT time,
Correct the words * there is a target is removed from the inventory
On Monday, December 13, 2021 at 4:31:09 PM UTC+8 nina guo wrote:
> Thank you Brian.
>
> Your suggestion is really good. May I have one more question?
>
> For example, if you read the inventory via Netbox every 5mins, let's
> as
Thank you Brian.
Your suggestion is really good. May I have one more question?
For example, if you read the inventory via Netbox every 5mins, let's
assume, if during the 5mins, there is a state of the target is removed
from the inventory, at this time point Prometheus still triggers an fake
a
On 13/12/2021 08:18, kiran wrote:
Hi Stuart,
The open telemetry library is for python application to instrument the
code.
In my case I already have metrics coming in open telemetry format
already. Just need transformation into prometheus format.
Maybe try asking on their mailing list (or wha
Hi Stuart,
The open telemetry library is for python application to instrument the code.
In my case I already have metrics coming in open telemetry format already.
Just need transformation into prometheus format.
On Mon, Dec 13, 2021 at 2:14 AM Stuart Clark
wrote:
> On 13/12/2021 08:11, kiran w
On 13/12/2021 08:11, kiran wrote:
@Stuart: Thank you. Any reference to libraries which can do that. I am
not able to find any.
For Python there seems to be this for Open Telemetry:
https://github.com/open-telemetry/opentelemetry-python
For Prometheus you'd just use the standard client librar
Re-posting as I did not get any response.
Thanks & Regards
Vinay Hegde
On Friday, December 3, 2021 at 1:13:00 PM UTC+5:30 vinay Hegde wrote:
> Hi Team,
> I need a help in getting instance status with time information when using
> blackbox exporter.
> Basically, I am using ICMP ping4 module to g
@Stuart: Thank you. Any reference to libraries which can do that. I am not
able to find any.
On Mon, Dec 13, 2021 at 2:07 AM Stuart Clark
wrote:
> On 13/12/2021 08:03, kiran wrote:
>
> All,
>
> 1. Clients' system is emitting metrics in Open telemetry format and
> pushing to a HTTP end point *on
On 13/12/2021 08:03, kiran wrote:
All,
1. Clients' system is emitting metrics in Open telemetry format and
pushing to a HTTP end point *on our side*.
*Note*:No control to change anything on the clients' side.
2. We need to transform the data received at the above end point into
prometheus ex
All,
1. Clients' system is emitting metrics in Open telemetry format and
pushing to a HTTP end point *on our side*.
*Note*:No control to change anything on the clients' side.
2. We need to transform the data received at the above end point into
prometheus exposition format(
https://prometheus.io/
22 matches
Mail list logo
