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

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 Logstash server's certific
 
 [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/observability/ci-cd-observability.asciidoc

@@ -279,7 +279,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"
 
@@ -291,7 +291,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"
 
@@ -413,7 +413,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

@@ -8,7 +8,7 @@
 beta[] Synthetic tests support the configuration of dynamic parameters that can be
 used in the suites. In addition, the Synthetics agent, which is built on top
 of Playwright, supports configuring browser and context options that are available
-in Playwright specific methods, for example, `ignoreHTTPSErrors`, `extraHTTPHeaders` and `viewport`. 
+in Playwright specific methods, for example, `ignoreHTTPSErrors`, `extraHTTPHeaders` and `viewport`.
 
 [discrete]
 [[synthetics-config-file]]