-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chore] updating scrapers to use default method from scraperhelper #22138
Changes from 3 commits
d2ed9d9
77ac225
3794295
b070e52
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
# If your change doesn't affect end users, such as a test fix or a tooling change, | ||
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: breaking | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) | ||
component: receivers | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Updating receivers that run intervals to use standard interval by default | ||
|
||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. | ||
issues: [22138] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,9 +32,7 @@ func NewFactory() receiver.Factory { | |
|
||
func createDefaultConfig() component.Config { | ||
return &Config{ | ||
ScraperControllerSettings: scraperhelper.ScraperControllerSettings{ | ||
CollectionInterval: 10 * time.Second, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like this was missed and effectively the Apache receiver's default collection interval has changed from 10s to 60s? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shit, I can revert in a follow up PR. |
||
}, | ||
ScraperControllerSettings: scraperhelper.NewDefaultScraperControllerSettings(metadata.Type), | ||
HTTPClientSettings: confighttp.HTTPClientSettings{ | ||
Endpoint: defaultEndpoint, | ||
Timeout: 10 * time.Second, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,9 +31,7 @@ func NewFactory() receiver.Factory { | |
|
||
func createDefaultConfig() component.Config { | ||
return &Config{ | ||
ScraperControllerSettings: scraperhelper.ScraperControllerSettings{ | ||
CollectionInterval: defaultCollectionInterval, | ||
}, | ||
ScraperControllerSettings: scraperhelper.NewDefaultScraperControllerSettings(metadata.Type), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
TopMetricsQueryMaxRows: defaultTopMetricsQueryMaxRows, | ||
BackfillEnabled: defaultBackfillEnabled, | ||
HideTopnLockstatsRowrangestartkey: defaultHideTopnLockstatsRowrangestartkey, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
memcached: | ||
endpoint: "localhost:11211" | ||
collection_interval: 10s | ||
collection_interval: 1m |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
nginx: | ||
endpoint: "http://localhost:80/status" | ||
collection_interval: 10s | ||
collection_interval: 1m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still a breaking change?
If I understand correctly, the change in components' behavior is that they start scraping after 1 second and not after their default collection interval, is this right? In that case, I believe we should call it out in the release notes (using the
subtext
below?).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏽 , that makes sense but at this point this is a transparent change until the upstream is merged.
However, I think this missed thev0.78.0
release so we have time to fix this up.I can correct it in the next release with more details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment of mine is actually incorrect 🙂 Not until the core PR gets merged:
Looking at this PR again in detail, it wasn't (meant as) a breaking change, rather a refactoring. The only (accidental, I suppose) breaking change is that the Apache receiver's default collection interval has changed from 10s to 60s. This should probably be fixed in a future PR.