If you just need to know the scrape timestamps, you can query each
Prometheus instance like this:

up{instance="foo"}[1h]

This will return the timetsamps for each scrape over a given time range.

On Wed, Feb 16, 2022 at 2:11 AM kekr...@gmail.com <kekru...@gmail.com>
wrote:

> Stuart, I am not sure I understand the log files question.  I am not aware
> of any log files related to the scrape itself.  We do have log files
> related to the exporters running on the server but they do not capture the
> scrapes.  I am trying to get details of what is going on on the target
> server itself, not so concerned about what the Prometheus server has log
> wise.
>
> If you will add some more detail around the question, I will be glad to
> answer.
>
> On Tuesday, February 15, 2022 at 4:41:41 PM UTC-6 kekr...@gmail.com wrote:
>
>> I got the Grafana date problem solved and have the scrape time history
>> for the metric created - the info I needed.
>>
>> Thank you Stuart and Brian for the assistance.
>>
>> Kevin
>>
>> On Tuesday, February 15, 2022 at 4:32:02 PM UTC-6 Stuart Clark wrote:
>>
>>> On 15/02/2022 22:29, kekr...@gmail.com wrote:
>>> > I am not seeing the frequency is more often than I expect.  I am being
>>> > told a log file is being created by the scrapes in a temp directory
>>> > every minute.  I am saying it is not Prometheus. So now i have to
>>> > prove it is not Prometheus.
>>> >
>>> > As an alternate solution, I am trying to use the Prometheus timestamp
>>> > function on the metric being created by the scrape in Grafana to get
>>> > the time history of the metric as proof.  The thought being the time
>>> > difference between the metric history is 3 minutes.  But I am having
>>> > trouble getting the value of the timestamp function to act as an epoch
>>> > date.    If I use the value returned in a web epoch translator, it
>>> > translate to the correct date.  If I multiple the value by 1000, as
>>> > you do every epoch date in Grafana, it actually multiplies the value
>>> > rather than putting it in human readable date format.
>>> I'm not clear if you are getting logs from these requests or not? I'd
>>> expect any request logs to include the path being requested, time &
>>> source IP. What do you see?
>>>
>>> --
>>> 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/4fdc7c08-bbbf-40bc-a26c-c791337155c2n%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-users/4fdc7c08-bbbf-40bc-a26c-c791337155c2n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CABbyFmrgCAT%3D83%3Dba1mWCfQEHM2LqDj%2BVR6cNRYT8sYeJvuiDw%40mail.gmail.com.

Reply via email to