Renamed data prepper files to have dashes for consistency (#7790)

* Renamed data prepper files to have dashes for consistency Signed-off-by: Fanit Kolchina <[email protected]> * More files Signed-off-by: Fanit Kolchina <[email protected]> --------- Signed-off-by: Fanit Kolchina <[email protected]>
opensearch-project · Aug 2, 2024 · 76a29ff · 76a29ff
1 parent 8a321e5
commit 76a29ff
Show file tree

Hide file tree

Showing 21 changed files with 10 additions and 10 deletions.
diff --git a/_data-prepper/common-use-cases/log-enrichment.md b/_data-prepper/common-use-cases/log-enrichment.md
@@ -370,7 +370,7 @@ The `date` processor can generate timestamps for incoming events if you specify
 
 ### Deriving punctuation patterns
 
-The [`substitute_string`]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/substitute_string/) processor (which is one of the mutate string processors) lets you derive a punctuation pattern from incoming events. In the following example pipeline, the processor will scan incoming Apache log events and derive punctuation patterns from them:
+The [`substitute_string`]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/substitute-string/) processor (which is one of the mutate string processors) lets you derive a punctuation pattern from incoming events. In the following example pipeline, the processor will scan incoming Apache log events and derive punctuation patterns from them:
 
 ```yaml
 processor:  

diff --git a/_data-prepper/common-use-cases/trace-analytics.md b/_data-prepper/common-use-cases/trace-analytics.md
@@ -32,7 +32,7 @@ To monitor trace analytics in Data Prepper, we provide three pipelines: `entry-p
 
 ### OpenTelemetry trace source
 
-The [OpenTelemetry source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel_traces/) accepts trace data from the OpenTelemetry Collector. The source follows the [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-specification/tree/master/specification/protocol) and officially supports transport over gRPC and the use of industry-standard encryption (TLS/HTTPS).
+The [OpenTelemetry source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel-traces/) accepts trace data from the OpenTelemetry Collector. The source follows the [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-specification/tree/master/specification/protocol) and officially supports transport over gRPC and the use of industry-standard encryption (TLS/HTTPS).
 
 ### Processor
 
@@ -49,8 +49,8 @@ OpenSearch provides a generic sink that writes data to OpenSearch as the destina
 
 The sink provides specific configurations for the trace analytics feature. These configurations allow the sink to use indexes and index templates specific to trace analytics. The following OpenSearch indexes are specific to trace analytics:
 
-* otel-v1-apm-span –- The *otel-v1-apm-span* index stores the output from the [otel_traces_raw]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel_traces/) processor.
-* otel-v1-apm-service-map –- The *otel-v1-apm-service-map* index stores the output from the [service_map_stateful]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/service_map/) processor.
+* otel-v1-apm-span –- The *otel-v1-apm-span* index stores the output from the [otel_traces_raw]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel-traces/) processor.
+* otel-v1-apm-service-map –- The *otel-v1-apm-service-map* index stores the output from the [service_map_stateful]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/service-map/) processor.
 
 ## Trace tuning
 

diff --git a/...-data-prepper/extensions/geoip_service.md → ...-data-prepper/extensions/geoip-service.md b/...-data-prepper/extensions/geoip_service.md → ...-data-prepper/extensions/geoip-service.md
diff --git a/...guration/processors/convert_entry_type.md → ...guration/processors/convert-entry-type.md b/...guration/processors/convert_entry_type.md → ...guration/processors/convert-entry-type.md
diff --git a/...onfiguration/processors/delete_entries.md → ...onfiguration/processors/delete-entries.md b/...onfiguration/processors/delete_entries.md → ...onfiguration/processors/delete-entries.md
diff --git a/_data-prepper/pipelines/configuration/processors/geoip.md b/_data-prepper/pipelines/configuration/processors/geoip.md
@@ -10,7 +10,7 @@ nav_order: 49
 
 The `geoip` processor enriches events with geographic information extracted from IP addresses contained in the events.
 By default, Data Prepper uses the [MaxMind GeoLite2](https://dev.maxmind.com/geoip/geolite2-free-geolocation-data) geolocation database.
-Data Prepper administrators can configure the databases using the [`geoip_service`]({{site.url}}{{site.baseurl}}/data-prepper/managing-data-prepper/extensions/geoip_service) extension configuration.
+Data Prepper administrators can configure the databases using the [`geoip_service`]({{site.url}}{{site.baseurl}}/data-prepper/managing-data-prepper/extensions/geoip-service/) extension configuration.
 
 ## Usage
 

diff --git a/_data-prepper/pipelines/configuration/processors/mutate-event.md b/_data-prepper/pipelines/configuration/processors/mutate-event.md
@@ -11,9 +11,9 @@ nav_order: 65
 Mutate event processors allow you to modify events in Data Prepper. The following processors are available:
 
 * [add_entries]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/add-entries/) allows you to add entries to an event.
