Scrape Job Timeout Not Honoring Configured Timeout Values

[gamegha]

Report

Even after configuring mutexTimeout, scrapeTimeout, and scrapeJobTimeout in runtime.yaml, the Promitor Scraper Agent consistently cancels scrape jobs after 90 seconds. This suggests that the timeout is either hardcoded or the configuration is not being respected.

Promitor Scraper Agent version: 2.14.1
Deployment method: Docker Compose
Runtime config: runtime.yaml mounted via volume

[ERR] Scrape job ... was cancelled due to timeout.
[INF] Timeout after 90

[13:34:00 INF] Timeout after 90
[13:34:00 INF] Init timeout token
[13:34:37 ERR] Scrape job ... was cancelled due to timeout.

unable to scrape the metrics, to test the functionality tested for only 1 metrics which also timed out.

Thanks,
Ganesh Singh

Expected Behavior

Expected behavior
Scrape jobs should respect the configured scrapeJobTimeout and not be cancelled after 90 seconds.

Actual Behavior

[ERR] Scrape job ... was cancelled due to timeout.
[INF] Timeout after 90
[13:34:00 INF] Timeout after 90
[13:34:00 INF] Init timeout token
[13:34:37 ERR] Scrape job ... was cancelled due to timeout.

Steps to Reproduce the Problem

Promitor Scraper Agent version: 2.14.1
Deployment method: Docker Compose
Runtime config: runtime.yaml mounted via volume

Component

Scraper

Version

2.14.1

Configuration

Configuration:

# Add your scraping configuration here

runtime.yaml

runtime:
scraping:
mutexTimeout: 00:04:00
scrapeTimeout: 00:02:00
scrapeJobTimeout: 00:03:00

Logs

example

Platform

None

Contact Details

No response

[github-actions]

Thank you for opening an issue! We rely on the community to maintain Promitor. (Learn more)

Is this something you want to contribute?

[gamegha]

with this error only 0 and 1 values are scarping not the actual which we have for metrics.