Skeleton

Author: aurbiztondo-splunk

_includes/gdi/collector-available-processors.rst

@@ -24,9 +24,12 @@
    * - :ref:`kubernetes-attributes-processor` (``k8sattributes``)
      - Allows automatic tagging of spans, metrics, and logs with Kubernetes metadata. Formerly known as ``k8s_tagger``.
      - Metrics, logs, traces
-   * - :ref:`memory-limiter-processor` (``memory_limiter``) 
+   * - :ref:`memory-limiter-processor` (``memory_limiter``)   
      - Prevents out of memory situations on the Splunk Distribution of OpenTelemetry Collector.
      - Metrics, logs, traces
+   * - :ref:`metrics-generation-processor` (``metricsgeneration``) 
+     - Creates new metrics using existing metrics following a given rule.
+     - Metrics
    * - :ref:`metrics-transform-processor` (``metricstransform``) 
      - Renames metrics, and adds, renames, or deletes label keys and values.
      - Metrics

gdi/opentelemetry/components/a-components-processors.rst

@@ -18,6 +18,7 @@ Collector components: Processors
     groupbyattrs-processor
     kubernetes-attributes-processor
     memory-limiter-processor
+    metrics-generation-processor    
     metrics-transform-processor
     probabilistic-sampler-processor
     redaction-processor
@@ -30,7 +31,7 @@ Collector components: Processors
 
 The Splunk Distribution of the OpenTelemetry Collector includes and supports the processors listed on this doc. To see other components, refer to :ref:`otel-components`.
 
-.. note:: The following list might not contain all the latest additions. For a complete list of Collector components, including components that aren't included in the Splunk Distribution of OpenTelemetry Collector, see the ``opentelemetry-contrib`` repository in GitHub.
+.. note:: The following list might not contain all the latest additions. For a complete list of Collector components, including components that aren't included in the Splunk Distribution of the OpenTelemetry Collector, see the ``opentelemetry-contrib`` repository in GitHub.
 
 The following processors are available:
 

gdi/opentelemetry/components/metrics-generation-processor.rst

@@ -0,0 +1,85 @@
+.. _metrics-generation-processor:
+
+***********************************
+Metrics generation processor
+***********************************
+
+.. meta::
+      :description: Creates new metrics using existing metrics following a given rule.
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Metrics transform processor to creates new metrics using existing metrics following a given rule.
+
+
+
+
+Get started
+======================
+
+Follow these steps to configure and activate the component:
+
+1. Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
+
+  - :ref:`otel-install-linux`
+  - :ref:`otel-install-windows`
+  - :ref:`otel-install-k8s`
+
+2. Configure the ``metricsgeneration`` processor as described in the next section.
+3. Restart the Collector.
+
+Sample configuration
+--------------------------------------------
+
+To activate the resource processor, add ``metricsgeneration`` to the ``processors`` section of your configuration file. 
+
+For example:
+
+.. code-block:: yaml
+
+  processors:
+    metricsgeneration:
+
+To complete the configuration, include the processor in the ``metrics`` pipeline of the ``service`` section of your configuration file. For example:
+
+.. code-block:: yaml
+
+  service:
+    pipelines:
+      metrics:
+        processors: [metricsgeneration]
+
+.. _metrics-generation-processor-config-example:
+
+Configuration example
+----------------------------------
+
+
+.. _metrics-generation-processor-settings:
+
+Settings
+======================
+
+The following table shows the configuration options for the ``metricstransform`` processor:
+
+.. raw:: html
+
+  <div class="metrics-standard" category="included" url="https://raw.githubusercontent.com/splunk/collector-config-tools/main/cfg-metadata/processor/metricstransform.yaml"></div>
+
+Troubleshooting
+======================
+
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
+.. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
+
+