full package upgrades

docs/docusaurus.build.config.js

@@ -11,8 +11,8 @@ module.exports = {
       // Set `contextualSearch` to `true` when having multiple versions!!!
       contextualSearch: true,
       searchParameters: {
-        facetFilters: ["tags:observability"]
+        facetFilters: ['tags:observability'],
       },
     },
-  }
-}
+  },
+};

docs/docusaurus.config.js

@@ -24,7 +24,7 @@ module.exports = {
         {
           type: 'docsVersionDropdown',
 
-          //// Optional
+          // Optional
           position: 'right',
           // Add additional dropdown items at the beginning/end of the dropdown.
           dropdownItemsBefore: [],
@@ -84,21 +84,18 @@ module.exports = {
       {
         docs: {
           sidebarPath: require.resolve('./sidebars.js'),
-          routeBasePath: "/",
+          routeBasePath: '/',
           path: 'preview',
           sidebarCollapsible: false,
           // Please change this to your repo.
-          editUrl:
-            'https://github.com/arcus-azure/arcus.observability/edit/master/docs',
-          includeCurrentVersion:process.env.CONTEXT !== 'production',
+          editUrl: 'https://github.com/arcus-azure/arcus.observability/edit/master/docs',
+          includeCurrentVersion: process.env.CONTEXT !== 'production',
         },
         theme: {
           customCss: require.resolve('./src/css/custom.css'),
         },
       },
     ],
   ],
-  stylesheets: [
-    'https://fonts.googleapis.com/css2?family=Bitter:wght@700&family=Inter:wght@400;500&display=swap',
-  ],
+  stylesheets: ['https://fonts.googleapis.com/css2?family=Bitter:wght@700&family=Inter:wght@400;500&display=swap'],
 };

docs/package.json

@@ -14,17 +14,20 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "^2.0.1",
-    "@docusaurus/preset-classic": "^2.0.1",
-    "@docusaurus/theme-search-algolia": "^2.0.1",
-    "@mdx-js/react": "^1.6.21",
-    "@svgr/webpack": "^6.3.1",
-    "clsx": "^1.1.1",
+    "@docusaurus/core": "^3.2.1",
+    "@docusaurus/preset-classic": "^3.2.1",
+    "@docusaurus/theme-search-algolia": "^3.2.1",
+    "@mdx-js/react": "^3.0.1",
+    "@svgr/webpack": "^8.1.0",
+    "clsx": "2.1.0",
     "file-loader": "^6.2.0",
