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
pull/4152/head
Jamie Strandboge 2022-06-22 11:05:03 -05:00 committed by GitHub
parent 2c05f032b9
commit 310acf9e52
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 4 deletions

View File

@ -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.

View File

@ -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.