Re: [prometheus-users] collect non-metrics data

2023-02-13 Thread Christoph Anton Mitterer
Hey Ben.

On Saturday, February 11, 2023 at 11:18:44 AM UTC+1 Ben Kochie wrote:

You combine this with an "info" metric that tells you about the rest of the 
device.

Ah,... and I assume that one could just also export these info metrics 
alongside e.g. node_md_state?

Thanks :-)
Chris.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/d3abe98c-6b2b-4471-a981-8b99936b7dd4n%40googlegroups.com.


Re: [prometheus-users] Document recording rules

2023-02-13 Thread sayf.eddi...@gmail.com
Done https://github.com/prometheus/prometheus/issues/11969

Thanks

On Monday, February 13, 2023 at 3:37:12 PM UTC+1 Ben Kochie wrote:

> That's a very interesting idea. I don't think that's possible right now. 
> But maybe file a feature request on github?
>
> On Mon, Feb 13, 2023 at 3:27 PM sayf.eddi...@gmail.com <
> sayf.eddi...@gmail.com> wrote:
>
>> Hello,
>>
>> I am working on adding recording rules. But I dont see how to document 
>> them in the code.
>> We have `HELP` entry for metrics, `description` and `summary` for alerts. 
>> what about recording rules?
>>
>> Best regards
>>
>> -- 
>> 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-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/prometheus-users/9cb12679-6585-4340-bd28-b045f5237fcdn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/bd5701da-750e-4ddb-9559-c241b549201bn%40googlegroups.com.


Re: [prometheus-users] Document recording rules

2023-02-13 Thread Ben Kochie
That's a very interesting idea. I don't think that's possible right now.
But maybe file a feature request on github?

On Mon, Feb 13, 2023 at 3:27 PM sayf.eddi...@gmail.com <
sayf.eddine.hamm...@gmail.com> wrote:

> Hello,
>
> I am working on adding recording rules. But I dont see how to document
> them in the code.
> We have `HELP` entry for metrics, `description` and `summary` for alerts.
> what about recording rules?
>
> Best regards
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-users/9cb12679-6585-4340-bd28-b045f5237fcdn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/CABbyFmpUHiY4iJB3Pju5AFU7Bu2oo0j5RD7mck65i8RS_bhQXg%40mail.gmail.com.


[prometheus-users] Document recording rules

2023-02-13 Thread sayf.eddi...@gmail.com
Hello,

I am working on adding recording rules. But I dont see how to document them 
in the code.
We have `HELP` entry for metrics, `description` and `summary` for alerts. 
what about recording rules?

Best regards

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/9cb12679-6585-4340-bd28-b045f5237fcdn%40googlegroups.com.


Re: [prometheus-users] 404 Error as prometheus adds a port 443 to my aws app runner domain

2023-02-13 Thread V P
Thanks for the quick reply Stuart, here i am facing an error with app 
runner domain i.e my app runner service don't include any port in its URL 
its simply https://example.apprunner.com when m using it with prometheus 
i.e  https://example.apprunner.com/actuator/prometheus , it taking a 
default port 443 at  https://example.apprunner.com:443 and thus throwing a 
404 error as that's not my actual URL ( 
https://example.apprunner.com/actuator/prometheus  )

On Monday, 13 February 2023 at 17:46:39 UTC+5:30 Stuart Clark wrote:

> On 13/02/2023 09:16, V P wrote:
> > We want to scrape a https app runner domain without a port number and 
> > the Prometheus configuration is according to that. Is there a way to 
> > prevent the default port number for https(443) to get applied in the 
> > domain name of app runner when the Prometheus targets the https domain?
> >
> > As my domain https://app-runner.com/actuator/prometheus gets converted 
> to
> > https://app-runner.com:443/actuator/prometheus in the targets and 
> > gives a 404 error due to the addition on port number in url.
> >
> > I changed the scheme to https, tried adding 443 port in target field 
> > of yml config file as well still getting the same error 404
>
> I'm not quite sure what you are meaning by "without a port number"? All 
> connections are to a specific port. If you don't specify a port when 
> doing a web request it will default to 80 or 443 (depending on if it is 
> HTTP or HTTPS).
>
> -- 
> Stuart Clark
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/204c5439-842e-4cd7-870c-794c4b87db54n%40googlegroups.com.


[prometheus-users] Prometheus config not able to scrape through https app runner domain

2023-02-13 Thread Vedant Yerpude
How to scrape through the https app runner domain without providing the 
port number?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/50bb6e32-be78-434d-946d-6d1407972481n%40googlegroups.com.


Re: [prometheus-users] 404 Error as prometheus adds a port 443 to my aws app runner domain

2023-02-13 Thread Stuart Clark

On 13/02/2023 09:16, V P wrote:
We want to scrape a https app runner domain without a port number and 
the Prometheus configuration is according to that. Is there a way to 
prevent the default port number for https(443) to get applied in the 
domain name of app runner when the Prometheus targets the https domain?


