open-telemetry · cartermp · Jun 7, 2023 · Jun 7, 2023 · Jun 7, 2023 · Jun 7, 2023
@@ -4,5 +4,5 @@ linkTitle: API
 redirect: https://open-telemetry.github.io/opentelemetry-js/
 manualLinkTarget: _blank
 _build: { render: link }
-weight: 50
+weight: 210
 ---
@@ -1,7 +1,7 @@
 ---
 title: Automatic Instrumentation
 linkTitle: Automatic
-weight: 30
+weight: 20
 ---
 
 Automatic instrumentation provides a way to instrument any Node.js application

@@ -1,7 +1,7 @@
 ---
 title: Automatic Instrumentation Configuration
 linkTitle: Configuration
-weight: 45
+weight: 10
 ---
 
 This module is highly configurable by setting

@@ -2,7 +2,7 @@
 title: Context
 description: OpenTelemetry JavaScript Context API Documentation
 aliases: [/docs/instrumentation/js/api/context]
-weight: 8
+weight: 60
 ---
 
 In order for OpenTelemetry to work, it must store and propagate important

@@ -2,7 +2,7 @@
 title: Instrumentation Examples
 title: Examples
 aliases: [/docs/instrumentation/js/instrumentation_examples]
-weight: 99
+weight: 220
 ---
 
 Here are some of the resources for OpenTelemetry instrumentation examples.

@@ -1,6 +1,6 @@
 ---
 title: Exporters
-weight: 5
+weight: 50
 spelling: cSpell:ignore proto nginx openzipkin
 ---
 

@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 aliases: [/docs/js/getting_started]
-weight: 1
+weight: 10
 ---
 
 These two guides for Node.js and the browser use simple examples in javascript

@@ -1,7 +1,7 @@
 ---
 title: Browser
 aliases: [/docs/js/getting_started/browser]
-weight: 3
+weight: 20
 ---
 
 While this guide uses the example application presented below, the steps to

@@ -3,7 +3,7 @@ title: Node.js
 description: Get telemetry for your app in less than 5 minutes!
 aliases: [/docs/js/getting_started/nodejs]
 spelling: cSpell:ignore rolldice autoinstrumentation autoinstrumentations KHTML
-weight: 2
+weight: 10
 ---
 
 This page will show you how to get started with OpenTelemetry in Node.js.
@@ -454,8 +454,8 @@ the console output, such as the following:
 ## Next Steps
 
 Enrich your instrumentation generated automatically with
-[manual instrumentation](/docs/instrumentation/js/instrumentation) of your own
-codebase. This gets you customized observability data.
+[manual instrumentation](/docs/instrumentation/js/manual) of your own codebase.
+This gets you customized observability data.
 
 You'll also want to configure an appropriate exporter to
 [export your telemetry data](/docs/instrumentation/js/exporters) to one or more

@@ -1,7 +1,7 @@
 ---
 title: Using instrumentation libraries
 linkTitle: Libraries
-weight: 3
+weight: 40
 spelling: cSpell:ignore autoinstrumentation metapackage
 ---
 
@@ -256,8 +256,8 @@ You can also find more instrumentations available in the
 ## Next steps
 
 After you have set up instrumentation libraries, you may want to add
-[manual instrumentation](/docs/instrumentation/js/instrumentation) to collect
-custom telemetry data.
+[manual instrumentation](/docs/instrumentation/js/manual) to collect custom
+telemetry data.
 
 You'll also want to configure an appropriate exporter to
 [export your telemetry data](/docs/instrumentation/js/exporters) to one or more

@@ -1,7 +1,9 @@
 ---
-title: Instrumentation
-aliases: [/docs/instrumentation/js/api/tracing]
-weight: 4
+title: Manual
+aliases:
+  - /docs/instrumentation/js/api/tracing
+  - /docs/instrumentation/js/instrumentation
+weight: 30
 spelling: cSpell:ignore Millis
 ---
 

@@ -2,7 +2,7 @@
 title: Propagation
 description: Context propagation for the JS SDK
 aliases: [/docs/instrumentation/js/api/propagation]
-weight: 7
+weight: 65
 spelling: cSpell:ignore traceparent tracestate
 ---
 

@@ -1,6 +1,6 @@
 ---
 title: Resources
-weight: 6
+weight: 70
 ---
 
 A [resource][] represents the entity producing telemetry as resource attributes.

@@ -1,6 +1,6 @@
 ---
 title: Sampling
-weight: 9
+weight: 80
 ---
 
 [Sampling](/docs/concepts/sampling/) is a process that restricts the amount of

@@ -1,6 +1,6 @@
 ---
 title: Serverless
-weight: 8
+weight: 100
 spelling: cSpell:ignore otelwrapper
 ---