From 310acf9e52e79be4fb975855ada2fbba65844c36 Mon Sep 17 00:00:00 2001
From: Jamie Strandboge <jamie@strandboge.com>
Date: Wed, 22 Jun 2022 11:05:03 -0500
Subject: [PATCH] add missed items from 2.2 (#4151)

* copy forward security/disable-devel.md from v2.2

* apply 2.2 repl fixes in a37484ca to 2.3
---
 content/influxdb/v2.3/security/disable-devel.md | 17 +++++++++++++++++
 .../write-data/replication/replicate-data.md    |  9 +++++----
 2 files changed, 22 insertions(+), 4 deletions(-)
 create mode 100644 content/influxdb/v2.3/security/disable-devel.md

diff --git a/content/influxdb/v2.3/security/disable-devel.md b/content/influxdb/v2.3/security/disable-devel.md
new file mode 100644
index 000000000..d0bc88114
--- /dev/null
+++ b/content/influxdb/v2.3/security/disable-devel.md
@@ -0,0 +1,17 @@
+---
+title: Disable development features
+seotitle: Disable development features in InfluxDB
+description: >
+  Disable development features that may not be desirable in production.
+weight: 105
+menu:
+  influxdb_2_3:
+    parent: Security & authorization
+influxdb/v2.3/tags: [security, development]
+---
+
+By default, InfluxDB {{< current-version >}} enables useful functionality that exposes some level of information about your instance. Two of these are endpoints for observability of the health and activity of your instance. The third is the bundled UI. Depending on your site requirements, you may want to disable one or more of these when running InfluxDB in production. To disable, use the following configuration options:
+
+- [Disable /debug/pprof](/influxdb/v2.3/reference/config-options/#pprof-disabled). This endpoint provides runtime profiling data.
+- [Disable /metrics](/influxdb/v2.3/reference/config-options/#metrics-disabled). This endpoint exposes [internal InfluxDB metrics](/influxdb/v2.2/reference/internals/metrics/).
+- [Disable UI](/influxdb/v2.3/reference/config-options/#ui-disabled). The user interface for InfluxDB.
diff --git a/content/influxdb/v2.3/write-data/replication/replicate-data.md b/content/influxdb/v2.3/write-data/replication/replicate-data.md
index f8f27aa64..165fab8d1 100644
--- a/content/influxdb/v2.3/write-data/replication/replicate-data.md
+++ b/content/influxdb/v2.3/write-data/replication/replicate-data.md
@@ -43,7 +43,7 @@ Use InfluxDB replication streams (InfluxDB Edge Data Replication) to replicate t
     ```sh
     influx remote create \
       --name example-remote-name \
-      --remote-url cloud2.influxdata.com \
+      --remote-url https://cloud2.influxdata.com \
       --remote-api-token mYsuP3r5Ecr37t0k3n \
       --remote-org-id 00xoXXoxXX00
     ```
@@ -105,6 +105,7 @@ In some cases, you may not want to write raw, high-precision data to a remote In
     import "influxdata/influxdb/tasks"
     import "types"
 
+    // omit this line if adding task via the UI
     option task = {name: "Downsample raw data", every: 10m}
 
     data = () => from(bucket: "example-bucket")
@@ -112,14 +113,14 @@ In some cases, you may not want to write raw, high-precision data to a remote In
 
     numeric = data()
         |> filter(fn: (r) => types.isType(v: r._value, type: "float") or types.isType(v: r._value, type: "int") or types.isType(v: r._value, type: "uint"))
-        |> aggregateWindow(every: -task.every, fn: mean)
+        |> aggregateWindow(every: task.every, fn: mean)
 
     nonNumeric = data()
         |> filter(fn: (r) => types.isType(v: r._value, type: "string") or types.isType(v: r._value, type: "bool"))
-        |> aggregateWindow(every: -task.every, fn: last)
+        |> aggregateWindow(every: task.every, fn: last)
 
     union(tables: [numeric, nonNumeric])
-        |> to(bucket: "example-downsampled-bucket"])
+        |> to(bucket: "example-downsampled-bucket")
     ```
 
 3. [Create a replication stream](#configure-a-replication-stream) to replicate data from the downsampled bucket to the remote InfluxDB {{% cloud-only %}}Cloud {{% /cloud-only %}}instance.