elastic / elastic/integrations
google_workspace: make request tracing configuration per-data stream
Open
enhancement
Integration:google_workspace
Team:Security-Service Integrations
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 225
Description
When debugging a data stream in the google_workspace integration, it can be useful to enable request trace logging. However, this configuration acts across the package, meaning that irrelevant requests will contaminate the trace logs. Worse, the logs will rollover at a great rate due to the number of data streams in the package.
This is probably true for other packages as well.
We should make the configuration per-data stream.
Contributor guide
Assessment
This issue has not been assessed yet.