-    "prism-react-renderer": "^1.2.1",
-    "react": "^17.0.1",
-    "react-dom": "^17.0.1",
-    "url-loader": "^4.1.1"
+    "prism-react-renderer": "2.3.1",
+    "react": "18.2.0",
+    "react-dom": "18.2.0",
+    "url-loader": "4.1.1"
+  },
+  "engines": {
+    "node": ">=18.19.0"
   },
   "browserslist": {
     "production": [

docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md

@@ -338,10 +338,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`585ea273-eaa9-44bb-905a-6805bd418566`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Order API**. You clearly see how the initial request to the **Order API** is the caller of the dependency towards the **Order Worker**:
-![Product API <> Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
 
 ## Further reading
 * [Arcus Service Bus messaging documentation](https://messaging.arcus-azure.net/Features/message-pumps/service-bus)

docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md

@@ -307,10 +307,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`8a622fa4-a757-47a0-9db9-e22d00328087`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Product API**. You clearly see how the initial request to the **Product API** is the caller of the dependency towards the **Stock API**:
-![Product API <> Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
 
 ## Conclusion
 In this user guide, you've seen how the Arcus HTTP correlation functionality can be used to set up service-to-service correlation in Web API solutions. The service-to-service correlation is a very wide topic and can be configured with many options. See the [this documentation page](https://webapi.arcus-azure.net/features/correlation) to learn more about HTTP correlation in Web API applications.

docs/versioned_docs/version-v2.3/02-Features/writing-different-telemetry-types.md

@@ -29,11 +29,11 @@ We provide the capability to track the following telemetry types on top of ILogg
   - [Metrics](#metrics)
   - [Requests](#requests)
 
-For most optimal output, we recommend using our [Azure Application Insights sink](/features/sinks/azure-application-insights).
+For most optimal output, we recommend using our [Azure Application Insights sink](./sinks/azure-application-insights).
 
 **We highly encourage to provide contextual information to all your telemetry** to make it more powerful and support this for all telemetry types.
 
-> :bulb: For sake of simplicity we have not included how to track contextual information, for more information see [our documentation](/features/making-telemetry-more-powerful).
+> :bulb: For sake of simplicity we have not included how to track contextual information, for more information see [our documentation](./making-telemetry-more-powerful).
 
 ## Installation
 

docs/versioned_docs/version-v2.4/02-Features/writing-different-telemetry-types.md

@@ -34,11 +34,11 @@ We provide the capability to track the following telemetry types on top of ILogg
     - [Incoming Azure Service Bus requests](#incoming-azure-service-bus-requests)
     - [Incoming HTTP requests](#incoming-http-requests)
 
-For most optimal output, we recommend using our [Azure Application Insights sink](/features/sinks/azure-application-insights).
+For most optimal output, we recommend using our [Azure Application Insights sink](./sinks/azure-application-insights).
 
 **We highly encourage to provide contextual information to all your telemetry** to make it more powerful and support this for all telemetry types.
 
-> :bulb: For sake of simplicity we have not included how to track contextual information, for more information see [our documentation](/features/making-telemetry-more-powerful).
+> :bulb: For sake of simplicity we have not included how to track contextual information, for more information see [our documentation](./making-telemetry-more-powerful).
 
 ## Installation
 

docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md

@@ -333,10 +333,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/servicebus-worker-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/servicebus-worker-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`585ea273-eaa9-44bb-905a-6805bd418566`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Order API**. You clearly see how the initial request to the **Order API** is the caller of the dependency towards the **Order Worker**:
-![Product API <> Stock API transaction search example](/media/servicebus-worker-service-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/servicebus-worker-service-correlation-example-transactionsearch.png)
 
 ## Further reading
 * [Arcus Service Bus messaging documentation](https://messaging.arcus-azure.net/Features/message-pumps/service-bus)

docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md

@@ -295,10 +295,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`8a622fa4-a757-47a0-9db9-e22d00328087`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Product API**. You clearly see how the initial request to the **Product API** is the caller of the dependency towards the **Stock API**:
-![Product API <> Stock API transaction search example](/media/product-stock-api-service-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/product-stock-api-service-correlation-example-transactionsearch.png)
 
 ## Conclusion
 In this user guide, you've seen how the Arcus HTTP correlation functionality can be used to set up service-to-service correlation in Web API solutions. The service-to-service correlation is a very wide topic and can be configured with many options. See the [this documentation page](https://webapi.arcus-azure.net/features/correlation) to learn more about HTTP correlation in Web API applications.

docs/versioned_docs/version-v2.7.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md

@@ -336,10 +336,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`585ea273-eaa9-44bb-905a-6805bd418566`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Order API**. You clearly see how the initial request to the **Order API** is the caller of the dependency towards the **Order Worker**:
-![Product API <> Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
 
 ## Further reading
 * [Arcus Service Bus messaging documentation](https://messaging.arcus-azure.net/Features/message-pumps/service-bus)

docs/versioned_docs/version-v2.7.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md

@@ -307,10 +307,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`8a622fa4-a757-47a0-9db9-e22d00328087`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Product API**. You clearly see how the initial request to the **Product API** is the caller of the dependency towards the **Stock API**:
-![Product API <> Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
 
 ## Conclusion
 In this user guide, you've seen how the Arcus HTTP correlation functionality can be used to set up service-to-service correlation in Web API solutions. The service-to-service correlation is a very wide topic and can be configured with many options. See the [this documentation page](https://webapi.arcus-azure.net/features/correlation) to learn more about HTTP correlation in Web API applications.

docs/versioned_docs/version-v2.8.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md

@@ -336,10 +336,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`585ea273-eaa9-44bb-905a-6805bd418566`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Order API**. You clearly see how the initial request to the **Order API** is the caller of the dependency towards the **Order Worker**:
-![Product API <> Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
 
 ## Further reading
 * [Arcus Service Bus messaging documentation](https://messaging.arcus-azure.net/Features/message-pumps/service-bus)

docs/versioned_docs/version-v2.8.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md

@@ -307,10 +307,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`8a622fa4-a757-47a0-9db9-e22d00328087`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Product API**. You clearly see how the initial request to the **Product API** is the caller of the dependency towards the **Stock API**:
-![Product API <> Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
 
 ## Conclusion
 In this user guide, you've seen how the Arcus HTTP correlation functionality can be used to set up service-to-service correlation in Web API solutions. The service-to-service correlation is a very wide topic and can be configured with many options. See the [this documentation page](https://webapi.arcus-azure.net/features/correlation) to learn more about HTTP correlation in Web API applications.

docs/versioned_docs/version-v3.0.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md

@@ -338,10 +338,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/servicebus-worker-service-w3c-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`585ea273-eaa9-44bb-905a-6805bd418566`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Order API**. You clearly see how the initial request to the **Order API** is the caller of the dependency towards the **Order Worker**:
-![Product API <> Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/servicebus-worker-service-w3c-correlation-example-transactionsearch.png)
 
 ## Further reading
 * [Arcus Service Bus messaging documentation](https://messaging.arcus-azure.net/Features/message-pumps/service-bus)

docs/versioned_docs/version-v3.0.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md

@@ -307,10 +307,10 @@ curl -Method POST `
 The real result, though, happens in Application Insights.
 
 The application map (`Application Insights > Investigate > Application Map`) shows a clear relationship between the two services:
-![Product API <> Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
+![Product API - Stock API application map example](/media/product-stock-api-service-correlation-example-applicationmap.png)
 
 If you copy the `X-Transaction-ID` from the response (`8a622fa4-a757-47a0-9db9-e22d00328087`) and past it in the transaction search (`Application Insights > Investigate > Transaction search`), you'll see this relationship in more detail when you select the initial HTTP request to the **Product API**. You clearly see how the initial request to the **Product API** is the caller of the dependency towards the **Stock API**:
-![Product API <> Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
+![Product API - Stock API transaction search example](/media/product-stock-api-service-w3c-correlation-example-transactionsearch.png)
 
 ## Conclusion
 In this user guide, you've seen how the Arcus HTTP correlation functionality can be used to set up service-to-service correlation in Web API solutions. The service-to-service correlation is a very wide topic and can be configured with many options. See the [this documentation page](https://webapi.arcus-azure.net/features/correlation) to learn more about HTTP correlation in Web API applications.

docs/versioned_sidebars/version-v0.1.0-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v0.1.0/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v0.1.1-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v0.1.1/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v0.2.0-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v0.2.0/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v0.3-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v0.3/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v0.4-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v0.4/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v1.0-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v1.0/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v2.0-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v2.0/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v2.1-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v2.1/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v2.2-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v2.2/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."

docs/versioned_sidebars/version-v2.3-sidebars.json

@@ -1,5 +1,5 @@
 {
-  "version-v2.3/tutorialSidebar": [
+  "tutorialSidebar": [
     {
       "type": "autogenerated",
       "dirName": "."