12 Commits (05356e76de82724ebf104457cb4cf1e91920621e)

Author	SHA1	Message	Date
Julien Pivotto	4b735f02a6	Merge pull request #10569 from zzJinux/discovery-manager-run ... Fix discovery managers to be properly cancelled	1 year ago
Julien Pivotto	009017a3fb	Revert "Remove deleted target from discovery manager" ... Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu>	1 year ago
haleyao	c5a37ddad5	Remove deleted target from discovery manager ... Signed-off-by: haleyao <haleyao@tencent.com>	1 year ago
Matthieu MOREL	bae9a21200	Merge branch 'main' into linter/nilerr ... Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>	2 years ago
beorn7	c3c7d44d84	lint: Adjust to the lint warnings raised by current versions of golint-ci ... We haven't updated golint-ci in our CI yet, but this commit prepares for that. There are a lot of new warnings, and it is mostly because the "revive" linter got updated. I agree with most of the new warnings, mostly around not naming unused function parameters (although it is justified in some cases for documentation purposes – while things like mocks are a good example where not naming the parameter is clearer). I'm pretty upset about the "empty block" warning to include `for` loops. It's such a common pattern to do something in the head of the `for` loop and then have an empty block. There is still an open issue about this: https://github.com/mgechev/revive/issues/810 I have disabled "revive" altogether in files where empty blocks are used excessively, and I have made the effort to add individual `// nolint:revive` where empty blocks are used just once or twice. It's borderline noisy, though, but let's go with it for now. I should mention that none of the "empty block" warnings for `for` loop bodies were legitimate. Signed-off-by: beorn7 <beorn@grafana.com>	2 years ago
Matthieu MOREL	fb3eb21230	enable gocritic, unconvert and unused linters ... Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>	2 years ago
Bryan Boreham	2f58be840d	service discovery: add config name to log messages ... This makes it easier to connect a log message with the config it relates to. Each SD config has a name, either the scrape job name or something like "config-0" for Alertmanager config. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 years ago
Matthieu MOREL	f43749e82f	refactor (discovery): move from github.com/pkg/errors to 'errors' and 'fmt' (#10807) ... Signed-off-by: Matthieu MOREL <mmorel-35@users.noreply.github.com> Co-authored-by: Matthieu MOREL <mmorel-35@users.noreply.github.com>	3 years ago
Jinwook Jeong	c7c7847b6f	Fix discovery managers to be properly cancelled ... Signed-off-by: Jinwook Jeong <vustthat@gmail.com>	3 years ago
Shihao Xia	d26fd5c97b	fix potential goroutine leaks (#10057) ... Signed-off-by: Shihao Xia <charlesxsh@hotmail.com>	3 years ago
Mateusz Gozdek	1a6c2283a3	Format Go source files using 'gofumpt -w -s -extra' ... Part of #9557 Signed-off-by: Mateusz Gozdek <mgozdekof@gmail.com>	3 years ago
Julien Pivotto	432005826d	Add a feature flag to enable the new discovery manager (#9537) ... * Add a feature flag to enable the new manager This PR creates a copy of the legacy manager and uses it by default. It is a companion PR to #9349. With this PR, users can enable the new discovery manager and provide us with any feedback / side effects that the new behaviour might have. Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>	3 years ago