[8.7](backport #4926) [Observability Docs] Replace placeholder URLs (#4935)

* [Observability Docs] Replace placeholder URLs (#4926)

(cherry picked from commit 5b5a5c9)


* fix conflicts

---------

Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
Co-authored-by: Mike Birnstiehl <michael.birnstiehl@elastic.co>

Author: mergify[bot]

docs/en/apm-server/legacy/copied-from-beats/docs/https.asciidoc

@@ -32,7 +32,7 @@ For example:
 ["source","yaml",subs="attributes,callouts"]
 ----------------------------------------------------------------------
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   username: "{beat_default_index_prefix}_writer" <1>
   password: "{pwd}" <2>
 ----------------------------------------------------------------------
@@ -55,7 +55,7 @@ For example:
 ["source","yaml",subs="attributes,callouts"]
 ----------------------------------------------------------------------
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   api_key: "KnR6yE41RrSowb0kQ0HWoA" <1>
 ----------------------------------------------------------------------
 <1> This API key must have the privileges required to publish events to {es}.
@@ -71,7 +71,7 @@ For example:
 ["source","yaml",subs="attributes,callouts"]
 ----------------------------------------------------------------------
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   ssl.certificate: "/etc/pki/client/cert.pem" <1>
   ssl.key: "/etc/pki/client/cert.key" <2>
 ----------------------------------------------------------------------
@@ -98,7 +98,7 @@ Here is an example configuration:
 ["source","yaml",subs="attributes,callouts"]
 ----------------------------------------------------------------------
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   ssl.certificate_authorities: <1>
     - /etc/pki/my_root_ca.pem
     - /etc/pki/my_other_ca.pem

docs/en/apm-server/legacy/copied-from-beats/docs/monitoring/monitoring-internal-collection.asciidoc

@@ -79,7 +79,7 @@ monitoring:
   enabled: true
   cluster_uuid: PRODUCTION_ES_CLUSTER_UUID <1>
   elasticsearch:
-    hosts: ["https://example.com:9200", "https://example2.com:9200"] <2>
+    hosts: ["<HOST_URL>:9200", "<HOST_URL>:9200"] <2>
     api_key:  id:api_key <3>
     username: {beat_monitoring_user}
     password: somepassword
@@ -102,7 +102,7 @@ monitoring:
   enabled: true
   cluster_uuid: PRODUCTION_ES_CLUSTER_UUID
   elasticsearch:
-    hosts: ["https://example.com:9200", "https://example2.com:9200"]
+    hosts: ["<HOST_URL>:9200", "<HOST_URL>:9200"]
     username: ""
     ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
     ssl.certificate: "/etc/pki/client/cert.pem"

docs/en/apm-server/legacy/copied-from-beats/docs/shared-ssl-logstash-config.asciidoc

@@ -86,26 +86,26 @@ Before running {beatname_uc}, you should validate the {ls} server's certificate.
 
 [source,shell]
 ------------------------------------------------------------------------------
-curl -v --cacert ca.crt https://logs.mycompany.com:5044
+curl -v --cacert ca.crt <YOUR_URL>:5044
 ------------------------------------------------------------------------------
 
 If the test is successful, you'll receive an empty response error:
 
 [source,shell]
 ------------------------------------------------------------------------------
-* Rebuilt URL to: https://logs.mycompany.com:5044/
+* Rebuilt URL to: <YOUR_URL>:5044/
 *   Trying 192.168.99.100...
-* Connected to logs.mycompany.com (192.168.99.100) port 5044 (#0)
+* Connected to <YOUR_URL> (192.168.99.100) port 5044 (#0)
 * TLS 1.2 connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
-* Server certificate: logs.mycompany.com
-* Server certificate: mycompany.com
+* Server certificate: <YOUR_URL>
+* Server certificate: <YOUR_URL>
 > GET / HTTP/1.1
-> Host: logs.mycompany.com:5044
+> Host: <YOUR_URL>:5044
 > User-Agent: curl/7.43.0
 > Accept: */*
 >
 * Empty reply from server
-* Connection #0 to host logs.mycompany.com left intact
+* Connection #0 to host <YOUR_URL> left intact
 curl: (52) Empty reply from server
 ------------------------------------------------------------------------------
 

docs/en/apm-server/legacy/copied-from-beats/outputs/elasticsearch/docs/elasticsearch.asciidoc

@@ -14,7 +14,7 @@ Example configuration:
 ["source","yaml",subs="attributes"]
 ----
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"] <1>
+  hosts: ["<YOUR_ES_HOST_URL>:9200"] <1>
 ----
 <1> To enable SSL, add `https` to all URLs defined under __hosts__.
 
@@ -30,7 +30,7 @@ output, {beatname_uc} can use any of the following authentication methods:
 ["source","yaml",subs="attributes,callouts"]
 ----
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   username: "{beat_default_index_prefix}_writer"
   password: "{pwd}"
 ----
@@ -40,7 +40,7 @@ output.elasticsearch:
 ["source","yaml",subs="attributes,callouts"]
 ----
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   api_key: "ZCV7VnwBgnX0T19fN8Qe:KnR6yE41RrSowb0kQ0HWoA"
 ----
 
@@ -49,7 +49,7 @@ output.elasticsearch:
 ["source","yaml",subs="attributes,callouts"]
 ----
 output.elasticsearch:
-  hosts: ["https://myEShost:9200"]
+  hosts: ["<YOUR_ES_HOST_URL>:9200"]
   ssl.certificate: "/etc/pki/client/cert.pem"
   ssl.key: "/etc/pki/client/cert.key"
 ----

docs/en/observability/ci-cd-observability.asciidoc

@@ -362,7 +362,7 @@ passing the configuration details as environment variables:
 
 [source,bash]
 ----
-export OTEL_EXPORTER_OTLP_ENDPOINT="https://elastic-apm-server.example.com:8200"
+export OTEL_EXPORTER_OTLP_ENDPOINT="<YOUR_APM_SERVER_URL>:8200"
 export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer an_apm_secret_token"
 export OTEL_TRACES_EXPORTER="otlp"
 
@@ -374,7 +374,7 @@ command line argument “-Dmaven.ext.class.path=...”
 
 [source,bash]
 ----
-export OTEL_EXPORTER_OTLP_ENDPOINT="https://elastic-apm-server.example.com:8200"
+export OTEL_EXPORTER_OTLP_ENDPOINT="<YOUR_APM_SERVER_URL>:8200"
 export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer an_apm_secret_token"
 export OTEL_TRACES_EXPORTER="otlp"
 
@@ -520,7 +520,7 @@ through the `TRACEPARENT`.
 
 [source,bash]
 ----
-OTEL_EXPORTER_OTLP_ENDPOINT=https://elastic-apm-server.example.com:8200 \
+OTEL_EXPORTER_OTLP_ENDPOINT=<YOUR_APM_SERVER_URL>:8200 \
 OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer an_apm_secret_token" \
 OTEL_SERVICE_NAME=pytest_otel \
 pytest --otel-session-name='My_Test_cases'

docs/en/observability/monitor-java-app.asciidoc

@@ -1709,7 +1709,7 @@ environment variables. The `.env` file should look like this:
 [source,bash]
 ----
 ELASTIC_APM_SERVICE_NAME=javalin-app
-ELASTIC_APM_SERVER_URLS=https://APM_ENDPOINT_URL
+ELASTIC_APM_SERVER_URLS=<YOUR_APM_ENDPOINT_URL>
 ELASTIC_APM_SECRET_TOKEN=PqWTHGtHZS2i0ZuBol
 ----
 +

docs/en/observability/synthetics-configuration.asciidoc

@@ -104,7 +104,7 @@ To list available locations you can:
 Locations will be listed in _Locations_.
 
 `privateLocations` (`Array<string>`)::
-The <<synthetics-private-location,{private-location}s>> to which the monitors will be deployed. These {private-location}s refer to locations hosted and managed by you, whereas 
+The <<synthetics-private-location,{private-location}s>> to which the monitors will be deployed. These {private-location}s refer to locations hosted and managed by you, whereas
 `locations` are hosted by Elastic. You can specify a {private-location} using the location's name.
 +
 To list available {private-location}s you can: