docs: Move observability. Add external links. Fix admonitions

Author: alhendrickson

docs/overview/Natural Language Processing.md

@@ -173,7 +173,7 @@ Please see [CogStack using Apache NiFi Deployment Examples](https://github.com/C
 
 Assuming that the application is running on the `localhost` with the API exposed on port `5000`, one can run:
 
-```java
+```bash
 curl -XPOST http://localhost:5000/api/process \
   -H 'Content-Type: application/json' \
   -d '{"content":{"text":"The patient was diagnosed with leukemia."}}'
@@ -182,7 +182,7 @@ curl -XPOST http://localhost:5000/api/process \
 
 and the received result:
 
-```java
+```json
 {
   "result": {
     "text": "The patient was diagnosed with leukemia.",
@@ -211,7 +211,7 @@ and the received result:
 
 Bio-YODIE is being run as a service using CogStack GATE NLP Runner Service as described above. In this example Bio-YODIE application will only output annotations of `Disease` type from `Bio` group (defined in the service configuration file). Assuming that the service is running on the `localhost` with the API exposed on port `8095`, so one can run:
 
-```java
+```bash
 curl --header "Content-Type: application/json" \
   --request POST \
   --data '{"content":{"text": "lung cancer diagnosis"}}' \
@@ -220,7 +220,7 @@ curl --header "Content-Type: application/json" \
 
 and the received result:
 
-```java
+```json
 {
   "result": {
     "text": "lung cancer diagnosis",
@@ -270,7 +270,7 @@ As an extra example, a simple application for extracting drug names from the fre
 
 Similarly as in above, assuming that the application is running on the `localhost` with the API exposed on port `8095`, one can run:
 
-```java
+```bash
 curl -XPOST http://localhost:8095/api/process \
   -H 'Content-Type: application/json' \
   -d '{"content":{"text":"The patient was prescribed with Aspirin."}}'
@@ -279,7 +279,7 @@ curl -XPOST http://localhost:8095/api/process \
 
 and the received result:
 
-```java
+```json
 {
   "result": {
     "text": "The patient was prescribed with Aspirin.",

docs/platform/observability/reference/quickstart-manual.md

@@ -11,8 +11,8 @@ mkdir -p observability-simple/alloy/probers
 
 Download these two files, and place in the right folder
 
-- [docker-compose.yml](../../../observability/examples/simple/docker-compose.yml) in observability-simple/
-- [probe-observability.yml](../../../observability/examples/simple/alloy/probers/probe-observability.yml) into observability-simple/alloy/probers
+- [docker-compose.yml](../../../../observability/examples/simple/docker-compose.yml) in observability-simple/
+- [probe-observability.yml](../../../../observability/examples/simple/alloy/probers/probe-observability.yml) into observability-simple/alloy/probers
 
 ### Step 2: Start the stack
 

docs/platform/observability/setup/production-setup.md

@@ -26,15 +26,15 @@ This script will setup all the folder structure, and download all the relevant f
 The script automates making folders, and downloading these files:
 
 Downloads the example docker compose files:
-- [docker-compose.yml](../../../observability/examples/full/docker-compose.yml)
-- [exporters.docker-compose.yml](../../../observability/examples/full/exporters.docker-compose.yml)
-- [exporters.elastic.docker-compose.yml](../../../observability/examples/full/exporters.elastic.docker-compose.yml)
+- [docker-compose.yml](../../../../observability/examples/full/docker-compose.yml)
+- [exporters.docker-compose.yml](../../../../observability/examples/full/exporters.docker-compose.yml)
+- [exporters.elastic.docker-compose.yml](../../../../observability/examples/full/exporters.elastic.docker-compose.yml)
 
 Downloads the configurations:
-- [alloy/probers/probe-external.yml](../../../observability/examples/full/alloy/probers/probe-external.yml)
-- [alloy/probers/probe-observability.yml ](../../../observability/examples/full/alloy/probers/probe-observability.yml)
-- [prometheus/scrape-configs/exporters/exporters.yml](../../../observability/examples/full/prometheus/scrape-configs/exporters/exporters.yml)
-- [prometheus/scrape-configs/recording-rules/slo.yml](../../../observability/examples/full/prometheus/scrape-configs/recording-rules/slo.yml)
+- [alloy/probers/probe-external.yml](../../../../observability/examples/full/alloy/probers/probe-external.yml)
+- [alloy/probers/probe-observability.yml ](../../../../observability/examples/full/alloy/probers/probe-observability.yml)
+- [prometheus/scrape-configs/exporters/exporters.yml](../../../../observability/examples/full/prometheus/scrape-configs/exporters/exporters.yml)
+- [prometheus/scrape-configs/recording-rules/slo.yml](../../../../observability/examples/full/prometheus/scrape-configs/recording-rules/slo.yml)
 
 
 
@@ -86,7 +86,7 @@ This is probably the hardest step: You will actually need to know what is runnin
 ## Step 5: Run Grafana Alloy on every VM
 The Grafana Alloy image needs to be run on each VM that you want to get information from. 
 
-Use the example docker compose file in [exporters.docker-compose.yml](../../../observability/examples/full/exporters.docker-compose.yml) which will start up alloy and get metrics
+Use the example docker compose file in [exporters.docker-compose.yml](../../../../observability/examples/full/exporters.docker-compose.yml) which will start up alloy and get metrics
 
    ```
    docker compose -f exporters.docker-compose.yml up -d

docs/platform/observability/setup/telemetry.md

@@ -16,7 +16,7 @@ We have to run Grafana Alloy on every single VM to get telemetry.
 
 Alloy is setup to push metrics to a central prometheus instance.
 
-- Copy this docker compose file: [exporters.docker-compose.yml](../../../observability/examples/full/exporters.docker-compose.yml)
+- Copy this docker compose file: [exporters.docker-compose.yml](../../../../observability/examples/full/exporters.docker-compose.yml)
 - Edit the environment variables to point to your prometheus URL:
 
 ```yaml
@@ -34,8 +34,8 @@ Now you have the setup, you will have to run this on every VM you want metrics f
 ### Elastic Search Metrics
 To get elasticsearch metrics we have to mount an alloy config file into the image.
 
-- Copy this docker compose file: [exporters.elastic.docker-compose.yml](../../../observability/examples/full/exporters.elastic.docker-compose.yml)
-- Copy this configuration file [elasticsearch.alloy](../../../observability/examples/full/alloy/elasticsearch.alloy) into `alloy/elasticsearch.alloy`
+- Copy this docker compose file: [exporters.elastic.docker-compose.yml](../../../../observability/examples/full/exporters.elastic.docker-compose.yml)
+- Copy this configuration file [elasticsearch.alloy](../../../../observability/examples/full/alloy/elasticsearch.alloy) into `alloy/elasticsearch.alloy`
 
 In the docker compose file, we can see there are two changes to the usual exporter: