-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Profiler: Go agent should not collect disabled profile types #2835
Copy link
Copy link
Closed
Labels
api: cloudprofilerIssues related to the Cloud Profiler API.Issues related to the Cloud Profiler API.lang: goIssues specific to Go.Issues specific to Go.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
api: cloudprofilerIssues related to the Cloud Profiler API.Issues related to the Cloud Profiler API.lang: goIssues specific to Go.Issues specific to Go.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Client
Profiler
Environment
Any
Go Environment
$ go version any
Expected behavior
If Profiler agent is started with certain profile types disabled, those profile types should not be collected.
Actual behavior
Profiler agent collects disabled profile types. It should not.