-* [convert_entry_type]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/convert_entry_type/) allows you to convert value types in an event.
+* [convert_entry_type]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/convert-entry-type/) allows you to convert value types in an event.
 * [copy_values]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/copy-values/) allows you to copy values within an event.
-* [delete_entries]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/delete_entries/) allows you to delete entries from an event.
+* [delete_entries]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/delete-entries/) allows you to delete entries from an event.
 * [list_to_map]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/list-to-map) allows you to convert list of objects from an event where each object contains a `key` field into a map of target keys.
 * `map_to_list` allows you to convert a map of objects from an event, where each object contains a `key` field, into a list of target keys.
 * [rename_keys]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/rename-keys/) allows you to rename keys in an event.

diff --git a/.../configuration/processors/otel_metrics.md → .../configuration/processors/otel-metrics.md b/.../configuration/processors/otel_metrics.md → .../configuration/processors/otel-metrics.md
diff --git a/...s/configuration/processors/otel_traces.md → ...s/configuration/processors/otel-traces.md b/...s/configuration/processors/otel_traces.md → ...s/configuration/processors/otel-traces.md
diff --git a/...nes/configuration/processors/parse_ion.md → ...nes/configuration/processors/parse-ion.md b/...nes/configuration/processors/parse_ion.md → ...nes/configuration/processors/parse-ion.md
diff --git a/...es/configuration/processors/parse_json.md → ...es/configuration/processors/parse-json.md b/...es/configuration/processors/parse_json.md → ...es/configuration/processors/parse-json.md
diff --git a/...nes/configuration/processors/parse_xml.md → ...nes/configuration/processors/parse-xml.md b/...nes/configuration/processors/parse_xml.md → ...nes/configuration/processors/parse-xml.md
diff --git a/...s/configuration/processors/service_map.md → ...s/configuration/processors/service-map.md b/...s/configuration/processors/service_map.md → ...s/configuration/processors/service-map.md
diff --git a/.../configuration/processors/split_string.md → .../configuration/processors/split-string.md b/.../configuration/processors/split_string.md → .../configuration/processors/split-string.md
diff --git a/...figuration/processors/string_converter.md → ...figuration/processors/string-converter.md b/...figuration/processors/string_converter.md → ...figuration/processors/string-converter.md
diff --git a/...iguration/processors/substitute_string.md → ...iguration/processors/substitute-string.md b/...iguration/processors/substitute_string.md → ...iguration/processors/substitute-string.md
diff --git a/...s/configuration/processors/trim_string.md → ...s/configuration/processors/trim-string.md b/...s/configuration/processors/trim_string.md → ...s/configuration/processors/trim-string.md
diff --git a/...es/configuration/processors/write_json.md → ...es/configuration/processors/write-json.md b/...es/configuration/processors/write_json.md → ...es/configuration/processors/write-json.md
diff --git a/_data-prepper/pipelines/configuration/sources/s3.md b/_data-prepper/pipelines/configuration/sources/s3.md
@@ -138,7 +138,7 @@ The `codec` determines how the `s3` source parses each Amazon S3 object. For inc
 
 ### `newline` codec
 
-The `newline` codec parses each single line as a single log event. This is ideal for most application logs because each event parses per single line. It can also be suitable for S3 objects that have individual JSON objects on each line, which matches well when used with the [parse_json]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/parse_json/) processor to parse each line.
+The `newline` codec parses each single line as a single log event. This is ideal for most application logs because each event parses per single line. It can also be suitable for S3 objects that have individual JSON objects on each line, which matches well when used with the [parse_json]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/parse-json/) processor to parse each line.
 
 Use the following options to configure the `newline` codec.
 

diff --git a/_ingest-pipelines/processors/convert.md b/_ingest-pipelines/processors/convert.md
@@ -7,7 +7,7 @@ redirect_from:
    - /api-reference/ingest-apis/processors/convert/
 ---
 
-This documentation describes using the `convert` processor in OpenSearch ingest pipelines. Consider using the [Data Prepper `convert_entry_type` processor]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/convert_entry_type/), which runs on the OpenSearch cluster, if your use case involves large or complex datasets.
+This documentation describes using the `convert` processor in OpenSearch ingest pipelines. Consider using the [Data Prepper `convert_entry_type` processor]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/convert-entry-type/), which runs on the OpenSearch cluster, if your use case involves large or complex datasets.
 {: .note}
 
 # Convert processor

diff --git a/_observing-your-data/trace/ta-dashboards.md b/_observing-your-data/trace/ta-dashboards.md
@@ -48,7 +48,7 @@ The **Trace Analytics** application includes two options: **Services** and **Tra
 The plugin requires you to use [Data Prepper]({{site.url}}{{site.baseurl}}/data-prepper/) to process and visualize OTel data and relies on the following Data Prepper pipelines for OTel correlations and service map calculations:
 
 - [Trace analytics pipeline]({{site.url}}{{site.baseurl}}/data-prepper/common-use-cases/trace-analytics/)
-- [Service map pipeline]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/service_map/)
+- [Service map pipeline]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/service-map/)
 
 ### Standardized telemetry data