ethereum-address-metrics-exporter: raise ServiceMonitor interval #311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eskp
force-pushed
the
address-exporter-interval
branch
from
9d994a7
to
79de2d0
Compare
added 2 commits
May 29, 2024 10:24
|
Hey @eskp . Sorry for the super late reply 🙏 Can you run |
|
Done thanks @skylenet |
skylenet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Default chart value for
ServiceMonitorconfig is set withintervalless thanscrapeTimeout, which Grafana Alloy doesn't like:ts=2024-05-28T23:57:50.491815865Z level=error msg="error generating scrapeconfig from serviceMonitor" component_path=/ component_id=prometheus.operator.servicemonitors.service_monitors name=mainnet-mon-exporter err="scrape timeout greater than scrape interval for scrape config with job name \"serviceMonitor/default/mainnet-mon-exporter/0\""