Remove pprofextension, moved to contrib

cmd/otelcol/config.yaml

@@ -1,6 +1,6 @@
 extensions:
-  pprof:
-    endpoint: 0.0.0.0:1777
+  memory_ballast:
+    size_mib: 512
   zpages:
     endpoint: 0.0.0.0:55679
 
@@ -31,4 +31,4 @@ service:
       processors: [batch]
       exporters: [logging]
 
-  extensions: [pprof, zpages]
+  extensions: [memory_ballast, zpages]

examples/local/otel-config.yaml

@@ -1,6 +1,6 @@
 extensions:
-  pprof:
-    endpoint: 0.0.0.0:1777
+  memory_ballast:
+    size_mib: 512
   zpages:
     endpoint: 0.0.0.0:55679
 
@@ -34,4 +34,4 @@ service:
       processors: [memory_limiter, batch]
       exporters: [logging]
 
-  extensions: [pprof, zpages]
+  extensions: [memory_ballast, zpages]

extension/README.md

@@ -10,8 +10,7 @@ performance profile.
 
 Supported service extensions (sorted alphabetically):
 
-- [Health Check](healthcheckextension/README.md)
-- [Performance Profiler](pprofextension/README.md)
+- [Memory Ballast](ballastextension/README.md)
 - [zPages](zpagesextension/README.md)
 
 The [contributors
@@ -29,79 +28,5 @@ will be shutdown. The ordering is determined in the `extensions` tag under the
 service:
   # Extensions specified below are going to be loaded by the service in the
   # order given below, and shutdown on reverse order.
-  extensions: [health_check, pprof, zpages]
+  extensions: [memory_ballast, zpages]
 ```
-
-# Extensions
-
-## <a name="health_check"></a>Health Check
-Health Check extension enables an HTTP url that can be probed to check the
-status of the OpenTelemetry Collector. This extension can be used as a
-liveness and/or readiness probe on Kubernetes.
-
-The following settings are required:
-
-- `port` (default = 13133): What port to expose HTTP health information.
-
-Example:
-
-```yaml
-extensions:
-  health_check:
-```
-
-The full list of settings exposed for this exporter is documented [here](healthcheckextension/config.go)
-with detailed sample configurations [here](healthcheckextension/testdata/config.yaml).
-
-## <a name="pprof"></a>Performance Profiler
-
-Performance Profiler extension enables the golang `net/http/pprof` endpoint.
-This is typically used by developers to collect performance profiles and
-investigate issues with the service.
-
-The following settings are required:
-
-- `endpoint` (default = localhost:1777): The endpoint in which the pprof will
-be listening to.
-- `block_profile_fraction` (default = 0): Fraction of blocking events that
-are profiled. A value <= 0 disables profiling. See
-https://golang.org/pkg/runtime/#SetBlockProfileRate for details.
-- `mutex_profile_fraction` (default = 0): Fraction of mutex contention
-events that are profiled. A value <= 0 disables profiling. See
-https://golang.org/pkg/runtime/#SetMutexProfileFraction for details.
-
-The following settings can be optionally configured:
-
-- `save_to_file`: File name to save the CPU profile to. The profiling starts when the
-Collector starts and is saved to the file when the Collector is terminated.
-
-Example:
-
-```yaml
-extensions:
-  pprof:
-```
-
-The full list of settings exposed for this exporter are documented [here](pprofextension/config.go)
-with detailed sample configurations [here](pprofextension/testdata/config.yaml).
-
-## <a name="zpages"></a>zPages
-
-Enables an extension that serves zPages, an HTTP endpoint that provides live
-data for debugging different components that were properly instrumented for such.
-All core exporters and receivers provide some zPages instrumentation.
-
-The following settings are required:
-
-- `endpoint` (default = localhost:55679): Specifies the HTTP endpoint that serves
-zPages.
-
-Example:
-
-```yaml
-extensions:
-  zpages:
-```
-
-The full list of settings exposed for this exporter are documented [here](zpagesextension/config.go)
-with detailed sample configurations [here](zpagesextension/testdata/config.yaml).