DOCS-10432: add autodiscovery to temporal doc (#20049)

* update readme

* Update temporal/README.md

Co-authored-by: Alicia Scott <aliciascott@users.noreply.github.com>

---------

Co-authored-by: Alicia Scott <aliciascott@users.noreply.github.com>

Author: cswatt

temporal/README.md

@@ -17,17 +17,28 @@ No additional installation is needed on your server.
 
 ### Configuration
 
+<!-- xxx tabs xxx -->
+<!-- xxx tab "Host" xxx -->
+
+#### Host
+
+##### Metric collection
+
 1. Configure your Temporal services to expose metrics via a `prometheus` endpoint by following the [official Temporal documentation][10].
 
 2. Edit the `temporal.d/conf.yaml` file located in the `conf.d/` folder at the root of your Agent's configuration directory to start collecting your Temporal performance data. 
 
-To get started, configure the `openmetrics_endpoint` option to match the `listenAddress` and `handlerPath` options from your Temporal server configuration.
+   Configure the `openmetrics_endpoint` option to match the `listenAddress` and `handlerPath` options from your Temporal server configuration.
 
-Note that when Temporal services in a cluster are deployed independently, every service exposes its own metrics. As a result, you need to configure the `prometheus` endpoint for every service that you want to monitor and define a separate `instance` on the integration's configuration for each of them.
+   ```yaml
+   init_config:
+   instances:
+     - openmetrics_endpoint: <LISTEN_ADDRESS>/<HANDLER_PATH>
+   ```
 
-See the [sample temporal.d/conf.yaml][4] for all available configuration options.
+   Note that when Temporal services in a cluster are deployed independently, every service exposes its own metrics. As a result, you need to configure the `prometheus` endpoint for every service that you want to monitor and define a separate `instance` on the integration's configuration for each of them.
 
-#### Log collection
+##### Log collection
 
 1. Collecting logs is disabled by default in the Datadog Agent. Enable it in your `datadog.yaml` file:
 
@@ -48,6 +59,68 @@ See the [sample temporal.d/conf.yaml][4] for all available configuration options
 
 4. [Restart the Agent][5].
 
+<!-- xxz tab xxx -->
+
+<!-- xxx tab "Containerized" xxx -->
+
+#### Containerized
+
+##### Metric collection
+
+For containerized environments, refer to [Configure integrations with Autodiscovery on Kubernetes][14] or [Configure integrations with Autodiscovery on Docker][15] for instructions on using the parameters below. See the [sample temporal.d/conf.yaml][4] for a complete list of configuration options.
+
+| Parameter            | Value                                |
+| -------------------- | ------------------------------------ |
+| `<INTEGRATION_NAME>` | `temporal`                          |
+| `<INIT_CONFIG>`      | blank or `{}`                        |
+| `<INSTANCES_CONFIG>`  | `{"openmetrics_endpoint": "<LISTEN_ADDRESS>/<HANDLER_PATH>"}`, where `<LISTEN_ADDRESS>` and `<HANDLER_PATH>` are replaced by the `listenAddress` and `handlerPath` from your Temporal server configuration. |
+
+Note that when Temporal services in a cluster are deployed independently, every service exposes its own metrics. As a result, you need to configure the `prometheus` endpoint for every service that you want to monitor and define a separate `instance` on the integration's configuration for each of them.
+
+**Example**
+
+The following Kubernetes annotation is applied to a pod under `metadata`, where `<CONTAINER_NAME>` is the name of your Temporal container (or a [custom identifier][16]):
+
+```
+ad.datadoghq.com/<CONTAINER_NAME>.checks: |
+  {
+    "temporal": {
+      "init_config": {},
+      "instances": [{"openmetrics_endpoint": "<LISTEN_ADDRESS>/<HANDLER_PATH>"}]
+    }
+  } 
+```
+
+##### Log collection
+
+Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Docker Log Collection][18] or [Kubernetes Log Collection][17].
+
+Apply the following configuration parameter to `logs`:
+
+| Parameter      | Value                                               |
+| -------------- | --------------------------------------------------- |
+| `<LOG_CONFIG>` | `{"source": "temporal", "type": "file", "path": "/var/log/temporal/temporal-server.log"}` |
+
+**Example**
+
+The following Kubernetes annotation is applied to a pod under `metadata`, where `<CONTAINER_NAME>` is the name of your Temporal container (or a [custom identifier][16]):
+
+```
+ad.datadoghq.com/<CONTAINER_NAME>.logs: |
+  [
+    {
+      "source": "temporal",
+      "type": "file",
+      "path": "/var/log/temporal/temporal-server.log"
+    } 
+  ]
+```
+
+<!-- xxz tab xxx -->
+
+<!-- xxz tabs xxx -->
+
+
 ### Validation
 
 [Run the Agent's status subcommand][6] and look for `temporal` under the Checks section.
@@ -94,3 +167,8 @@ Additional helpful documentation, links, and articles:
 [11]: https://docs.temporal.io/references/configuration#log
 [12]: https://www.datadoghq.com/blog/temporal-server-integration/
 [13]: https://docs.datadoghq.com/integrations/temporal_cloud/
+[14]: https://docs.datadoghq.com/containers/kubernetes/integrations/
+[15]: https://docs.datadoghq.com/containers/docker/integrations/
+[16]: https://docs.datadoghq.com/containers/guide/ad_identifiers/
+[17]: https://docs.datadoghq.com/agent/kubernetes/log/
+[18]: https://docs.datadoghq.com/containers/docker/log/