Move opentelemetry redis example to examples repository

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx

@@ -45,16 +45,16 @@ Refer to our
 [documentation and examples](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/opentelemetry-set-up-your-app)
 for monitoring service entities using OpenTelemetry.
 
-#### Required attributes
+#### Required attributes [#service-required-attributes]
 
 * [`service.name`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/service): The service name you see in the UI comes from this value.
 
-#### Recommended attributes [#recommended-attributes]
+#### Recommended attributes [#service-recommended-attributes]
 
 * [`service.instance.id`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/service): Enables faceting between multiple instances of the same service.
 * [`telemetry.sdk.language`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/telemetry): When present, this value drives the display of any runtime-specific UI, such as the JVM runtime page for Java applications.
 
-#### Entity tags [#entity-tags]
+#### Entity tags [#service-entity-tags]
 
 * [`service.namespace`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/service)
 * [`telemetry.sdk.language`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/telemetry) (added as language tag)
@@ -68,16 +68,14 @@ for monitoring service entities using OpenTelemetry.
 A host entity is synthesized by adhering to the OpenTelemetry resource semantic
 conventions describing a [host](https://opentelemetry.io/docs/specs/semconv/resource/host).
 
-Refer to our
-[documentation](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/opentelemetry-collector-infra-hosts)
-for monitoring host entities using the host metrics receiver for the OpenTelemetry collector.
+Refer to the host monitoring example in [collector for infrastructure monitoring](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/) for more details.
 
-#### Required attributes [#required-attributes]
+#### Required attributes [#host-required-attributes]
 
 * [`host.name`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/host): The host name you see in the UI comes from this value.
 * [`host.id`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/host)
 
-#### Entity tags [#entity-tags]
+#### Entity tags [#host-entity-tags]
 
 * [`cloud.provider`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/cloud)
 * [`cloud.account.id`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/cloud)
@@ -92,6 +90,29 @@ for monitoring host entities using the host metrics receiver for the OpenTelemet
 * [`host.image.id`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/host)
 * [`host.image.version`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/host)
 
+### Redis instances [#redis]
+
+A redis instance is synthesized using data emitted from the collector [redis receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/redisreceiver). Unfortunately, there are currently no semantic conventions for redis instances, or identifying attributes in the metrics the redis receiver emits. Therefore, users are required to manually include the attributes described below.
+
+Refer to the redis example in [collector for infrastructure monitoring](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/) for more details.
+
+#### Required attributes [#redis-required-attributes]
+
+* [`server.address`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/server/): The redis instance name you see in the UI comes from this value.
+* [`server.port`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/server/)
+
+#### Entity tags [#redis-entity-tags]
+
+* `redis.version`
+* `redis.role`
+* [`host.type`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/host)
+* [`cloud.provider`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/cloud)
+* [`cloud.account.id`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/cloud)
+* [`cloud.region`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/cloud)
+* `instrumenation.name`
+* [`server.address`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/server/)
+* [`server.port`](https://opentelemetry.io/docs/specs/semconv/attributes-registry/server/)
+
 ## Supported entity relationships [#supported-entity-relationships]
 
 New Relic supports relationships between entities sourced from

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro.mdx

@@ -6,6 +6,8 @@ tags:
   - OpenTelemetry
 metaDescription: Using the OpenTelemetry Collector for infrastructure monitoring
 freshnessValidatedDate: 2024-05-14
+redirect:
+ - /docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-redis
 ---
 
 The [OpenTelemetry collector](https://opentelemetry.io/docs/collector/) is a vendor-agnostic tool for receiving, processing, and exporting telemetry data. While collector requirements and configuration will vary, it comes with a variety of receivers and processors which make it popular for infrastructure monitoring. It's also common to use the collector for data processing, but this documentation focuses on infrastructure monitoring use cases. See [OpenTelemetry Collector for data processing](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro) for more info.
@@ -20,7 +22,7 @@ The following examples demonstrate using the collector to monitor various infras
 - [Hosts](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-hosts)
 - [Kafka Confluent Cloud](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-kafka-confluentcloud)
 - [Prometheus](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-prometheus)
-- [Redis](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-redis)
+- [Redis](https://github.com/newrelic/newrelic-opentelemetry-examples/tree/main/other-examples/collector/redis)
 - [Singlestore](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-singlestore)
 - [Squid](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-squid)
 - [StatsD](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-statsd)