Source template feature for Timestamp parsing (#5552)

* Source template feature for Timestamp parsing

* Update otrmTimestampParsing.md

* Apply suggestions from code review

Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>

* comments incorporated

* Fix broken links

* Minor change to link text

* Replace otelcol timestamp /reuse reference (#5566)

* Replace otelcol timestamp /reuse reference

* cross-references

* Update docs/send-data/opentelemetry-collector/remote-management/source-templates/postgresql/index.md

* Update docs/send-data/opentelemetry-collector/remote-management/source-templates/rabbitmq/index.md

* Update docs/send-data/opentelemetry-collector/remote-management/source-templates/redis/index.md

* Update docs/send-data/opentelemetry-collector/remote-management/source-templates/otrm-time-reference.md

Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>

* Update docs/reuse/apps/opentelemetry/timestamp-parsing.md

Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>

---------

Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>

* Fixes from the comments PR:5566

* minor fixes

---------

Co-authored-by: Jagadisha V <[email protected]>
Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>
Co-authored-by: Jagadisha V <[email protected]>
Co-authored-by: Kim (Sumo Logic) <[email protected]>

Author: 4 people

docs/reuse/apps/opentelemetry/logs-advance-option-otel.md

@@ -0,0 +1 @@
+**Timestamp Parsing**. You can configure timestamp parsing for logs ingested using this source template. For more information, see [Timestamps, Time Zones, Time Ranges, and Date Formats for the OpenTelemetry Collector](/docs/send-data/opentelemetry-collector/remote-management/source-templates/otrm-time-reference).

docs/reuse/apps/opentelemetry/timestamp-parsing.md

@@ -77,9 +77,9 @@ In this step, you will configure the yaml required for Apache Collection. Below
 - **Error file log path**. Enter the path to the error log file for your Apache instance.
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default, sumo tags `_sourceCategory` with the value otel/apache user needs to provide the value for `webengine.cluster.name`.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 

docs/send-data/opentelemetry-collector/remote-management/source-templates/apache/index.md

@@ -77,9 +77,9 @@ In this step, you will configure the yaml required for Docker Collection. Below
 - **Excluded Image List**. A list of strings, [regexes](https://golang.org/pkg/regexp/), or [globs](https://github.com/gobwas/glob) whose referent container image names will not be among the queried containers for scrapping metrics. Learn more about [*excluded_images*](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/dockerstatsreceiver/README.md#configuration).
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default, Sumo Logic tags `_sourceCategory` with the value otel/docker.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 

docs/send-data/opentelemetry-collector/remote-management/source-templates/docker/index.md

@@ -71,16 +71,16 @@ import CollectorInstallation from '../../../../../reuse/apps/opentelemetry/colle
 In this step, you will configure the yaml required for Elasticsearch collection. Below are the inputs required for configuration:
 
 - **Name**. Name of the source template.
-- **Description**. Description for the source template.	
+- **Description**. Description for the source template.
 - **Log Filepath**. Location where the Elasticsearch logs are logged. Please refer to your elasticsearch.conf file.
 - **Endpoint**. Enter the url of the server you need to monitor. (default: `localhost:9200`).
 - **Username**. Enter the Elasticsearch username.
 - **Password Environment Variable Name**. Enter the Elasticsearch password environment variable name.
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default, Sumo Logic tags `_sourceCategory` with the value otel/elasticsearch user needs to provide the value for `db.cluster.name`.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 
@@ -92,4 +92,4 @@ import DataConfiguration from '../../../../../reuse/apps/opentelemetry/data-conf
 
 :::info
 Refer to the [changelog](changelog.md) for information on periodic updates to this source template.
-:::
+:::

docs/send-data/opentelemetry-collector/remote-management/source-templates/elasticsearch/index.md

@@ -86,4 +86,15 @@ In this section, we'll show you how to set up source templates for the following
       <a href="/docs/send-data/opentelemetry-collector/remote-management/source-templates/windows"><img src={useBaseUrl('img/integrations/microsoft-azure/windows.png')} alt="Thumbnail icon" width="30"/><h4>Windows</h4></a><p>Learn how to configure our OTel Windows source template.</p>
     </div>
   </div>
+
+  <div className="box smallbox card">
+    <div className="container">
+      <a href="/docs/send-data/opentelemetry-collector/remote-management/source-templates/otrm-time-reference"><img src={useBaseUrl('img/send-data/otel-color.svg')} alt="Thumbnail icon" width="30"/><h4>Timestamps, Time Zones, and Date Formats</h4></a><p>Learn how Sumo Logic manages timestamps, time zones, and dates.</p>
+    </div>
+  </div>
+  <div className="box smallbox card">
+    <div className="container">
+      <a href="/docs/send-data/opentelemetry-collector/remote-management/source-templates/st-with-secrets"><img src={useBaseUrl('img/send-data/otel-color.svg')} alt="Thumbnail icon" width="30"/><h4>Setting Environment Variables with Secret Values for Source Templates</h4></a><p>Learn about the steps for setting environment variable with secret value.</p>
+    </div>
+  </div>
 </div>

docs/send-data/opentelemetry-collector/remote-management/source-templates/index.md

@@ -68,9 +68,9 @@ In this step, you will configure the yaml required for Kafka collection. Below a
 - **Endpoint**. The URL of the broker endpoint (default: `localhost:9092`).
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default, Sumo Logic tags `_sourceCategory` with the value otel/kafka user needs to provide the value for `webengine.cluster.name`.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 

docs/send-data/opentelemetry-collector/remote-management/source-templates/kafka/index.md

@@ -55,9 +55,9 @@ In this step, you will configure the yaml required for Local File collection. Be
 - **Collection should begin from**. Defines where will the collection of the logs start from. Possible values are "End of File" and "Beginning of File".
 - **Detect messages spanning multiple lines**. You can enable this option when dealing with logs which span over multiple lines. On enabling this option you will need to specify **Boundary regex location** where you can specify if the expression defines end or start of the log line and **Expression to match message boundary** where you will define the expression.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add processing rules for logs collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 

docs/send-data/opentelemetry-collector/remote-management/source-templates/localfile/index.md

@@ -80,17 +80,17 @@ import CollectorInstallation from '../../../../../reuse/apps/opentelemetry/colle
 In this step, you will configure the yaml required for MySQL collection. Below are the inputs required for configuration:
 
 - **Name**. Name of the source template.
-- **Description**. Description for the source template.	
+- **Description**. Description for the source template.
 - **Error log path**. Location where the SQL Errors are logged. Please refer to your my.cnf file.
 - **Slow Transaction log file path (optional)**. Location where the Slow SQL transactions are logged. Please refer to your my.cnf file.
 - **Endpoint**. The URL of the MySQL endpoint (default: `localhost:3306`).
 - **Username**. Enter the MySQL username.
 - **Password Environment Variable Name**. Enter the MySQL password environment variable name.
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default, Sumo Logic tags `_sourceCategory` with the value otel/mysql user needs to provide the value for `db.cluster.name`.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).
 
@@ -102,4 +102,4 @@ import DataConfiguration from '../../../../../reuse/apps/opentelemetry/data-conf
 
 :::info
 Refer to the [changelog](changelog.md) for information on periodic updates to this source template.
-:::
+:::

docs/send-data/opentelemetry-collector/remote-management/source-templates/mysql/index.md

@@ -76,9 +76,9 @@ In this step, you will configure the yaml required for Nginx collection. Below a
 - **Path to Nginx error Log file**. Enter the path to the error log file for your Nginx instance.
 - **Fields/Metadata**. You can provide any customer fields to be tagged with the data collected. By default sumo tags `_sourceCategory` with the value otel/nginx user needs to provide the value for `webengine.cluster.name`.
 
-import OtelLogAdvanceOption from '../../../../../reuse/apps/opentelemetry/logs-advance-option-otel.md';
+import TimestampParsing from '../../../../../reuse/apps/opentelemetry/timestamp-parsing.md';
 
-<OtelLogAdvanceOption/>
+<TimestampParsing/>
 
 **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](../../processing-rules/index.md).