As my domain https://app-runner.com/actuator/prometheus gets converted to
https://app-runner.com:443/actuator/prometheus in the targets and 
gives a 404 error due to the addition on port number in url.


I changed the scheme to https, tried adding 443 port in target field 
of yml config file as well still getting the same error 404


I'm not quite sure what you are meaning by "without a port number"? All 
connections are to a specific port. If you don't specify a port when 
doing a web request it will default to 80 or 443 (depending on if it is 
HTTP or HTTPS).


--
Stuart Clark

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/2f842031-0a26-3c52-53c2-925cdeee7f09%40Jahingo.com.


[prometheus-users] Exporting Prometheus metrics from locally to AWS managed Prometheus

2023-02-13 Thread Pradumn Mishra
Hi,
I am currently creating a local Prometheus server and able to scap metrics 
using opentelemetry agent. The metrics are also opentelemetry metrics. I 
want to implement the same into AWS managed Prometheus so that my local 
metrics are pushed there.
Is there any reference or documentation for the same because I could not 
find it.
The language I am using for opentelemetry application is C#.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/948aa3a8-7c94-4eb4-9b73-1846a9417ce0n%40googlegroups.com.


[prometheus-users] Prometheus certificates issue

2023-02-13 Thread Vedant Yerpude
how to supply the certiifcates in prometheus docker?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/46a57bf0-4de7-4a52-9832-9320105db415n%40googlegroups.com.


[prometheus-users] How to supply the certificates in prometheus docker

2023-02-13 Thread V P
Is there a way to add security certificates in Prometheus config from 
docker so as to avoid the https port number to get added in my target 
domain so I wont be getting a *404 error* in Prometheus.

my domain : *https://app-runner.com/actuator/prometheus*

instance created : *https://app-runner.com:443/actuator/prometheus *as 443 
gets added here I get 404 error and my state is DOWN

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/7cf15363-0069-436c-86d5-9579e470f380n%40googlegroups.com.


Re: [prometheus-users] Csv file import and scrape metrics into Prometheus

2023-02-13 Thread Pradumn Mishra
I have a similar usecase where I have json files with metrics which also 
has Timestamps (string format). Do I need to  backfill the data into 
prometheus or write a exporter. I have tried the latter. so a sample of my 
data has :
{some attributes (including timestamp)} value
I used the observable gauge using Measurment in C#. 
But the metric I am getting in prometheus is like this:
metric_name{attribute1:attribute1_value, 
.timestamp:timestamp_value} value timestamp
I want the my timestamp_value present in the attribute to be the actual 
timestamp of the prometheus and not the current timestamp recorded by 
prometheus. Any suggestions???

On Friday, 9 September, 2022 at 7:04:36 pm UTC+5:30 Olivier Harand wrote:

> Hello everyone, 
>
> In a personal small lab, i remember that i did convert a CSV to SQlite, 
> then used one of the SQL / Query exporter available to move the data to 
> Prometheus. So i could trace the changes, evolution over time, requesting 
> data with promQL in Grafana Dashboards. 
>
> If you are not interested in viewing the changes over time, better use a 
> SQLite or even CSV datasource in Grafana. 
>
> Have a good day ! 
>
> Le ven. 9 sept. 2022 à 12:19, Shruthi P  a écrit :
>
>> Hi All, 
>> I have a csv and yaml file with some data. I want prometheus to monitor 
>> the data and add metrics for the data to finally use it in grafana for 
>> visualization /
>> Please give pointers there
>>
>> -- 
>> 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-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/prometheus-users/70d0b2b8-814e-4f51-8388-d24701c968bfn%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
>  
>
> Olivier Harand
>
> Chief Monitoring Officer
>
> +33012028
> +33783296234
> olivier...@outscale.com
> 319 Bureaux de la Colline - 92210 Saint-Cloud
>
> 
> 
> 
>
> IMPORTANT : The information contained in this message may be privileged 
> and confidential and
> protected from disclosure. If the reader of this message is not the 
> intended recipient, or
> an employee or agent responsible for delivering this message to the 
> intended recipient, you
> are hereby notified that any dissemination, distribution or copying of 
> this communication is
> strictly prohibited. If you have received this communication in error, 
> please notify us immediately
> by replying to the message and deleting it from your computer.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/402c0ce7-3a9a-4679-97fe-851c1a16d4c0n%40googlegroups.com.


[prometheus-users] 404 Error as prometheus adds a port 443 to my aws app runner domain

2023-02-13 Thread V P
We want to scrape a https app runner domain without a port number and the 
Prometheus configuration is according to that. Is there a way to prevent 
the default port number for https(443) to get applied in the domain name of 
app runner when the Prometheus targets the https domain?

As my domain https://app-runner.com/actuator/prometheus gets converted to 
https://app-runner.com:443/actuator/prometheus in the targets and gives a 
404 error due to the addition on port number in url.

I changed the scheme to https, tried adding 443 port in target field of yml 
config file as well still getting the same error 404

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/bc79294c-cf35-47fb-9365-fcf2729f6e92n%40googlegroups.com.