* Refactor config: pipelines now under service
This change moves 'pipelines' sections from the top level to under the 'service' section.
* Fix typo in old comment
* Use strict mode to read config
Reading the config using exact matches causes errors for unknown sections reducing the changes of accidental errors on the configuration files.
* Add comments and fix testbed config files
* Refactor extensions to new config format
* Refactored PProf
* Refactor health-check extension
* Refactor service application for extensions
* Refactor zPages and update docker compose example
* Fix staticcheck issue
* Update README and other comments/docs
* Remove tabs from yaml in extension/README.md
* Remove closeFn field from service and related functions
* PR Feedback 00
* Add doc.go to extensiontest package
* Move getAvailablePort to testutils package
* Add tests for testutils functions getting available endpoints
- Problem to solve: Logging exporter outputs received
traces/metrics to the stdout. The existing implementation
uses the same log level as the otel process. So if the otel
process uses info log level, the user can not see more verbose
logging message via the logging exporter on the console.
- Solution: use sperate zap loggers for exporters used in different
pipelines.
- Use case: (1) as describe above.(2) Later more log messages
could be added to the logging_exporter.go in different
log levels, which could be configurable. (3) Setting
different log levels for loggers in different pipelines.
process. With this approach, users can configures the log level
of the logging exporter. In additon, messages in the exporter
could appear according to the level in the configuration
file.
Co-Authored-By: Yang Song <songy23@users.noreply.github.com>
Signed-off-by: Hui Kang <kangh@us.ibm.com>
Ian Quick
huikang
Paulo Janotti
Tigran Najaryan
Iñigo