Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge branch 'master' into common-queries

pull/978/head
Scott Anderson 2020-04-24 13:23:30 -06:00
parent c85b8fb86f c551ca1e6f
commit 31f6cce326
213 changed files with 3438 additions and 1707 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
.circleci/config.yml
View File

@ -2,7 +2,7 @@ version: 2
jobs:
build:
docker:
- image: circleci/node:dubnium
- image: circleci/node:erbium
environment:
HUGO_VERSION: "0.59.1"
S3DEPLOY_VERSION: "2.3.2"
@ -10,8 +10,8 @@ jobs:
- checkout
- restore_cache:
keys:
- install-v1-{{ checksum ".circleci/config.yml" }}
- install-v1-
- install-{{ .Environment.CACHE_VERSION }}-{{ checksum ".circleci/config.yml" }}
- install-{{ .Environment.CACHE_VERSION }}-
- run:
name: Make bin folder
command: mkdir -p $HOME/bin
@ -22,13 +22,13 @@ jobs:
name: Install s3deploy
command: ./deploy/ci-install-s3deploy.sh
- run:
name: Install NPM dependencies
command: sudo npm i -g postcss-cli autoprefixer redoc-cli
name: Install NodeJS dependencies
command: sudo yarn global add postcss-cli autoprefixer redoc-cli
- run:
name: Generate API documentation
command: cd api-docs && bash generate-api-docs.sh
- save_cache:
key: install-v1-{{ checksum ".circleci/config.yml" }}
key: install-{{ .Environment.CACHE_VERSION }}-{{ checksum ".circleci/config.yml" }}
paths:
- /home/circleci/bin
- run:
@ -46,8 +46,8 @@ jobs:
- checkout
- restore_cache:
keys:
- install-v1-{{ checksum ".circleci/config.yml" }}
- install-v1-
- install-{{ .Environment.CACHE_VERSION }}-{{ checksum ".circleci/config.yml" }}
- install-{{ .Environment.CACHE_VERSION }}-
- attach_workspace:
at: workspace
- run:

139
CONTRIBUTING.md
View File

@ -64,10 +64,6 @@ menu:
parent: # Specifies a parent group and nests navigation items
weight: # Determines sort order in both the nav tree and in article lists
draft: # If true, will not render page on build
enterprise_all: # If true, specifies the doc as a whole is specific to InfluxDB Enterprise
enterprise_some: # If true, specifies the doc includes some content specific to InfluxDB Enterprise
cloud_all: # If true, specifies the doc as a whole is specific to InfluxDB Cloud
cloud_some: # If true, specifies the doc includes some content specific to InfluxDB Cloud
v2.x/tags: # Tags specific to each version (replace .x" with the appropriate minor version )
related: # Creates links to specific internal and external content at the bottom of the page
- /path/to/related/article
@ -76,6 +72,7 @@ external_url: # Used in children shortcode type="list" for page links that are e
list_image: # Image included with article descriptions in children type="articles" shortcode
list_note: # Used in children shortcode type="list" to add a small note next to listed links
list_code_example: # Code example included with article descriptions in children type="articles" shortcode
products: # List of products that the page specifically applies to: [oss, cloud, enterprise]
```
#### Title usage
@ -124,27 +121,7 @@ Insert warning markdown content here.
```
### Enterprise Content
Many articles are unique to InfluxDB enterprise or at least contain some information specific to InfluxDB Enterprise.
There are frontmatter options and an enterprise shortcode that help to properly identify this content.
#### All content is Enterprise-specific
If all content in an article is Enterprise-specific, set the `enterprise_all` frontmatter to `true`.
```yaml
enterprise_all: true
```
This will display a message at the top of page indicating that the things discussed are unique to InfluxDB Enterprise.
#### Only some content is Enterprise-specific
If only some content in the article is enterprise specific, set the `enterprise_some` frontmatter to `true`.
```yaml
enterprise_some: true
```
This will display a message at the top of page indicating some things are unique to InfluxDB Enterprise.
To format Enterprise-specific content, wrap it in the `{{% enterprise %}}` shortcode:
For sections content that relate specifically to InfluxDB Enterprise, use the `{{% enterprise %}}` shortcode.
```md
{{% enterprise %}}
@ -152,6 +129,13 @@ Insert enterprise-specific markdown content here.
{{% /enterprise %}}
```
#### All content is Enterprise-specific
If all content in an article is Enterprise-specific, include `enterprise`in the `products` frontmatter.
```yaml
products: [enterprise]
```
#### Enterprise name
The name used to refer to InfluxData's enterprise offering is subject to change.
To facilitate easy updates in the future, use the `enterprise-name` shortcode
@ -177,47 +161,19 @@ Find more info [here][{{< enterprise-link >}}]
```
### InfluxDB Cloud Content
Some articles are unique to InfluxDB Cloud or at least contain some information specific to InfluxDB Cloud.
There are frontmatter options and an cloud shortcode that help to properly identify this content.
#### All content is cloud-specific
If all content in an article is cloud-specific, set the menu in the frontmatter to `v2_0_cloud`
(change the version number for the specific version of InfluxDB Cloud).
```yaml
menu:
v2_0_cloud:
name: Menu item name
# ...
```
The pages `parent` depends on where it fits in the hierarchy of the cloud documentation.
#### Only some content is cloud-specific
If only some content in the article is cloud-specific, set the `cloud_some` frontmatter to `true`.
```yaml
cloud_some: true
```
This will display a message at the top of page indicating some things are unique to InfluxDB Cloud.
To format cloud-specific content, wrap it in the `{{% cloud %}}` shortcode:
For sections content that relate specifically to InfluxDB Cloud, use the `{{% cloud %}}` shortcode.
```md
{{% cloud %}}
Insert Cloud-specific markdown content here.
Insert cloud-specific markdown content here.
{{% /cloud %}}
```
#### InfluxDB Cloud content block
The `{{ cloud-msg }}` shortcode creates a highlighted block of text specific to
InfluxDB Cloud meant to stand out from the rest of the article content.
It's format is similar to note and warning blocks.
#### All content is cloud-specific
If all content in an article is cloud-specific, include `cloud` in the `products` frontmatter.
```md
{{% cloud-msg %}}
Insert Cloud-specific markdown content here.
{{% /cloud-msg %}}
```yaml
products: [cloud]
```
#### InfluxDB Cloud name
@ -244,6 +200,13 @@ InfluxDB Cloud.
Find more info [here][{{< cloud-link >}}]
```
### InfluxDB OSS Content
If all content in an article is OSS-specific, include `oss` in the `products` frontmatter.
```yaml
products: [oss]
```
### Tabbed Content
Shortcodes are available for creating "tabbed" content (content that is changed by a users' selection).
Ther following three must be used:
@ -521,29 +484,6 @@ The following case insensitive values are supported:
- settings
- feedback
### InfluxDB UI notification messages
In some cases, documentation references a notification message that appears in
the top-right corner of the InfluxDB UI.
Rather than taking a screenshot of the message (that can be hard to maintain over time),
use the `{{< ui-message >}}` shortcode.
It expects two parameters:
**`text`** (Required)
The message displayed.
**`color`** (Optional)
Sets the background color and icons used in the message.
The following options are available:
- green _(default)_
- blue
- red
```
{{< ui-message color="green" text="The message displayed in the notification.">}}
```
### Flexbox-formatted content blocks
CSS Flexbox formatting lets you create columns in article content that adjust and
flow based on the viewable width.
@ -608,6 +548,41 @@ Redoc generates HTML documentation using the InfluxDB `swagger.yml`.
For more information about generating InfluxDB API documentation, see the
[API Documentation README](https://github.com/influxdata/docs-v2/tree/master/api-docs#readme).
## InfluxDB URLs
When a user selects an InfluxDB product and region, example URLs in code blocks
throughout the documentation are updated to match their product and region.
InfluxDB URLs are configured in `/data/influxdb_urls.yml`.
By default, the InfluxDB URL replaced inside of code blocks is `http://localhost:9999`.
Use this URL in all code examples that should be updated with a selected provider and region.
For example:
~~~
```sh
# This URL will get updated
http://localhost:9999
# This URL will NOT get updated
http://example.com
```
~~~
If the user selects the **US West (Oregon)** region, all occurrences of `http://localhost:9999`
in code blocks will get updated to `https://us-west-2-1.aws.cloud2.influxdata.com`.
### Exempt URLs from getting updated
To exempt a code block from being updated, include the `{{< keep-url >}}` shortcode
just before the code block.
~~~
{{< keep-url >}}
```
// This URL won't get updated
http://localhost:9999
```
~~~
## New Versions of InfluxDB
Version bumps occur regularly in the documentation.
Each minor version has its own directory with unique content.

20
api-docs/template.hbs
View File

@ -2,19 +2,20 @@
<html>
<head>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-WXRH9C');</script>
<!-- End Google Tag Manager -->
<meta charset="utf8" />
<title>{{title}}</title>
<meta name="description" content="The InfluxDB API provides a programmatic interface for interactions with InfluxDB {{templateOptions.version}}.">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" href="/img/favicon.png" type="image/png" sizes="32x32">
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-45024174-12"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-45024174-12');
</script>
<meta name="google-site-verification" content="_V6CNhaIIgVsTO9max_ECw7DUfPL-ZGE7G03MQgEGMU" />
<style>
@ -29,6 +30,11 @@
</head>
<body>
<!-- Google Tag Manager (noscript) -->
<noscript>
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WXRH9C" height="0" width="0" style="display:none;visibility:hidden"></iframe>
</noscript>
<!-- End Google Tag Manager (noscript) -->
<div id="loading">
<div class="spinner"></div>
</div>

296
api-docs/v2.0/swagger.yml
View File

@ -2282,7 +2282,17 @@ paths:
content:
application/json:
schema:
$ref: "#/components/schemas/Dashboard"
type: object
properties:
name:
description: optional, when provided will replace the name
type: string
description:
description: optional, when provided will replace the description
type: string
cells:
description: optional, when provided will replace all existing cells with the cells provided
$ref: "#/components/schemas/CellWithViewProperties"
parameters:
- $ref: '#/components/parameters/TraceSpan'
- in: path
@ -3751,6 +3761,11 @@ paths:
schema:
type: string
description: Filter organizations to a specific organization ID.
- in: query
name: userID
schema:
type: string
description: Filter organizations to a specific user ID.
responses:
'200':
description: A list of organizations
@ -4361,7 +4376,7 @@ paths:
$ref: "#/components/schemas/Error"
/packages/stacks:
post:
operationId: CreatePkg
operationId: CreateStack
tags:
- InfluxPackages
summary: Create a new Influx package
@ -6351,6 +6366,10 @@ components:
- flux
dialect:
$ref: "#/components/schemas/Dialect"
now:
description: Specifies the time that should be reported as "now" in the query. Default is the server's now time.
type: string
format: date-time
InfluxQLQuery:
description: Query influx using the InfluxQL language
type: object
@ -7209,6 +7228,8 @@ components:
type: boolean
orgID:
type: string
stackID:
type: string
package:
$ref: "#/components/schemas/Pkg"
packages:
@ -7316,6 +7337,8 @@ components:
type: string
orgID:
type: string
pkgName:
type: string
name:
type: string
description:
@ -7333,6 +7356,8 @@ components:
- $ref: "#/components/schemas/CheckDiscriminator"
- type: object
properties:
pkgName:
type: string
labelAssociations:
type: array
items:
@ -7350,6 +7375,8 @@ components:
type: "string"
orgID:
type: "string"
pkgName:
type: string
name:
type: "string"
description:
@ -7367,12 +7394,18 @@ components:
items:
type: object
properties:
status:
type: string
resourcePkgName:
type: string
resourceName:
type: string
resourceID:
type: string
resourceType:
type: string
labelPkgName:
type: string
labelName:
type: string
labelID:
@ -7392,6 +7425,8 @@ components:
- $ref: "#/components/schemas/NotificationEndpointDiscrimator"
- type: object
properties:
pkgName:
type: string
labelAssociations:
type: array
items:
@ -7401,11 +7436,13 @@ components:
items:
type: object
properties:
pkgName:
type: string
name:
type: string
description:
type: string
endpointName:
endpointPkgName:
type: string
endpointID:
type: string
@ -7448,6 +7485,8 @@ components:
items:
type: object
properties:
pkgName:
type: string
id:
type: string
name:
@ -7471,6 +7510,8 @@ components:
- $ref: "#/components/schemas/TelegrafRequest"
- type: object
properties:
pkgName:
type: string
labelAssociations:
type: array
items:
@ -7480,6 +7521,8 @@ components:
items:
type: object
properties:
pkgName:
type: string
id:
type: string
orgID:
@ -7502,13 +7545,17 @@ components:
items:
type: object
properties:
stateStatus:
type: string
id:
type: string
name:
pkgName:
type: string
new:
type: object
properties:
name:
type: string
description:
type: string
retentionRules:
@ -7516,6 +7563,8 @@ components:
old:
type: object
properties:
name:
type: string
description:
type: string
retentionRules:
@ -7525,9 +7574,11 @@ components:
items:
type: object
properties:
stateStatus:
type: string
id:
type: string
name:
pkgName:
type: string
new:
$ref: "#/components/schemas/CheckDiscriminator"
@ -7538,26 +7589,50 @@ components:
items:
type: object
properties:
name:
stateStatus:
type: string
description:
id:
type: string
charts:
type: array
items:
$ref: "#/components/schemas/PkgChart"
pkgName:
type: string
new:
type: object
properties:
name:
type: string
description:
type: string
charts:
type: array
items:
$ref: "#/components/schemas/PkgChart"
old:
type: object
properties:
name:
type: string
description:
type: string
charts:
type: array
items:
$ref: "#/components/schemas/PkgChart"
labels:
type: array
items:
type: object
properties:
stateStatus:
type: string
id:
type: string
name:
pkgName:
type: string
new:
type: object
properties:
name:
type: string
color:
type: string
description:
@ -7565,6 +7640,8 @@ components:
old:
type: object
properties:
name:
type: string
color:
type: string
description:
@ -7574,16 +7651,20 @@ components:
items:
type: object
properties:
isNew:
type: boolean
status:
type: string
resourceType:
type: string
resourceID:
type: string
resourcePkgName:
type: string
resourceName:
type: string
labelID:
type: string
labelPkgName:
type: string
labelName:
type: string
notificationEndpoints:
@ -7591,9 +7672,11 @@ components:
items:
type: object
properties:
stateStatus:
type: string
id:
type: string
name:
pkgName:
type: string
new:
$ref: "#/components/schemas/NotificationEndpointDiscrimator"
@ -7604,79 +7687,170 @@ components:
items:
type: object
properties:
name:
stateStatus:
type: string
description:
id:
type: string
endpointName:
pkgName:
type: string
endpointID:
type: string
endpointType:
type: string
every:
type: string
offset:
type: string
messageTemplate:
type: string
status:
type: string
statusRules:
type: array
items:
type: object
properties:
currentLevel:
new:
type: object
properties:
name:
type: string
previousLevel:
description:
type: string
tagRules:
type: array
items:
type: object
properties:
key:
endpointName:
type: string
value:
endpointID:
type: string
operator:
endpointType:
type: string
every:
type: string
offset:
type: string
messageTemplate:
type: string
status:
type: string
statusRules:
type: array
items:
type: object
properties:
currentLevel:
type: string
previousLevel:
type: string
tagRules:
type: array
items:
type: object
properties:
key:
type: string
value:
type: string
operator:
type: string
old:
type: object
properties:
name:
type: string
description:
type: string
endpointName:
type: string
endpointID:
type: string
endpointType:
type: string
every:
type: string
offset:
type: string
messageTemplate:
type: string
status:
type: string
statusRules:
type: array
items:
type: object
properties:
currentLevel:
type: string
previousLevel:
type: string
tagRules:
type: array
items:
type: object
properties:
key:
type: string
value:
type: string
operator:
type: string
tasks:
type: array
items:
type: object
properties:
name:
stateStatus:
type: string
cron:
id:
type: string
description:
type: string
every:
type: string
offset:
type: string
query:
type: string
status:
pkgName:
type: string
new:
type: object
properties:
name:
type: string
cron:
type: string
description:
type: string
every:
type: string
offset:
type: string
query:
type: string
status:
type: string
old:
type: object
properties:
name:
type: string
cron:
type: string
description:
type: string
every:
type: string
offset:
type: string
query:
type: string
status:
type: string
telegrafConfigs:
type: array
items:
$ref: "#/components/schemas/TelegrafRequest"
type: object
properties:
stateStatus:
type: string
id:
type: string
pkgName:
type: string
new:
$ref: "#/components/schemas/TelegrafRequest"
old:
$ref: "#/components/schemas/TelegrafRequest"
variables:
type: array
items:
type: object
properties:
stateStatus:
type: string
id:
type: string
name:
pkgName:
type: string
new:
type: object
properties:
name:
type: string
description:
type: string
args:
@ -7684,6 +7858,8 @@ components:
old:
type: object
properties:
name:
type: string
description:
type: string
args:
@ -7712,6 +7888,8 @@ components:
type: string
orgID:
type: string
pkgName:
type: string
name:
type: string
description:
@ -8838,7 +9016,7 @@ components:
description: Colors define color encoding of data into a visualization
type: array
items:
type: string
$ref: "#/components/schemas/DashboardColor"
Axes:
description: The viewport for a View's visualizations
type: object

3
assets/js/content-interactions.js
View File

@ -16,7 +16,8 @@ var elementWhiteList = [
".code-tabs p a",
".truncate-toggle",
".children-links a",
".list-links a"
".list-links a",
"a.url-trigger"
]
$('.article a[href^="#"]:not(' + elementWhiteList + ')').click(function (e) {

117
assets/js/influxdb-url.js Normal file
View File

@ -0,0 +1,117 @@
var defaultUrl = "http://localhost:9999"
var elementSelector = ".article--content pre:not(.preserve)"
// Retrieve the selected URL from the influxdb_url session cookie
function getUrl() {
var currentUrl = Cookies.get('influxdb_url')
if (typeof currentUrl == 'undefined' ) {
return defaultUrl
} else {
return currentUrl
}
}
// Retrieve the previously selected URL from the influxdb_prev_url session cookie
// This is used to update URLs whenever you switch between browser tabs
function getPrevUrl() {
var prevUrl = Cookies.get('influxdb_prev_url')
if (typeof prevUrl == 'undefined' ) {
return defaultUrl
} else {
return prevUrl
}
}
// Iterate through code blocks and update InfluxDB urls
function updateUrls(currentUrl, newUrl) {
if (typeof currentUrl != newUrl) {
$(elementSelector).each(function() {
$(this).html($(this).html().replace(currentUrl, newUrl));
});
}
}
// Append the URL selector button to each codeblock with an InfluxDB URL
function appendUrlSelector(currentUrl) {
$(elementSelector).each(function() {
var code = $(this).html()
if (code.includes(currentUrl)) {
$(this).after("<div class='select-url'><a class='url-trigger' href='#'>Cloud or OSS?</a></div>")
$('.select-url').fadeIn(400)
}
});
}
// Toggle the URL selector modal window
function toggleModal() {
$(".modal").fadeToggle(200).toggleClass("open")
}
// Set the selected URL radio button to :checked
function setRadioButton(currentUrl) {
$('input[name="influxdb-loc"][value="' + currentUrl + '"]').prop("checked", true)
}
// Store the InfluxDB URL session cookies – influxdb_url and influxdb_prev_url
function storeUrl(newUrl, prevUrl) {
Cookies.set('influxdb_prev_url', prevUrl)
Cookies.set('influxdb_url', newUrl)
}
// Preserver URLs in codeblocks that come just after or are inside a div
// with the class, .keep-url
function addPreserve() {
$('.keep-url').each(function () {
// For code blocks with no syntax highlighting
$(this).next('pre').addClass('preserve')
// For code blocks with syntax highlighting
$(this).next('.highlight').find('pre').addClass('preserve')
// For code blocks inside .keep-url div
// Special use case for codeblocks generated from yaml data / frontmatter
$(this).find('pre').addClass('preserve')
})
}
// Update URLs when selected in the modal
$('input[name="influxdb-loc"]').change(function() {
var newUrl = $(this).val()
updateUrls(getUrl(), newUrl)
storeUrl(newUrl, getUrl())
})
// Add the preserve tag to code blocks that shouldn't be udpated
addPreserve()
// Update URLs on load
updateUrls(defaultUrl, getUrl())
// Append URL selector buttons to code blocks
appendUrlSelector(getUrl())
// Set active radio button on page load
setRadioButton(getUrl())
// Update URLs whenever you focus on the browser tab
$(window).focus(function() {
updateUrls(getPrevUrl(), getUrl())
setRadioButton(getUrl())
});
// Toggle modal window on click
$("#modal-close, .modal-overlay, .url-trigger").click(function(e) {
e.preventDefault()
toggleModal()
})
// Show the feature callout on page load
if ( Cookies.get('influxdb_url_selector_seen') != 'true' ) {
$('#callout-url-selector').fadeIn(300).removeClass('start-position')
}
// Set feature cookie when the button is clicked
$('button.url-trigger, #callout-url-selector .close').click(function() {
if ( Cookies.get('influxdb_url_selector_seen') != 'true') {
Cookies.set('influxdb_url_selector_seen', 'true')
$('#callout-url-selector').fadeOut(200)
}
})

2
assets/js/jquery-3.3.1.min.js vendored
View File

File diff suppressed because one or more lines are too long

2
assets/js/jquery-3.5.0.min.js vendored Normal file
View File

File diff suppressed because one or more lines are too long

54
assets/styles/layouts/_api-overrides.scss
View File

@ -37,7 +37,7 @@ $bold: 700;
margin-left: -25px;
border-radius: 50%;
border: 3px solid $g16-pearl;
border-top-color: $cp-comet;
border-top-color: $br-pulsar;
animation: spinner .6s linear infinite;
}
@ -47,7 +47,7 @@ $bold: 700;
font-family: $rubik;
padding: 15px 20px ;
display: block;
background-color: $wp-violentdark;
background-color: $g2-kevlar;
a {
color: $g20-white;
text-decoration: none;
@ -141,21 +141,21 @@ $bold: 700;
// Required tags
.jsTAxL {
color: $o-curacao;
color: $r-curacao;
}
///////////////////////////// RESPONSE COLOR BLOCKS ////////////////////////////
// Green
.hLVzSF {
background-color: rgba($gr-wasabi, .5);
.hLVzSF, .fDvFMp {
background-color: rgba($gr-honeydew, .2);
color: $gr-emerald;
}
// Red
.byLrBg {
background-color: rgba($o-marmelade, .35);
color: $o-curacao;
background-color: rgba($r-curacao, .1);
color: $r-curacao;
}
@ -168,7 +168,7 @@ $bold: 700;
}
.gpbcFk:hover, .sc-eTuwsz.active {
background-color: rgb(237, 237, 237);
background-color: $g17-whisper;
}
// List item text
@ -182,23 +182,23 @@ $bold: 700;
// Request method tags
.cFwMcp {
&.post { background-color: $b-curious; }
&.get { background-color: $gr-canopy; }
&.put { background-color: $cp-comet; }
&.patch { background-color: $ch-keylime; }
&.delete { background-color: $o-curacao; }
&.post { background-color: $b-ocean; }
&.get { background-color: $gr-rainforest; }
&.put { background-color: $br-galaxy; }
&.patch { background-color: $y-thunder; color: rgba($g5-pepper, .75);}
&.delete { background-color: $r-curacao; }
}
// Active nav section
.gcUzvG, .iNzLCk:hover {
color: $m-magenta;
color: $br-magenta;
}
/////////////////////////////// RIGHT CODE COLUMN //////////////////////////////
// Right column backgrounds
.dtUibw, .fLUKgj {
background-color: $wp-jagger;
background-color: $g2-kevlar;
h3,h4,h5,h6 {
font-family: $rubik !important;
font-weight: $medium !important;
@ -207,19 +207,19 @@ $bold: 700;
// Code backgrounds
.irpqyy > .react-tabs__tab-panel {
background-color: $wp-telopea;
background-color: $g0-obsidian;
}
.dHLKeu, .fVaxnA {
padding-left: 10px;
background-color: $wp-telopea;
background-color: $g0-obsidian;
}
// Response code tabs
.irpqyy > ul > li {
background-color: $wp-telopea;
background-color: $g0-obsidian;
border-radius: 3px;
&.react-tabs__tab--selected{ color: $cp-blueviolet; }
&.tab-error { color: $o-fire; }
&.react-tabs__tab--selected{ color: $br-pulsar;}
&.tab-error { color: $r-fire; }
&.tab-success { color: $gr-viridian; }
}
@ -234,15 +234,15 @@ $bold: 700;
letter-spacing: .04em;
border-radius: 3px;
}
.bNYCAJ { background-color: $b-curious; } /* Post */
.jBjYbV { background-color: $gr-canopy; } /* Get */
.hOczRB { background-color: $cp-comet; } /* Put */
.fRsrDc { background-color: $ch-chartreuse; color: $ch-olive; } /* Patch */
.hPskZd { background-color: $o-curacao; } /* Delete */
.bNYCAJ { background-color: $b-ocean; } /* Post */
.jBjYbV { background-color: $gr-viridian; } /* Get */
.hOczRB { background-color: $br-galaxy; } /* Put */
.fRsrDc { background-color: $y-thunder; color: $g5-pepper; } /* Patch */
.hPskZd { background-color: $r-curacao; } /* Delete */
// Content type block
.gzAoUb {
background-color: rgba($wp-jagger, .4);
background-color: $g2-kevlar;
font-family: $rubik;
}
.iENVAs { font-family: $roboto-mono; }
@ -259,7 +259,7 @@ $bold: 700;
.jCgylq {
.token.string {
color: $gr-honeydew;
& + a { color: $b-malibu; }
& + a { color: $b-pool; }
}
.token.boolean { color: #f955b0; }
}

31
assets/styles/layouts/_article.scss
View File

@ -108,6 +108,7 @@
"article/lists",
"article/note",
"article/pagination-btns",
"article/product-tags",
"article/related",
"article/scrollbars",
"article/svgs",
@ -137,6 +138,36 @@
transition: opacity .2s;
&:hover {opacity: 1;}
}
/////////////////////////// Getting Started Buttons //////////////////////////
.get-started-btns {
display: flex;
flex-direction: column;
justify-content: space-around;
align-items: flex-start;
margin-bottom: 2rem;
a.btn {
max-width: 300px;
width: 100%;
text-align: center;
padding: 1rem;
.oss:after {
content: 'beta';
display: inline-block;
position: relative;
font-style: italic;
font-size: .75em;
margin-left: .15rem;
padding: .1rem .4rem .12rem;
border-radius: 1rem;
border: 1px solid rgba($g20-white, .5);
top: -1px
}
}
}
}
////////////////////////////////////////////////////////////////////////////////

6
assets/styles/layouts/_error-page.scss
View File

@ -61,12 +61,12 @@
margin-right: 4px;
padding: .75rem 1rem;
border-radius: $radius;
background: $error-page-btn;
text-align: center;
color: $error-page-btn-text;
transition: background-color .2s;
@include gradient($grad-blue);
&:hover {
background: $error-page-btn-hover;
color: $error-page-btn-hover-text;
@include gradient($grad-blue);
}
&.back:before {
content: "\e90a";

66
assets/styles/layouts/_feature-callouts.scss Normal file
View File

@ -0,0 +1,66 @@
.feature-callout {
padding: .5rem .5rem .5rem .75rem;
@include gradient($grad-DesertFestival)
border-radius: $radius;
font-size: .95rem;
font-style: italic;
font-weight: $medium;
color: $g20-white;
box-shadow: 2px 2px 6px rgba($g2-kevlar, .35);
// temp styles for animation
transition: margin .3s ease-out;
display: none;
p {
position: relative;
margin: 0;
&:after {
content: "";
position: absolute;
width: 0;
height: 0;
border-style: solid;
}
&:hover {
cursor: default;
}
}
.new {
display: inline-block;
position: relative;
margin-right: .25rem;
font-size: .8rem;
padding: .1rem .35rem;
background: rgba($g20-white, .25);
border-radius: 1rem;
}
.close {
margin-left: .5rem;
color: rgba($g20-white, .5);
text-decoration: none;
&:hover {
color: rgba($g20-white, .9);
}
}
}
#callout-url-selector {
position: absolute;
top: 3.25rem;
right: 1rem;
p:after {
top: -1rem;
right: 1.85rem;
border-width: 0 7px 8px 7px;
border-color: transparent transparent #CB39C4 transparent;
}
&.start-position {
margin-top: 2.5rem
}
}

7
assets/styles/layouts/_global.scss
View File

@ -8,15 +8,12 @@ $bold: 700;
html {
height: 100%;
background: $body-bg;
}
body {
min-height: 100%;
font-family: 'Rubik', sans-serif;
background: radial-gradient(circle at 100% 0%, $body-gradient-top 0%, $body-gradient-bottom) 30%;
background-repeat: no-repeat;
background-attachment: fixed;
background: $body-bg;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
}
@ -26,7 +23,7 @@ body {
}
a {
transition: all .2s;
transition: color .2s, background-color .2s;
}
.page-wrapper {

164
assets/styles/layouts/_inline-icons.scss
View File

@ -48,24 +48,162 @@
}
}
.nav-icon {
background: linear-gradient(to right, #00A3FF, #BE2EE4);
font-family: $rubik;
.nav-item {
display: inline-block;
padding: 1rem 1.1rem;
border-radius: 0 5px 5px 0;
font-size: 1.05rem;
margin-bottom: 1rem;
position: relative;
vertical-align: top;
margin-bottom: 1.25rem;
.icon {
font-size: 1.65rem;
vertical-align: middle;
&:after {
content: "";
position: absolute;
top: 0;
left: 0;
width: 2px;
height: 100%;
background: #be2ee4;
background: linear-gradient(180deg,#be2ee4 0,#00a3ff);
}
&:first-child {
margin-right: 1.25rem;
}
strong {
color: $g20-white;
font-weight: $medium;
&.account {
padding: .25rem;
position: relative;
width: 210px;
height: 56px;
&:after { display: none; }
.acct-inner {
display: flex;
position: relative;
align-items: center;
width: 100%;
height: 100%;
background: $article-nav-acct-bg;
border-radius: 6px;
border: 3px solid $g8-storm;
&:after {
content: "";
position: absolute;
right: 1rem;
width: 0;
height: 0;
border-style: solid;
border-width: 5px 5px 0 5px;
border-color: $g16-pearl transparent transparent transparent;
}
}
.acct-icon {
margin: 0 .9rem 0 .5rem;
border-radius: 50%;
height: 28px;
width: 28px;
background: linear-gradient(45deg,#00a3ff,#67d74e);
color: $g20-white;
text-align: center;
line-height: 0;
overflow: hidden;
.icon {
margin-left: -.1rem;
font-size: 2rem;
}
}
.acct-label {
.username { color: $g16-pearl; font-weight: $medium; font-size: .85rem; line-height: 1.2rem; }
.orgname { color: $g11-sidewalk; font-size: .75rem; line-height: .75rem; }
}
&.small {
width: 56px;
.acct-inner {
justify-content: center;
align-items: center;
&:after { display: none; }
}
.acct-icon { margin: 0 }
}
}
}
.nav-icon {
display: flex;
justify-content: left;
align-items: center;
color: $g20-white;
width: 210px;
height: 56px;
font-family: $rubik;
font-weight: $medium;
padding: .9rem 1.1rem;
font-size: 1rem;
position: relative;
background: $article-nav-icon-bg;
.icon {
display: inline-block;
font-size: 1.35rem;
margin-right: 1rem;
}
.nav-icon-label {
display: inline-block;
padding: 0;
font-size: 1rem;
}
&:before, &:after {
content: "";
position: absolute;
left: 0;
height: 2px;
z-index: 2;
width: 12px;
}
&:before {
top: 0;
background: #be2ee4;
background: linear-gradient(90deg,#be2ee4 0,rgba(190,46,228,0));
}
&:after {
bottom: 0;
background: #00a3ff;
background: linear-gradient(90deg,#00a3ff 0,rgba(190,46,228,0));
}
&.small {
display: flex;
justify-content: center;
align-items: center;
padding: 0;
width: 56px;
flex-direction: column;
.icon {
position: relative;
margin: 0;
}
.nav-icon-label {
padding: 0;
margin-top: .75rem;
font-size: .67rem;
line-height: 0;
}
}
}
}
///////////////////////////////// MEDIA QUERIES ////////////////////////////////
@include media(small) {
.article--content .nav-item:nth-child(2) {display: none;}
}

30
assets/styles/layouts/_landing.scss
View File

@ -5,7 +5,7 @@
overflow: hidden;
border-radius: $radius 0 0 $radius;
min-height: 700px;
background: linear-gradient(55deg, $landing-lg-gradient-left, $landing-lg-gradient-right );
@include gradient($landing-artwork-gradient);
a {
text-decoration: none;
@ -99,15 +99,32 @@
&#get-started {
.btn {
position: relative;
display: inline-block;
padding: 1.25rem;
margin: 0 20% .35rem;
color: $landing-btn-text;
font-size: 1.1rem;
font-weight: $medium;
background: $landing-btn-bg;
@include gradient($landing-btn-grad);
transition: background-color .2s, color .2s;
border-radius: $radius;
z-index: 1;
&:before {
content: "";
position: absolute;
display: block;
top: 0;
right: 0;
width: 100%;
height: 100%;
border-radius: $radius;
@include gradient($landing-btn-grad-hover);
opacity: 0;
transition: opacity .2s;
z-index: -1;
}
&.oss:after {
content: 'beta';
@ -116,16 +133,14 @@
font-style: italic;
font-size: .75em;
margin-left: .45rem;
padding: .1rem .3rem .12rem;
border-radius: $radius;
padding: .1rem .4rem .12rem;
border-radius: 1rem;
border: 1px solid rgba($landing-btn-text, .5);
transition: border-color .2s;
}
&:hover {
background: $landing-btn-bg-hover;
color: $landing-btn-text-hover;
&:after { border-color: rgba($landing-btn-text-hover, .5) }
&:before { opacity: 1; }
}
}
}
@ -158,7 +173,6 @@
flex-grow: 2;
width: 49%;
text-align: center;
background: $landing-sm-bg-alt;
h3 {
margin: 0 0 .5rem;
font-size: 1.1rem;

216
assets/styles/layouts/_modal.scss Normal file
View File

@ -0,0 +1,216 @@
.modal {
display: none;
padding: 1rem;
position: fixed;
top: 0;
width: 100%;
height: 100%;
z-index: 100;
.modal-overlay {
position: absolute;
top:0;
left:0;
width: 100%;
height: 100%;
@include gradient($grad-Miyazakisky);
opacity: .85;
}
.modal-wrapper {
display: flex;
justify-content: center;
align-items: flex-start;
}
.modal-body {
position: relative;
display: flex;
overflow: hidden;
max-width: 650px;
max-height: 95vh;
margin-top: 10vh;
padding: .75rem 2rem 1.5rem;
border-radius: $radius * 1.5;
background: $article-bg;
color: $article-text;
font-size: 1rem;
transition: margin .4s;
}
&.open {
.modal-body { margin-top: 0; }
}
#modal-close {
position: absolute;
padding: .25rem;
top: 1rem;
right: 1rem;
color: rgba($article-text, .5);
transition: color .2s;
text-decoration: none;
&:hover {
color: $article-text;
}
}
.modal-content{
overflow: scroll;
h3 {
color: $article-heading;
font-weight: $medium;
font-size: 1.4rem;
margin-bottom: 1rem;
}
h4 {
color: $article-heading;
font-weight: $medium;
margin: 1rem 0 .5rem $radius;
}
h5 {
margin: .5rem 0 0;
color: $article-bold;
}
p,li {
margin: .25rem 0;
line-height: 1.5rem;
strong {
font-weight: $medium;
color: $article-bold;
}
&.note {
padding-top: 1.25rem;
margin-top: 1.5rem;
color: rgba($article-text, .5);
border-top: 1px solid rgba($article-text, .25);
font-size: .9rem;
font-style: italic;
}
}
a {
color: $article-link;
font-weight: $medium;
text-decoration: none;
transition: color .2s;
&:hover {
color: $article-link-hover;
}
}
}
.products {
display: flex;
flex-wrap: wrap;
flex-grow: 1;
justify-content: flex-start;
}
.product {
margin-right: .5rem;
.providers{
display: flex;
flex-wrap: wrap;
padding: .5rem 1rem;
background: rgba($article-text, .05);
border-radius: $radius;
.provider {
flex-grow: 1;
&:not(:last-child) {margin-right: 1rem;}
}
ul {
margin: .5rem .5rem .5rem 0;
padding: 0;
list-style: none;
}
}
}
.radio {
position: relative;
display: inline-block;
height: 1.15em;
width: 1.15em;
background: rgba($article-text, .05);
margin: 0 .3rem 0 .1rem;
vertical-align: text-top;
border-radius: $radius;
cursor: pointer;
border: 1.5px solid rgba($article-text, .2);
user-select: none;
}
input[type='radio'] {
margin-right: -1.1rem ;
padding: 0;
vertical-align: top;
opacity: 0;
cursor: pointer;
& + .radio:after {
content: "";
display: block;
position: absolute;
height: .5rem;
width: .5rem;
border-radius: 50%;
background: $article-link;
top: 50%;
left: 50%;
opacity: 0;
transform: scale(2) translate(-20%, -20%);
transition: all .2s;
}
&:checked + .radio:after {
opacity: 1;
transform: scale(1) translate(-50%, -50%);
}
}
}
///////////////////////////// InfluxDB URL Triggers ////////////////////////////
.article--content {
.select-url {
margin: -2.5rem 0 1rem;
text-align: right;
display: none;
}
.url-trigger {
padding: .25rem .5rem;
display: inline-block;
font-size: .85rem;
font-style: italic;
color: rgba($article-tab-code-text, .5);
background: $article-code-bg;
border-radius: 0 0 $radius $radius;
&:before {
content: "\e923";
display: inline-block;
margin-right: .35rem;
font-family: "icomoon";
font-style: normal;
font-size: .8rem;
}
&:hover {
color: $article-tab-code-text;
}
}
.code-tab-content {
.select-url{margin-top: -3.25rem}
}
}

40
assets/styles/layouts/_sidebar.scss
View File

@ -167,7 +167,47 @@
text-decoration: none;
font-weight: $medium;
display: inline-block;
/////////////////////// Product exclusivity labels ///////////////////////
span:after{
display: inline-block;
position: relative;
top: -2px;
margin-left: .15rem;
padding: .45rem .18rem .35rem;
line-height: 0;
font-size: .6rem;
font-style: italic;
border-radius: 8px;
}
.cloud {
&:after {
content: "CLOUD";
color: $product-cloud;
border: 1px solid rgba($product-cloud, .5);
background: rgba($product-cloud, .1);
}
}
.oss {
&:after {
content: "OSS";
color: $product-oss;
border: 1px solid rgba($product-oss, .5);
background: rgba($product-oss, .1);
}
}
.enterprise {
&:after {
content: "ENT";
color: $product-enterprise;
border: 1px solid rgba($product-enterprise, .5);
background: rgba($product-enterprise, .1);
}
}
}
////////////////////// End Product exclusivity labels //////////////////////
.nav-category > a {
color: $nav-category;
font-size: 1.1rem;

4
assets/styles/layouts/_syntax-highlighting.scss
View File

@ -1,3 +1,5 @@
pre { line-height: 1.25rem; }
code[class*="language-"],
pre[class*="language-"] {
/*text-shadow: 0 1px #101419;*/
@ -50,8 +52,6 @@ pre[class*="language-"] {
.highlight { color: $article-code;
line-height: 1.25rem;
// COLORS
.gh, /* Generic.Heading */

33
assets/styles/layouts/_top-nav.scss
View File

@ -36,18 +36,18 @@
}
.version-selector {
display: inline-block;
position: absolute;
z-index: 100;
right: 3.5rem;
color: $g20-white;
height: 2rem;
background: $version-selector-top;
font-weight: $medium;
border-radius: $radius;
overflow: hidden;
cursor: pointer;
transition: right .2s;
display: inline-block;
position: absolute;
z-index: 100;
right: 5.5rem;
color: $g20-white;
height: 2rem;
@include gradient($version-selector-gradient);
font-weight: $medium;
border-radius: $radius;
overflow: hidden;
cursor: pointer;
transition: right .2s;
.selected {
padding: 0 1.75rem 0 .75rem;
@ -65,7 +65,6 @@
&.open {
height: auto;
background: linear-gradient($version-selector-top, $version-selector-bottom);
&:after {
transform: rotate(180deg);
}
@ -102,7 +101,7 @@
}
}
.theme-switcher, #search-btn {
.theme-switcher, #search-btn, .url-trigger {
display: inline-block;
padding: 0;
font-size: 1.8rem;
@ -126,6 +125,12 @@
&#theme-switch-light { display: $theme-switch-light; }
}
.url-trigger {
font-size: 1.1rem;
vertical-align: top;
margin: .1rem 0 0 0;
}
#search-btn {
opacity: 0;
}

47
assets/styles/layouts/_ui-messages.scss
View File

@ -1,47 +0,0 @@
.article--content {
.ui-message {
display: flex;
align-items: center;
width: 375px;
margin: 1rem 0 2rem;
padding: .85rem 0;
font-family: $rubik;
font-size: .9rem;
border-radius: 5px;
color: $g20-white;
.icon, .close {
width: 13%;
text-align: center;
font-family: 'icomoon';
font-size: 1.1rem;
}
.close:after {
content: "\e932";
opacity: .25;
}
.text {
width: 74%;
font-weight: $medium;
}
&.green {
background: linear-gradient(45deg, #34bb56, #00a3fe);
.icon:before { content: ""; }
}
&.blue {
background: linear-gradient(45deg, rgb(190, 46, 228), rgb(0, 163, 255));
.icon:before { content: "\e935"; }
}
&.red {
background: linear-gradient(45deg, rgb(220, 78, 88), rgb(142, 31, 195));
.icon:before { content: "\e920"; }
}
}
}

29
assets/styles/layouts/article/_buttons.scss
View File

@ -1,22 +1,43 @@
/////////////////////////////////// Buttons //////////////////////////////////
a.btn {
position: relative;
display: inline-block;
margin: .5rem 0 1rem;
margin: .5rem .25rem .5rem 0;
padding: .5rem 1rem;
background: $article-btn;
color: $article-btn-text;
border-radius: $radius;
font-size: .95rem;
z-index: 1;
@include gradient($grad-blue);
&:after {
content: "";
position: absolute;
display: block;
top: 0;
right: 0;
width: 100%;
height: 100%;
border-radius: $radius;
@include gradient($grad-blue-light);
opacity: 0;
transition: opacity .2s;
z-index: -1;
}
&:hover {
background: $article-btn-hover;
color: $article-btn-text-hover;
cursor: pointer;
&:after {
opacity: 1;
}
}
&.download:before {
content: "\e91c";
font-family: "icomoon";
margin-right: .5rem;
font-size: 1.1rem;
}
}

59
assets/styles/layouts/article/_cloud.scss
View File

@ -1,37 +1,4 @@
.cloud {
position: relative;
padding: 0 0 .01rem 2rem;
margin-left: -2rem;
border-left: 2px solid $article-cloud-base;
.cloud-flag {
&:hover {
transform: scale(1);
color: $g20-white;
}
}
}
.cloud-flag {
padding: .2rem .4rem;
font-size: .75rem;
font-style: normal;
font-weight: bold;
color: $g20-white;
border-radius: $radius;
vertical-align: text-bottom;
background: $article-cloud-base;
position: absolute;
top: -.15rem;
left: -.68rem;
transform: scale(.8);
transition: all .2s;
&:before {
content: "C";
}
}
.cloud-msg {
border-color: $article-cloud-base;
background: rgba($article-cloud-base, .12);
h1,h2,h3,h4,h5,h6 {
@ -69,7 +36,7 @@
color: $article-cloud-text;
box-shadow: 1px 3px 10px $article-cloud-shadow;
thead{
background: $article-cloud-table-header;
@include gradient($article-cloud-table-header);
}
tr:nth-child(even) td {
background: $article-cloud-table-row-alt;
@ -79,6 +46,14 @@
border-color: rgba($article-cloud-text, .25);
p { color: rgba($article-cloud-text, .6); }
}
.code-tabs-wrapper .code-tabs a {
background: transparent;
color: rgba($article-cloud-text, .5);
&:hover { color: rgba($article-cloud-text, 1); }
&.is-active {
color: rgba($article-cloud-text, 1);
background: $article-cloud-code-bg};
}
&.flex {
font-style: italic;
@ -89,19 +64,3 @@
}
}
}
////////////////////////////////////////////////////////////////////////////////
///////////////////////////////// MEDIA QUERIES ////////////////////////////////
////////////////////////////////////////////////////////////////////////////////
@include media(small) {
.cloud-msg .cloud-flag { margin-left: .5rem }
.cloud {
padding: 0 0 .01rem .85rem;
margin-left: -.85rem;
.cloud-flag {
left: -.25rem;
}
}
}

51
assets/styles/layouts/article/_enterprise.scss
View File

@ -1,37 +1,4 @@
.enterprise {
position: relative;
padding: 0 0 .01rem 2rem;
margin-left: -2rem;
border-left: 2px solid $article-enterprise-base;
.enterprise-flag {
&:hover {
transform: scale(1);
color: $g20-white;
}
}
}
.enterprise-flag {
padding: .2rem .4rem;
font-size: .75rem;
font-style: normal;
font-weight: bold;
color: $g20-white;
border-radius: $radius;
vertical-align: text-bottom;
background: $article-enterprise-base;
position: absolute;
top: -.15rem;
left: -.68rem;
transform: scale(.8);
transition: all .2s;
&:before {
content: "E";
}
}
.enterprise-msg {
border-color: $article-enterprise-base;
background: rgba($article-enterprise-base, .15);
p,li {
@ -50,21 +17,3 @@
}
}
}
////////////////////////////////////////////////////////////////////////////////
///////////////////////////////// MEDIA QUERIES ////////////////////////////////
////////////////////////////////////////////////////////////////////////////////
@include media(small) {
.enterprise-msg .enterprise-flag {
margin-left: .5rem;
}
.enterprise {
padding: 0 0 .01rem .85rem;
margin-left: -.85rem;
.enterprise-flag {
left: -.25rem;
}
}
}

12
assets/styles/layouts/article/_note.scss
View File

@ -1,6 +1,6 @@
.note {
border-color: $article-note-base;
background: rgba($article-note-base, .12);
background: rgba($article-note-base, .1);
h1,h2,h3,h4,h5,h6 {
color: $article-note-heading;
}
@ -36,7 +36,7 @@
color: $article-note-text;
box-shadow: 1px 3px 10px $article-note-shadow;
thead{
background: $article-note-table-header;
@include gradient($article-note-table-header);
}
tr:nth-child(even) td {
background: $article-note-table-row-alt;
@ -46,4 +46,12 @@
border-color: rgba($article-note-text, .25);
p { color: rgba($article-note-text, .6); }
}
.code-tabs-wrapper .code-tabs a {
background: transparent;
color: rgba($article-note-text, .5);
&:hover { color: rgba($article-note-text, 1); }
&.is-active {
color: rgba($article-note-text, 1);
background: $article-note-code-bg};
}
}

28
assets/styles/layouts/article/_product-tags.scss Normal file
View File

@ -0,0 +1,28 @@
.product-tags {
margin: -2rem 0 2.5rem;
span {
margin-right: .25rem;
padding: .2rem .65rem .25rem;
border-radius: 1rem;
font-weight: $medium;
font-style: italic;
font-size: .85rem;
border: 1px solid;
&.oss {
color: $product-oss;
border-color: rgba($product-oss, .35);
background: rgba($product-oss, .1);
}
&.cloud {
color: $product-cloud;
border-color: rgba($product-cloud, .35);
background: rgba($product-cloud, .1);
}
&.enterprise {
color: $product-enterprise;
border-color: rgba($product-enterprise, .35);
background: rgba($product-enterprise, .1);
}
}
}

2
assets/styles/layouts/article/_scrollbars.scss
View File

@ -11,7 +11,7 @@ table { @include scrollbar($article-table-row-alt, $article-table-scrollbar);}
pre { @include scrollbar($article-warn-code-bg, $article-warn-code-scrollbar); }
table { @include scrollbar($article-warn-table-row-alt, $article-warn-table-scrollbar); }
}
.cloud-msg {
.cloud {
pre { @include scrollbar($article-cloud-code-bg, $article-cloud-code-scrollbar); }
table { @include scrollbar($article-cloud-table-row-alt, $article-cloud-table-scrollbar); }
}

114
assets/styles/layouts/article/_tabbed-content.scss
View File

@ -1,14 +1,9 @@
/////////////////////////////// Tabbed Content ///////////////////////////////
.tabs-wrapper {
margin: 2.5rem 0 .5rem;
}
.tabs-wrapper { margin: 2.5rem 0 .5rem; }
.code-tabs-wrapper { margin: 1.5rem 0 .5rem; }
.code-tabs-wrapper {
margin: 1.5rem 0 .5rem;
}
.tabs, .code-tabs {
.tabs {
p {
display: flex;
flex-wrap: wrap;
@ -16,71 +11,90 @@
a {
flex-grow: 1;
margin: 2px;
position: relative;
font-size: 0.875rem;
font-weight: $medium;
color: $article-tab-text;
padding: .35rem .75rem;
display: inline-block;
text-align: center;
color: $article-tab-text;
border-radius: $radius;
background-color: $article-tab-bg;
transition: background-color .2s, color .2s;
z-index: 1;
&:after {
content: "";
position: absolute;
display: block;
top: 0;
right: 0;
width: 100%;
height: 100%;
border-radius: $radius;
@include gradient($grad-blue);
opacity: 0;
transition: opacity .2s;
z-index: -1;
}
&:hover {
color: $article-tab-active-text;
background: $article-tab-active-bg;
&:after {
opacity: 1;
}
}
&.is-active {
color: $article-tab-active-text;
background: $article-tab-active-bg;
&:after {
opacity: 1;
@include gradient($grad-blue)
}
}
}
}
.code-tabs {
p {
margin: 0;
text-align: right;
display: block;
}
a {
padding: .1rem .75rem;
margin: 0;
border-radius: $radius $radius 0 0;
display: inline-block;
font-size: 0.875rem;
background: $article-bg;
color: rgba($article-tab-code-text, .5);
&:hover {
color: $article-tab-code-text;
}
&.is-active {
background-color: $article-code-bg;
color: $article-tab-code-text;
}
}
}
.code-tab-content {
padding: 0;
pre {
margin: 0 0 3rem;
border-radius: $radius 0 $radius $radius;
}
}
.tab-content, .code-tabs-content {
margin: .75rem 0 3rem;
width: 100%;
& > * {
width: 100% !important;
margin-left: 0 !important;
width: 100%;
margin-left: 0;
}
}
.tab-content:not(:first-of-type),
.code-tab-content:not(:first-of-type) {
display: none;
}
.code-tabs-wrapper {
.code-tabs {
p {
margin: 0;
text-align: right;
display: block;
}
a {
padding: .1rem .75rem;
margin: 0;
border-radius: $radius $radius 0 0;
display: inline-block;
background: $article-tab-code-bg;
color: $article-tab-code-text;
&:hover {
background: $article-tab-code-bg-hover;
color: $article-tab-code-text-hover;
}
&.is-active {
background-color: $article-code-bg;
color: $article-tab-code-active-text;
}
}
}
.code-tab-content {
padding: 0;
pre {
margin: 0 0 3rem;
border-radius: $radius 0 $radius $radius;
}
}
}
.tab-content:not(:first-of-type) { display: none; }
.code-tab-content:not(:first-of-type) { display: none; }

12
assets/styles/layouts/article/_tables.scss
View File

@ -9,23 +9,23 @@ table {
overflow-x: auto;
overflow-y: hidden;
box-shadow: 1px 3px 10px $article-shadow;
border-radius: ($radius * 1.5);
border-radius: ($radius);
th, td {
padding: .85rem 1.25rem;
}
thead {
background: linear-gradient(to right, $article-table-header-left, $article-table-header-right);
@include gradient($article-table-header, 90deg);
background-attachment: fixed;
}
th {
color: $g20-white;
&:first-child {
border-radius: ($radius * 1.5) 0 0 0;
border-radius: ($radius) 0 0 0;
}
&:last-child {
border-radius: 0 ($radius * 1.5) 0 0;
border-radius: 0 ($radius) 0 0;
}
}
@ -40,8 +40,8 @@ table {
}
&:last-child {
td {
&:first-child { border-radius: 0 0 0 ($radius * 1.5); }
&:last-child { border-radius: 0 0 ($radius * 1.5) 0; }
&:first-child { border-radius: 0 0 0 ($radius); }
&:last-child { border-radius: 0 0 ($radius) 0; }
}
}

10
assets/styles/layouts/article/_tags.scss
View File

@ -13,6 +13,16 @@
font-weight: $medium;
color: rgba($article-text, .75);
font-size: .8rem;
border-radius: 1rem;
&:after {
border-radius: 1rem;
@include gradient($grad-MilkyWay)
}
&:hover {
color: $g20-white;
}
}
}

11
assets/styles/layouts/article/_telegraf-plugins.scss
View File

@ -50,7 +50,6 @@
opacity: 0.25;
transition: opacity .2s, background .2s, color .2s;
background-color: rgba($article-btn, 0);
color: $article-bold;
.icon-github {
font-size: 1.2rem;
@ -62,7 +61,6 @@
.github-link {
opacity: 1;
background-color: rgba($article-btn, 1);
color: $g20-white;
}
}
@ -149,6 +147,7 @@
.checkbox {
display: inline-block;
position: relative;
height: 1.15em;
width: 1.15em;
background: rgba($article-text, .05);
@ -175,16 +174,16 @@
width: .5rem;
border-radius: 50%;
background: $article-link;
top: .65rem;
left: .35rem;
top: 50%;
left: 50%;
opacity: 0;
transform: scale(2);
transform: scale(2) translate(-20%, -20%);
transition: all .2s;
}
&:checked + .checkbox:after {
opacity: 1;
transform: scale(1);
transform: scale(1) translate(-50%, -50%);
}
}
}

10
assets/styles/layouts/article/_warn.scss
View File

@ -36,7 +36,7 @@
color: $article-warn-text;
box-shadow: 1px 3px 10px $article-warn-shadow;
thead{
background: $article-warn-table-header;
@include gradient($article-warn-table-header);
}
tr:nth-child(even) td {
background: $article-warn-table-row-alt;
@ -46,4 +46,12 @@
border-color: rgba($article-warn-text, .25);
p { color: rgba($article-warn-text, .6); }
}
.code-tabs-wrapper .code-tabs a {
background: transparent;
color: rgba($article-warn-text, .5);
&:hover { color: rgba($article-warn-text, 1); }
&.is-active {
color: rgba($article-warn-text, 1);
background: $article-warn-code-bg};
}
}

2
assets/styles/sidebar-closed.scss
View File

@ -27,7 +27,7 @@
opacity: 1;
}
.version-selector {
right: 5.5rem;
right: 7.5rem;
}
}

5
assets/styles/styles-default.scss
View File

@ -18,8 +18,9 @@
"layouts/content-wrapper",
"layouts/article",
"layouts/inline-icons",
"layouts/ui-messages",
"layouts/syntax-highlighting",
"layouts/algolia-search-overrides",
"layouts/landing",
"layouts/error-page";
"layouts/error-page",
"layouts/modal",
"layouts/feature-callouts";

175
assets/styles/themes/_theme-dark.scss
View File

@ -14,144 +14,142 @@
@import "tools/color-palette";
$body-bg: $np-deepnight;
$body-gradient-top: rgba($m-magenta, .2);
$body-gradient-bottom: $np-deepnight;
$body-bg: $g0-obsidian;
// TopNav Colors
$topnav-link: $g20-white;
$topnav-link-hover: $b-pool;
$version-selector-top: $b-pool;
$version-selector-bottom: $cp-comet;
$version-selector-gradient: $grad-Miyazakisky;
$theme-switch-light: inline-block;
$theme-switch-dark: none;
// Search
$sidebar-search-bg: $np-deepnight;
$sidebar-search-shadow: rgba($m-magenta, .05);
$sidebar-search-bg: $g2-kevlar;
$sidebar-search-shadow: rgba($g0-obsidian, .05);
$sidebar-search-highlight: $b-pool;
$sidebar-search-text: $g20-white;
// Left Navigation
$nav-category: $b-pool;
$nav-category-hover: $g20-white;
$nav-item: $g16-pearl;
$nav-item: $g15-platinum;
$nav-item-hover: $b-pool;
$nav-border: $wp-jango;
$nav-border: $g5-pepper;
$nav-toggle: $g16-pearl;
$nav-toggle-hover: $g16-pearl;
$nav-toggle-bg-hover: $b-pool;
$nav-active: $ch-chartreuse;
$nav-active: $br-chartreuse;
// Product Flags
$product-cloud: $b-pool;
$product-oss: $p-potassium;
$product-enterprise: $br-galaxy;
// Article Content
$article-bg: $wp-violentdark;
$article-bg: $g1-raven;
$article-heading: $g20-white;
$article-heading-alt: $g19-ghost;
$article-text: $np-mischka;
$article-bold: $g18-cloud;
$article-link: $b-dodger;
$article-text: $g15-platinum;
$article-bold: $g19-ghost;
$article-link: $b-pool;
$article-link-hover: $g20-white;
$article-hr: $wp-seance;
$article-shadow: $np-deepnight;
$article-hr: $g5-pepper;
$article-shadow: $g0-obsidian;
// Article Code
$article-code: $cp-munchkin;
$article-code-bg: $np-deepnight;
$article-code-accent1: $np-smokey;
$article-code-bg: $g0-obsidian;
$article-code-shadow: $g0-obsidian;
$article-code-accent1: $g7-graphite;
$article-code-accent2: $b-pool;
$article-code-accent3: $gr-viridian;
$article-code-accent4: $o-ruby;
$article-code-accent4: $r-ruby;
$article-code-accent5: #ff6db0;
$article-code-accent6: $b-pool;
$article-code-accent7: #e90;
$article-code-select: $b-pool;
$article-code-link: $b-dodger;
$article-code-link: $b-pool;
$article-code-link-hover: $g20-white;
$article-code-scrollbar: $np-martinique;
$article-code-scrollbar: $g3-castle;
// Article Tables
$article-table-header-left: $wp-violet;
$article-table-header-right: $b-curious;
$article-table-row-alt: #3C0C59;
$article-table-scrollbar: $np-deepnight;
$article-table-header: $grad-GundamPilot;
$article-table-row-alt: $g3-castle;
$article-table-scrollbar: $g0-obsidian;
// Article Notes, Warnings, & Messages
$article-note-base: $gr-viridian;
$article-note-heading: $g20-white;
$article-note-text: $gr-viridian;
$article-note-link: $gr-rainforest;
$article-note-text: $gr-honeydew;
$article-note-link: $gr-wasabi;
$article-note-link-hover: $g20-white;
$article-note-table-header: $gr-viridian;
$article-note-table-row-alt: #3B2862;
$article-note-table-scrollbar: $np-deepnight;
$article-note-shadow: $np-deepnight;
$article-note-code: $cp-comet;
$article-note-code-bg: $wp-jaguar;
$article-note-table-header: $grad-green-dark;
$article-note-table-row-alt: #1a3c34;
$article-note-table-scrollbar: #162627;
$article-note-shadow: $g0-obsidian;
$article-note-code: $br-galaxy;
$article-note-code-bg: #0d1617;
$article-note-code-accent1: #567375;
$article-note-code-accent2: $b-pool;
$article-note-code-accent3: $gr-viridian;
$article-note-code-accent4: $o-ruby;
$article-note-code-accent4: $r-ruby;
$article-note-code-accent5: #ff6db0;
$article-note-code-accent6: $b-pool;
$article-note-code-accent7: #e90;
$article-note-code-scrollbar: $cp-jakarta;
$article-note-code-scrollbar: #162627;
$article-warn-base: $o-dreamsicle;
$article-warn-base: $r-dreamsicle;
$article-warn-heading: $g20-white;
$article-warn-text: $o-dreamsicle;
$article-warn-link: $o-tungsten;
$article-warn-text: $r-tungsten;
$article-warn-link: $r-marmelade;
$article-warn-link-hover: $g20-white;
$article-warn-table-header: rgba($o-dreamsicle, .9);
$article-warn-table-row-alt: #531B5B;
$article-warn-table-scrollbar: $wp-telopea;
$article-warn-shadow: $np-deepnight;
$article-warn-table-header: $grad-red;
$article-warn-table-row-alt: #4a2a2a;
$article-warn-table-scrollbar: #1f181b;
$article-warn-shadow: $g0-obsidian;
$article-warn-code: #ec6e6e;
$article-warn-code-bg: $wp-telopea;
$article-warn-code-bg: $g0-obsidian;
$article-warn-code-accent1: #844c4c;
$article-warn-code-accent2: $b-pool;
$article-warn-code-accent3: $gr-viridian;
$article-warn-code-accent4: $o-ruby;
$article-warn-code-accent4: $r-ruby;
$article-warn-code-accent5: #ffb4fb;
$article-warn-code-accent6: $b-pool;
$article-warn-code-accent7: #e90;
$article-warn-code-scrollbar: #561e4d;
$article-warn-code-scrollbar: #2a2025;
$article-cloud-base: $b-pool;
$article-cloud-heading: $g20-white;
$article-cloud-text: $b-fleur;
$article-cloud-link: $b-hawkeye;
$article-cloud-link-hover: $g20-white;
$article-cloud-table-header: $b-pool;
$article-cloud-table-row-alt: #382876;
$article-cloud-table-scrollbar: $np-deepnight;
$article-cloud-shadow: $np-deepnight;
$article-cloud-text: $b-neutrino;
$article-cloud-link: $g20-white;
$article-cloud-link-hover: $b-hydrogen;
$article-cloud-table-header: $grad-blue-dark;
$article-cloud-table-row-alt: #1b3a58;
$article-cloud-table-scrollbar: #192a3a;
$article-cloud-shadow: $g0-obsidian;
$article-cloud-code: $b-laser;
$article-cloud-code-bg: $wp-telopea;
$article-cloud-code-bg: #110d2b;
$article-cloud-code-accent1: #567375;
$article-cloud-code-accent2: $b-pool;
$article-cloud-code-accent3: $gr-viridian;
$article-cloud-code-accent4: $o-ruby;
$article-cloud-code-accent4: $r-ruby;
$article-cloud-code-accent5: #ff6db0;
$article-cloud-code-accent6: $b-pool;
$article-cloud-code-accent7: #e90;
$article-cloud-code-scrollbar: $cp-jakarta;
$article-cloud-code-scrollbar: #192a3a;
$article-enterprise-base: $cp-purple;
$article-enterprise-text: $cp-periwinkle;
$article-enterprise-link: $cp-coolfog;
$article-enterprise-base: $br-galaxy;
$article-enterprise-text: $cp-melrose;
$article-enterprise-link: $cp-titan;
$article-enterprise-link-hover: $g20-white;
// Article Tabs for tabbed content
$article-tab-text: $g12-forge;
$article-tab-bg: rgba($np-deepnight, .6);
$article-tab-bg: $g0-obsidian;
$article-tab-active-text: $g20-white;
$article-tab-active-bg: $b-pool;
$article-tab-code-text: $g9-mountain;
$article-tab-code-bg: rgba($np-deepnight, .45);
$article-tab-code-text-hover: $g20-white;
$article-tab-code-bg-hover: $b-pool;
$article-tab-code-active-text: $g20-white;
$article-tab-code-text: $g20-white;
// Article page buttons
$article-btn: $b-pool;
@ -159,40 +157,41 @@ $article-btn-text: $g20-white;
$article-btn-hover: $b-pool;
$article-btn-text-hover: $g20-white;
// Article UI nav icons
$article-nav-icon-bg: $g5-pepper;
$article-nav-acct-bg: $g3-castle;
// Error Page Colors
$error-page-btn: $b-dodger;
$error-page-btn: $b-pool;
$error-page-btn-text: $g20-white;
$error-page-btn-hover: $g20-white;
$error-page-btn-hover-text: $b-dodger;
$error-page-btn-hover-text: $b-pool;
// Landing Page colors
$landing-lg-gradient-left: $wp-violentdark;
$landing-lg-gradient-right: $cp-minsk;
$landing-sm-bg: $cp-victoria;
$landing-sm-bg-alt: $cp-victoria;
$landing-sm-bg-hover: $b-dodger;
$landing-artwork-gradient: $grad-GrapeSoda;
$landing-artwork-color: rgba($br-galaxy, .25);
$landing-sm-bg: rgba($g1-raven, .4);
$landing-sm-bg-hover: $b-pool;
$landing-btn-text: $g20-white;
$landing-btn-bg: $b-dodger;
$landing-btn-text-hover: $b-dodger;
$landing-btn-bg-hover: $g20-white;
$landing-artwork-color: $cp-minsk;
$landing-btn-grad: $grad-blue;
$landing-btn-grad-hover: $grad-blue-light;
// Tooltip colors
$tooltip-color: $ch-chartreuse;
$tooltip-color-alt: $ch-canary;
$tooltip-bg: $g20-white;
$tooltip-text: $cp-minsk;
$tooltip-color: $br-chartreuse;
$tooltip-color-alt: $br-chartreuse;
$tooltip-bg: $br-chartreuse;
$tooltip-text: $g2-kevlar;
// SVG colors
$svg-table-header: $cp-minsk;
$svg-table-stroke: $np-deepnight;
$svg-table-row-alt1: $m-magenta;
$svg-table-row-alt2: $gr-canopy;
$svg-table-code: $cp-munchkin;
$svg-table-code-bg: $np-deepnight;
$svg-table-header: $g6-smoke;
$svg-table-stroke: $g0-obsidian;
$svg-table-row-alt1: $br-magenta;
$svg-table-row-alt2: $gr-rainforest;
$svg-table-code: $article-code;
$svg-table-code-bg: $g0-obsidian;
$svg-table-code-operator: $b-pool;
$svg-table-code-string: $gr-viridian;
$svg-geo-s2-cell: $b-curious;
$svg-geo-region: $m-lavander;
$svg-geo-point: $ch-chartreuse;
$svg-geo-s2-cell: $b-dodger;
$svg-geo-region: $p-comet;
$svg-geo-point: $br-chartreuse;

148
assets/styles/themes/_theme-light.scss
View File

@ -15,64 +15,66 @@
// --------------------------------------------------
$body-bg: $g18-cloud !default;
$body-gradient-top: $g19-ghost !default;
$body-gradient-bottom: $g17-whisper !default;
$radius: 3px !default;
// TopNav Colors
$topnav-link: $g8-storm !default;
$topnav-link-hover: $b-dodger !default;
$version-selector-top: $b-pool !default;
$version-selector-bottom: $cp-comet !default;
$version-selector-gradient: $grad-PastelGothic !default;
$theme-switch-light: none !default;
$theme-switch-dark: inline-block !default;
// Search
$sidebar-search-bg: $g20-white !default;
$sidebar-search-shadow: $g14-chromium !default;
$sidebar-search-highlight: $b-dodger !default;
$sidebar-search-highlight: $b-pool !default;
$sidebar-search-text: $g8-storm !default;
// Left Navigation
$nav-category: $b-dodger !default;
$nav-category-hover: $cp-purple !default;
$nav-item: $np-rum !default;
$nav-item-hover: $cp-purple !default;
$nav-category-hover: $br-magenta !default;
$nav-item: $g9-mountain !default;
$nav-item-hover: $br-magenta !default;
$nav-border: $g14-chromium !default;
$nav-toggle: $g20-white !default;
$nav-toggle-hover: $g20-white !default;
$nav-toggle-bg-hover: $cp-comet !default;
$nav-active: $m-magenta !default;
$nav-toggle-bg-hover: $br-magenta !default;
$nav-active: $br-magenta !default;
// Product Flags
$product-cloud: $b-dodger !default;
$product-oss: $p-comet !default;
$product-enterprise: $br-pulsar !default;
// Article Content
$article-bg: $g20-white !default;
$article-heading: $cp-marguerite !default;
$article-heading-alt: $g7-graphite !default;
$article-text: $g8-storm !default;
$article-bold: $g8-storm !default;
$article-link: $b-dodger !default;
$article-link-hover: $cp-purple !default;
$article-shadow: #c8cdd0 !default;
$article-heading: $br-pulsar !default;
$article-heading-alt: $g5-pepper !default;
$article-text: $g6-smoke !default;
$article-bold: $g6-smoke !default;
$article-link: $b-pool !default;
$article-link-hover: $br-magenta !default;
$article-shadow: $g14-chromium !default;
$article-hr: $g15-platinum !default;
// Article Code
$article-code: $cp-marguerite !default;
$article-code-bg: $cp-titan !default;
$article-code-shadow: $g20-white !default;
$article-code-accent1: $cp-melrose !default;
$article-code-accent2: $b-dodger !default;
$article-code-accent3: #12A290 !default;
$article-code-accent4: $o-ruby !default;
$article-code-accent2: #0783e8 !default;
$article-code-accent3: #008859 !default;
$article-code-accent4: $r-ruby !default;
$article-code-accent5: #e24bbb !default;
$article-code-accent6: $b-dodger !default;
$article-code-accent7: #e90 !default;
$article-code-select: $b-pool !default;
$article-code-select: $b-dodger !default;
$article-code-link: $cp-marguerite !default;
$article-code-link-hover: $cp-marguerite !default;
$article-code-scrollbar: $cp-periwinkle !default;
// Article Tables
$article-table-header-left: $cp-marguerite !default;
$article-table-header-right: $b-laser !default;
$article-table-header: $grad-Miyazakisky !default;
$article-table-row-alt: #F6F7F8 !default;
$article-table-scrollbar: $g14-chromium !default;
@ -80,9 +82,9 @@ $article-table-scrollbar: $g14-chromium !default;
$article-note-base: $gr-rainforest !default;
$article-note-heading: $gr-emerald !default;
$article-note-text: $gr-emerald !default;
$article-note-link: $gr-emerald !default;
$article-note-link-hover: $cp-purple !default;
$article-note-table-header: $gr-viridian !default;
$article-note-link: $b-ocean !default;
$article-note-link-hover: $br-magenta !default;
$article-note-table-header: $grad-green-dark !default;
$article-note-table-row-alt: #d6f5e9 !default;
$article-note-table-scrollbar: #87DABE !default;
$article-note-shadow: #8CB7AB !default;
@ -91,18 +93,18 @@ $article-note-code-bg: #BDF3DA !default;
$article-note-code-accent1: #6abba0 !default;
$article-note-code-accent2: #0084d6 !default;
$article-note-code-accent3: #5d52d6 !default;
$article-note-code-accent4: $o-ruby !default;
$article-note-code-accent4: $r-ruby !default;
$article-note-code-accent5: #e24bbb !default;
$article-note-code-accent6: #0084d6 !default;
$article-note-code-accent7: #e90 !default;
$article-note-code-scrollbar: #87DABE !default;
$article-warn-base: $o-dreamsicle !default;
$article-warn-heading: $o-fire !default;
$article-warn-text: $o-curacao !default;
$article-warn-link: $o-curacao !default;
$article-warn-link-hover: $cp-purple !default;
$article-warn-table-header: $o-dreamsicle !default;
$article-warn-base: $r-dreamsicle !default;
$article-warn-heading: $r-fire !default;
$article-warn-text: $r-curacao !default;
$article-warn-link: $r-curacao !default;
$article-warn-link-hover: $br-pulsar !default;
$article-warn-table-header: $grad-red !default;
$article-warn-table-row-alt: #ffe6df !default;
$article-warn-table-scrollbar: #FFB1B1 !default;
$article-warn-shadow: #b98a7d !default;
@ -111,89 +113,85 @@ $article-warn-code-bg: #FFDDDC !default;
$article-warn-code-accent1: #fd99b8 !default;
$article-warn-code-accent2: #357ae8 !default;
$article-warn-code-accent3: #6c59cc !default;
$article-warn-code-accent4: $o-ruby !default;
$article-warn-code-accent4: $r-ruby !default;
$article-warn-code-accent5: #6a0a6f !default;
$article-warn-code-accent6: #357ae8 !default;
$article-warn-code-accent7: #e90 !default;
$article-warn-code-scrollbar: #FFB1B1 !default;
$article-cloud-base: $b-laser !default;
$article-cloud-heading: $b-eastern !default;
$article-cloud-text: $b-curious !default;
$article-cloud-link: $b-curious !default;
$article-cloud-link-hover: $cp-purple !default;
$article-cloud-table-header: $b-curious !default;
$article-cloud-table-row-alt: $b-hawkeye !default;
$article-cloud-table-scrollbar: $b-malibu !default;
$article-cloud-heading: $b-ocean !default;
$article-cloud-text: $b-ocean !default;
$article-cloud-link: $b-ocean !default;
$article-cloud-link-hover: $br-pulsar !default;
$article-cloud-table-header: $grad-blue !default;
$article-cloud-table-row-alt: $g20-white !default;
$article-cloud-table-scrollbar: $b-hydrogen !default;
$article-cloud-shadow: #6EB8E4 !default;
$article-cloud-code: $b-matisse !default;
$article-cloud-code-bg: $b-fleur !default;
$article-cloud-code: $b-ocean !default;
$article-cloud-code-bg: $b-neutrino !default;
$article-cloud-code-accent1: #3CAAE2 !default;
$article-cloud-code-accent2: $cp-blueviolet !default;
$article-cloud-code-accent2: $br-pulsar !default;
$article-cloud-code-accent3: #048E66 !default;
$article-cloud-code-accent4: $o-ruby !default;
$article-cloud-code-accent4: $r-ruby !default;
$article-cloud-code-accent5: #e24bbb !default;
$article-cloud-code-accent6: #0084d6 !default;
$article-cloud-code-accent7: #e90 !default;
$article-cloud-code-scrollbar: $b-malibu !default;
$article-cloud-code-scrollbar: $b-laser !default;
$article-enterprise-base: $cp-comet !default;
$article-enterprise-text: $cp-purple !default;
$article-enterprise-link: $cp-purple !default;
$article-enterprise-link-hover: $b-dodger !default;
$article-enterprise-base: $br-galaxy !default;
$article-enterprise-text: $cp-marguerite !default;
$article-enterprise-link: $cp-marguerite !default;
$article-enterprise-link-hover: $b-pool !default;
// Article Tabs for tabbed content
$article-tab-text: $g8-storm !default;
$article-tab-bg: $g18-cloud !default;
$article-tab-active-text: $g20-white !default;
$article-tab-active-bg: $b-pool !default;
$article-tab-code-text: $cp-munchkin !default;
$article-tab-code-bg: $g20-white !default;
$article-tab-code-text-hover: $g20-white !default;
$article-tab-code-bg-hover: $cp-comet !default;
$article-tab-code-active-text: $cp-marguerite !default;
$article-tab-code-text: $cp-marguerite !default;
// Article page buttons
$article-btn: $b-pool !default;
$article-btn-text: $g20-white !default;
$article-btn-hover: $b-dodger !default;
$article-btn-hover: $b-pool !default;
$article-btn-text-hover: $g20-white !default;
// Article UI nav icons
$article-nav-icon-bg: $g6-smoke !default;
$article-nav-acct-bg: $g5-pepper !default;
// Error Page Colors
$error-page-btn: $b-dodger !default;
$error-page-btn: $b-pool !default;
$error-page-btn-text: $g20-white !default;
$error-page-btn-hover: $b-pool !default;
$error-page-btn-hover-text: $g20-white !default;
// Landing Page colors
$landing-lg-gradient-left: $cp-jakarta !default;
$landing-lg-gradient-right: $wp-heart !default;
$landing-sm-bg: $wp-seance !default;
$landing-sm-bg-alt: $wp-jagger !default;
$landing-sm-bg-hover: $b-dodger !default;
$landing-artwork-gradient: $grad-GundamPilot !default;
$landing-artwork-color: rgba($p-shadow, .35) !default;
$landing-sm-bg: rgba($p-void, .4) !default;
$landing-sm-bg-hover: $b-pool !default;
$landing-btn-text: $g20-white !default;
$landing-btn-bg: $b-dodger !default;
$landing-btn-text-hover: $b-dodger !default;
$landing-btn-bg-hover: $g20-white !default;
$landing-artwork-color: rgba($g20-white, .15) !default;
$landing-btn-grad: $grad-blue !default;
$landing-btn-grad-hover: $grad-blue-light !default;
// Tooltip colors
$tooltip-color: $m-magenta !default;
$tooltip-color-alt: $wp-trance !default;
$tooltip-bg: $m-lavander !default;
$tooltip-color: $p-amethyst !default;
$tooltip-color-alt: $p-twilight !default;
$tooltip-bg: $p-amethyst !default;
$tooltip-text: $g20-white !default;
// SVG colors
$svg-table-header: $g15-platinum !default;
$svg-table-stroke: $g7-graphite !default;
$svg-table-row-alt1: $b-laser !default;
$svg-table-row-alt2: $cp-comet !default;
$svg-table-row-alt2: $br-galaxy !default;
$svg-table-code: $cp-marguerite !default;
$svg-table-code-bg: $cp-titan !default;
$svg-table-code-operator: $b-dodger !default;
$svg-table-code-operator: $b-pool !default;
$svg-table-code-string: #12A290 !default;
$svg-geo-s2-cell: $b-malibu !default;
$svg-geo-region: $cp-comet !default;
$svg-geo-point: $m-heliotrope !default;
$svg-geo-s2-cell: $b-hydrogen !default;
$svg-geo-region: $br-galaxy !default;
$svg-geo-point: $p-potassium !default;

239
assets/styles/tools/_color-palette.scss
View File

@ -1,120 +1,137 @@
// Influx Color Palette
// Greys (Dark to Light)
$g0-obsidian: #0F0E15;
$g1-raven: #1C1C21;
$g2-kevlar: #202028;
$g3-castle: #292933;
$g4-onyx: #2C2C38;
$g5-pepper: #383846;
$g6-smoke: #434453;
$g7-graphite: #545667;
$g8-storm: #676978;
$g9-mountain: #757888;
$g10-wolf: #8E91A1;
$g11-sidewalk: #999DAB;
$g12-forge: #A4A8B6;
$g13-mist: #BEC2CC;
$g14-chromium: #C6CAD3;
$g15-platinum: #D4D7DD;
$g16-pearl: #E7E8EB;
$g17-whisper: #EEEFF2;
$g18-cloud: #F2F2F5;
$g19-ghost: #FAFAFC;
$g20-white: #FFFFFF; // Brand color
// Brand Colors
$br-chartreuse: #D6F622;
$br-deeppurple: #13002D;
$br-magenta: #BF2FE5;
$br-galaxy: #9394FF;
$br-pulsar: #513CC6;
// Warm Purples - Magentas
$wp-jaguar: #1d0135;
$wp-telopea: #23043E;
$wp-violentdark: #2d0749;
$wp-violet: #32094E;
$wp-jagger: #420D5F;
$wp-jango: #521170;
$wp-seance: #611581;
$wp-trance: #801EA2;
$wp-heart: #A026C4;
$m-magenta: #BF2FE5; // Brand color
$m-lavander: #CA52E9;
$m-heliotrope: #D474EE;
$m-perfume: #DF97F2;
$m-pinkmist: #EABAF6;
$m-selago: #F4DCFB;
// Cool Purples
$cp-jakarta: #322368;
$cp-minsk: #423681;
$cp-victoria: #52499A;
$cp-blueviolet: #625CB3;
$cp-marguerite: #736ECD;
$cp-purple: #8381E6;
$cp-comet: #9394ff; // Brand color
$cp-melrose: #A5A6FF;
$cp-munchkin: #B7B8FF;
$cp-periwinkle: #C9CAFF;
$cp-coolfog: #DBDBFF;
$cp-titan: #EDEDFF;
// Neutral Purples
$np-deepnight: #13002d; // Brand color
$np-valhalla: #27153F;
$np-martinique: #3A2B50;
$np-wine: #4E4062;
$np-smokey: #625573;
$np-rum: #756A85;
$np-mobster: #898096;
$np-amethyst: #9D95A7;
$np-pearl: #B0AAB9;
$np-greysuit: #C4BFCA;
$np-mischka: #D8D4DC;
$np-athens: #EBEAED;
// Greys
$g0-obsidian: #0F0E15;
$g1-raven: #181820;
$g2-kevlar: #202028;
$g3-castle: #292933;
$g4-onyx: #31313D;
$g5-pepper: #383846;
$g6-smoke: #434453;
$g7-graphite: #545667;
$g8-storm: #676978;
$g9-mountain: #757888;
$g10-wolf: #8E91A1;
$g11-sidewalk: #999DAB;
$g12-forge: #A4A8B6;
$g13-mist: #BEC2CC;
$g14-chromium: #C6CAD3;
$g15-platinum: #D4D7DD;
$g16-pearl: #E7E8EB;
$g17-whisper: #EEEFF2;
$g18-cloud: #F6F6F8;
$g19-ghost: #FAFAFC;
$g20-white: #FFFFFF;
// Blues
$b-tiber: #0A3044;
$b-deepsea: #0E4562;
$b-chathams: #125A7F;
$b-matisse: #166F9D;
$b-eastern: #1A83BB;
$b-curious: #1E98D8;
$b-dodger: #2AA3FF;
$b-pool: #22ADF6; // Brand color
$b-laser: #47BBF8;
$b-malibu: #6CC8F9;
$b-horizon: #91D6FB;
$b-fleur: #B5E4FC;
$b-hawkeye: #DAF1FD;
$b-abyss: #120653;
$b-sapphire: #0B3A8D;
$b-ocean: #066FC5;
$b-dodger: #2AA3FF;
$b-pool: #00A3FF;
$b-laser: #00C9FF;
$b-hydrogen: #6BDFFF;
$b-neutrino: #BEF0FF;
$b-yeti: #F0FCFF;
// Chartreuses
$ch-olive: #3B440A;
$ch-saratoga: #55620E;
$ch-olivetone: #6F7F12;
$ch-trendy: #899D16;
$ch-citron: #A2BB1A;
$ch-keylime: #BCD81E;
$ch-chartreuse: #D6F622; // Brand color
$ch-canary: #E4F96C;
$ch-primrose: #F1FCB5;
// Purples
$p-shadow: #2B007E;
$p-void: #5C10A0;
$p-amethyst: #8E1FC3;
$p-star: #BE2EE4;
$p-comet: #CE58EB;
$p-potassium: #DD84F1;
$p-moonstone: #EBADF8;
$p-twilight: #FAD9FF;
// Greens
$gr-gypsy: #152B2D;
$gr-grass: #2B6058;
$gr-emerald: #108174;
$gr-viridian: #32B08C;
$gr-canopy: #20B76F;
$gr-rainforest: #4ED8A0;
$gr-honeydew: #7CE490;
$gr-krypton: #A5F3B4;
$gr-wasabi: #C6FFD0;
$gr-forestfog: #CFE6E1;
$gr-mint: #F2FFF4;
$gr-gypsy: #003E34;
$gr-emerald: #006F49;
$gr-viridian: #009F5F;
$gr-rainforest: #34BB55;
$gr-honeydew: #67D74E;
$gr-krypton: #9BF445;
$gr-wasabi: #C6F98E;
$gr-mint: #F3FFD6;
// Oranges
$o-basalt: #2F1F29;
$o-ember: #6F3943;
$o-ruby: #BF3D5E;
$o-fire: #DC4E58;
$o-curacao: #F95F53;
$o-dreamsicle: #FF8564;
$o-tungsten: #FFB6A0;
$o-marmelade: #FFDCCF;
$o-orangecream: #EADAD8;
$o-flan: #FFF7F4;
// Yellows
$y-oak: #3F241F;
$y-topaz: #E85B1C;
$y-tiger: #F48D38;
$y-pineapple: #FFB94A;
$y-thunder: #FFD255;
$y-sulfur: #FFE480;
$y-daisy: #FFF6B8;
$y-banana: #FFFDDE;
// Reds
$r-basalt: #2F1F29;
$r-ruby: #BF3D5E;
$r-fire: #DC4E58;
$r-curacao: #F95F53;
$r-dreamsicle: #FF8564;
$r-tungsten: #FFB6A0;
$r-marmelade: #FFDCCF;
$r-flan: #FFF7F4;
// Code (Light theme)
$cp-marguerite: #736ECD;
$cp-melrose: #A5A6FF;
$cp-munchkin: #B7B8FF;
$cp-periwinkle: #C9CAFF;
$cp-titan: #EDEDFF;
/////////////////////////////////// Gradients //////////////////////////////////
// Brand Gradients
$grad-WarpSpeed: $br-deeppurple, $p-void;
$grad-PowerStone: $p-void, $br-magenta;
$grad-MilkyWay: $br-magenta, $br-galaxy;
$grad-LazyAfternoon: $b-pool, $br-galaxy;
$grad-NineteenEightyFour: $b-pool, $br-magenta;
$grad-RadioactiveWarning: $b-pool, $br-chartreuse;
$grad-LostGalaxy: $br-deeppurple, $br-pulsar;
$grad-GrapeSoda: $br-deeppurple, $p-amethyst;
$grad-LavenderLatte: $br-deeppurple, $p-star;
$grad-OminousFog: $br-pulsar, $br-galaxy;
// Single Hue Gradient
$grad-grey-light: $g13-mist, $g18-cloud;
$grad-grey: $g10-wolf, $g13-mist;
$grad-grey-dark: $g3-castle, $g6-smoke;
$grad-blue-light: $b-pool, $b-hydrogen;
$grad-blue: $b-ocean, $b-pool;
$grad-blue-dark: $b-sapphire, $b-ocean;
$grad-purple-light: $p-comet, $p-moonstone;
$grad-purple: $p-star, $p-comet;
$grad-purple-dark: $p-void, $p-amethyst;
$grad-green-light: $gr-honeydew, $gr-krypton;
$grad-green: $gr-rainforest, $gr-honeydew;
$grad-green-dark: $gr-emerald, $gr-viridian;
$grad-yellow-light: $y-thunder, $y-sulfur;
$grad-yellow: $y-pineapple, $y-thunder;
$grad-yellow-dark: $y-topaz, $y-tiger;
$grad-red-light: $r-dreamsicle, $r-tungsten;
$grad-red: $r-curacao, $r-dreamsicle;
$grad-red-dark: $r-ruby, $r-fire;
// Multi-Hue Gradients
$grad-GundamPilot: $p-amethyst, $b-ocean;
$grad-Miyazakisky: $p-star, $b-pool;
$grad-PastelGothic: $p-comet, $b-laser;
$grad-GarageBand: $b-pool, $gr-rainforest;
$grad-LowDifficulty: $b-pool, $gr-honeydew;
$grad-DesertFestival: $r-curacao, $p-star;

27
assets/styles/tools/_icomoon.scss
View File

@ -1,12 +1,13 @@
@font-face {
font-family: 'icomoon';
src: url('fonts/icomoon.eot?9r9zke');
src: url('fonts/icomoon.eot?9r9zke#iefix') format('embedded-opentype'),
url('fonts/icomoon.ttf?9r9zke') format('truetype'),
url('fonts/icomoon.woff?9r9zke') format('woff'),
url('fonts/icomoon.svg?9r9zke#icomoon') format('svg');
src: url('fonts/icomoon.eot?rgf1km');
src: url('fonts/icomoon.eot?rgf1km#iefix') format('embedded-opentype'),
url('fonts/icomoon.ttf?rgf1km') format('truetype'),
url('fonts/icomoon.woff?rgf1km') format('woff'),
url('fonts/icomoon.svg?rgf1km#icomoon') format('svg');
font-weight: normal;
font-style: normal;
font-display: block;
}
[class^="icon-"], [class*=" icon-"] {
@ -30,11 +31,8 @@
.icon-ui-wrench-nav:before {
content: "\e93d";
}
.icon-ui-eye-closed:before {
content: "\e956";
}
.icon-ui-eye-open:before {
content: "\e957";
.icon-ui-user:before {
content: "\e93e";
}
.icon-ui-chat:before {
content: "\e93a";
@ -42,12 +40,21 @@
.icon-ui-bell:before {
content: "\e93b";
}
.icon-ui-users-trio:before {
content: "\e940";
}
.icon-ui-cloud:before {
content: "\e93f";
}
.icon-ui-nav-chat:before {
content: "\e941";
}
.icon-ui-eye-closed:before {
content: "\e956";
}
.icon-ui-eye-open:before {
content: "\e957";
}
.icon-ui-add-cell:before {
content: "\e91f";
}

5
assets/styles/tools/mixins.scss
View File

@ -6,6 +6,7 @@
}
&::-webkit-scrollbar-track {
background-color: $bg-color;
border-radius: 0 0 $radius $radius;
}
&::-webkit-scrollbar-thumb {
background-color: $thumb-color;
@ -13,3 +14,7 @@
border-radius: 6px;
}
}
@mixin gradient($colors, $deg: 45deg) {
background: linear-gradient($deg, $colors);
}

8
content/v2.0/cloud/account-management/_index.md → content/v2.0/account-management/_index.md
View File

@ -3,10 +3,14 @@ title: Manage your InfluxDB Cloud 2.0 Account
description: >
View and manage information related to your InfluxDB Cloud 2.0 account such as
pricing plans, data usage, account cancelation, etc.
weight: 4
weight: 10
products: [cloud]
aliases:
- /v2.0/cloud/account-management/
menu:
v2_0_cloud:
v2_0:
name: Account management
products: [cloud]
---
{{< children >}}

77
content/v2.0/cloud/account-management/billing.md → content/v2.0/account-management/billing.md
View File

@ -1,27 +1,51 @@
---
title: Add payment method and view billing
list_title: Add payment and view billing
title: Manage InfluxDB Cloud billing
list_title: Manage billing
description: >
Add your InfluxDB Cloud payment method and view billing information.
Upgrade to the InfluxDB Cloud Usage-Based Plan and manage your billing information.
aliases:
- /v2.0/cloud/account-management/billing
- /v2.0/cloud/account-management/upgrade-to-payg/
- /v2.0/cloud/account-management/upgrade-to-usage-based-plan/
weight: 103
menu:
v2_0_cloud:
v2_0:
parent: Account management
name: Add payment and view billing
name: Manage billing
products: [cloud]
---
## Upgrade to Usage-Based Plan
1. Click **Upgrade Now** in the top right corner of the {{< cloud-name "short" >}} user interface (UI).
2. Review the terms and pricing associated with the Usage-Based Plan.
3. Click **Sounds Good To Me**.
4. Enter your contact information.
Traditionally this would be "shipping" information, but InfluxData does not ship anything.
This information should be the primary location where the service is consumed.
All service updates, security notifications and other important information are
sent using the information you provide.
The address is used to determine any applicable sales tax.
5. Enter your payment information and click **Add Card**.
6. Review the plan details, contact information, and credit card information.
7. Click **Confirm & Order**.
Add your payment method and view billing information in the {{< cloud-name "short" >}} user interface (UI).
## Access billing details
1. Click the **user avatar** in the top right corner of the {{< cloud-name "short" >}}
UI and select **Billing**.
1. In the {{< cloud-name "short" >}} UI, select the **user avatar** in the left
navigation menu, and select **Billing**.
{{< nav-icon "account" >}}
2. Do one of the following:
- If you subscribed to an InfluxDB Cloud 2.0 plan through **AWS Marketplace**,
click the **AWS** link to access your billing and subscription information.
- If you subscribed to an InfluxDB Cloud 2.0 plan through **AWS Marketplace**
or **GCP Marketplace**, click the **AWS** or **GCP** link to access your
billing and subscription information.
- If you subscribed to an InfluxDB Cloud 2.0 plan through **InfluxData**, complete the following procedures as needed:
- [Add or update your {{< cloud-name >}} payment method](#add-or-update-your-influxdb-cloud-2-0-payment-method)
- [Add or update your payment method](#add-or-update-your-payment-method)
- [Add or update your contact information](#add-or-update-your-contact-information)
- [Send notifications when usage exceeds an amount](#send-notifications-when-usage-exceeds-an-amount)
@ -33,9 +57,9 @@ Add your payment method and view billing information in the {{< cloud-name "shor
- [Billing cycle](#billing-cycle)
- [Declined or late payments](#declined-or-late-payments)
### Add or update your InfluxDB Cloud 2.0 payment method
### Add or update your payment method
1. On the Billing page:
1. On the **Billing page**:
- To update, click the **Change Payment** button on the Billing page.
- In the **Payment Method** section:
- Enter your cardholder name and number
@ -47,39 +71,40 @@ Add your payment method and view billing information in the {{< cloud-name "shor
### Add or update your contact information
1. On the Billing page:
1. On the **Billing page**:
- To update, click the **Edit Information** button.
- In the **Contact Information** section, enter your name, company, and address.
2. Click **Save Contact Info**.
### Send notifications when usage exceeds an amount
1. On the Billing page, click **Notification Settings**.
1. On the **Billing page**, click **Notification Settings**.
2. Select the **Send email notification** toggle, and then enter the email address to notify.
3. Enter the dollar amount to trigger a notification email. By default, an email is triggered when the amount exceeds $10. (Whole dollar amounts only. For example, $10.50 is not a supported amount.)
### View Usage-based Plan information
- On the Billing page, view your billing information, including:
- Account balance
- Last billing update (updated hourly)
- Past invoices
- Payment method
- Contact information
- Notification settings
On the **Billing page**, view your billing information, including:
- Account balance
- Last billing update (updated hourly)
- Past invoices
- Payment method
- Contact information
- Notification settings
### View Free Plan information
- On the Billing page, view the total limits available for the Free Plan.
On the **Billing page**, view the total limits available for the Free Plan.
### Exceeded rate limits
## Exceeded rate limits
If you exceed your plan's [rate limits](/v2.0/cloud/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review.
If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review.
All rate-limited requests are rejected; including both read and write requests.
_Rate-limited requests are **not** queued._
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/)._
_To remove rate limits, [upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan)._
#### Rate-limited HTTP response code
@ -90,7 +115,7 @@ HTTP 429 “Too Many Requests”
Retry-After: xxx (seconds to wait before retrying the request)
```
### Billing cycle
## Billing cycle
Billing occurs on the first day of the month for the previous month. For example, if you start the Usage-based Plan on September 15, you're billed on October 1 for your usage from September 15-30.

9
content/v2.0/cloud/account-management/data-usage.md → content/v2.0/account-management/data-usage.md
View File

@ -4,10 +4,13 @@ list_title: View data usage
description: >
View your InfluxDB Cloud 2.0 data usage and rate limit notifications.
weight: 103
aliases:
- /v2.0/cloud/account-management/data-usage
menu:
v2_0_cloud:
v2_0:
parent: Account management
name: View data usage
products: [cloud]
---
To view your {{< cloud-name >}} data usage, click the **user avatar** in the top
@ -29,14 +32,14 @@ Find data usage information for the time frame specified in the drop-down at the
## Exceeded rate limits
If you exceed your plan's [rate limits](/v2.0/cloud/pricing-plans/), {{< cloud-name >}}
If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}}
will provide a notification in the {{< cloud-name "short" >}} user interface (UI)
and add a rate limit event to your **Usage** page for review.
All rate-limited requests are rejected; including both read and write requests.
_Rate-limited requests are **not** queued._
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/)._
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
### Rate-limited HTTP response code
When a request exceeds your plan's rate limit, the InfluxDB API returns the following response:

7
content/v2.0/cloud/account-management/offboarding.md → content/v2.0/account-management/offboarding.md
View File

@ -4,10 +4,13 @@ description: >
Cancel your InfluxDB Cloud 2.0 account at any time by stopping all read and write
requests, backing up data, and contacting InfluxData Support.
weight: 104
aliases:
- /v2.0/cloud/account-management/offboarding
menu:
v2_0_cloud:
v2_0:
parent: Account management
name: Cancel InfluxDB Cloud
products: [cloud]
---
To cancel your {{< cloud-name >}} subscription, complete the following steps:
@ -58,5 +61,5 @@ To request a backup of data in your {{< cloud-name "short" >}} instance, contact
2. Do one of the following:
- If you subscribed to an InfluxDB Cloud 2.0 **Usage-Based Plan** through **AWS Marketplace**, click the **AWS** link, click **Unsubscribe**, and then click **Yes, cancel subscription**.
- If you subscribed to an InfluxDB Cloud 2.0 **Usage-Based Plan** through **GCP Marketplace**, click the **GCP** link, click **Unsubscribe**, and then click **Yes, cancel subscription**.
- If you subscribed to an InfluxDB Cloud 2.0 **Usage-Based Plan** through **InfluxData**, click **Cancel Service**. Select **I understand and agree to these conditions**, and then click **I understand, Cancel Service.** Click **Confirm and Cancel Service**. Your payment method is charged your final balance immediately upon cancellation of service.

7
content/v2.0/cloud/pricing-calculator.md → content/v2.0/account-management/pricing-calculator.md
View File

@ -5,8 +5,9 @@ description: >
plugins, metrics, and writes for the Usage-based Plan.
weight: 2
menu:
v2_0_cloud:
v2_0:
name: Pricing calculator
products: [cloud]
draft: true
---
@ -36,7 +37,7 @@ Guidelines used to estimate costs for default configurations:
- Free Plan. Click the **user avatar** in the top right corner of your
{{< cloud-name "short" >}} user interface (UI) and select **Billing**.
Then click the **Pricing Calculator** link at the bottom of the page.
Then click the **Pricing Calculator** link at the bottom of the page.
- Usage-based Plan. Open the pricing calculator [here](https://cloud2.influxdata.com/pricing).
3. Choose your region.
4. Select your configuration:
@ -45,4 +46,4 @@ Guidelines used to estimate costs for default configurations:
- **Professional**. For teams monitoring multiple disparate systems or use cases.
- **Enterprise**. For teams monitoring multiple domains and use cases accessing a variety of dashboards.
5. Adjust the default configuration values to match your number of devices, plugins, metrics, and so on. The **Projected Usage** costs are automatically updated as you adjust your configuration.
6. Click **Get started with InfluxDB Cloud** [to get started](/v2.0/cloud/get-started/).
6. Click **Get started with InfluxDB Cloud** [to get started](/v2.0/get-started/).

13
content/v2.0/cloud/pricing-plans.md → content/v2.0/account-management/pricing-plans.md
View File

@ -5,10 +5,13 @@ description: >
Free Plan and the Usage-based Plan.
aliases:
- /v2.0/cloud/rate-limits/
weight: 2
- /v2.0/cloud/pricing-plans/
weight: 102
menu:
v2_0_cloud:
v2_0:
parent: Account management
name: Pricing plans
products: [cloud]
---
InfluxDB Cloud 2.0 offers two pricing plans:
@ -16,7 +19,7 @@ InfluxDB Cloud 2.0 offers two pricing plans:
- [Free Plan](#free-plan)
- [Usage-based Plan](#usage-based-plan)
<!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/v2.0/cloud/pricing-calculator/). -->
<!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/v2.0/account-management/pricing-calculator/). -->
## Free Plan
@ -41,11 +44,11 @@ Data retention is determined by the time at which data is written to InfluxDB; n
- Unlimited Slack notification endpoints
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/)._
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
## Usage-based Plan
The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/cloud/account-management/data-usage/).
The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/account-management/data-usage/).
#### Usage-based Plan rate limits

4
content/v2.0/backup-restore/_index.md
View File

@ -8,8 +8,8 @@ v2.0/tags: [backup, restore]
menu:
v2_0:
name: Back up & restore data
weight: 10
#draft: true
weight: 9
products: [oss]
---
InfluxDB provides tools to back up and restore data and metadata stored in InfluxDB.

6
content/v2.0/backup-restore/backup.md
View File

@ -10,7 +10,7 @@ weight: 101
related:
- /v2.0/backup-restore/restore/
- /v2.0/reference/cli/influx/backup/
#draft: true
products: [oss]
---
Use the [`influx backup` command](/v2.0/reference/cli/influx/backup/) to back up
@ -24,9 +24,9 @@ Root tokens created prior to **v2.0.0-beta.2** do not have the necessary permiss
To succesfully use the backup tool, set up a new InfluxDB instance using **v2.0.0-beta.2+**.
{{% /warn %}}
{{% cloud-msg %}}
{{% cloud %}}
The `influx backup` command **cannot** back up data stored in **{{< cloud-name "short" >}}**.
{{% /cloud-msg %}}
{{% /cloud %}}
The `influx backup` command requires:

6
content/v2.0/backup-restore/restore.md
View File

@ -11,15 +11,15 @@ v2.0/tags: [restore]
related:
- /v2.0/backup-restore/backup/
- /v2.0/reference/cli/influxd/restore/
#draft: true
products: [oss]
---
Use the `influxd restore` command to restore backup data and metadata from InfluxDB.
You must stop InfluxDB before restoring data.
{{% cloud-msg %}}
{{% cloud %}}
The `influxd restore` command only restores data to InfluxDB OSS, **not {{< cloud-name "short" >}}**.
{{% /cloud-msg %}}
{{% /cloud %}}
When restoring data from a backup file set, InfluxDB temporarily moves existing
data and metadata while the restore process runs.

27
content/v2.0/cloud/account-management/upgrade-to-usage-based-plan.md
View File

@ -1,27 +0,0 @@
---
title: Upgrade to a Usage-Based Plan
description: >
Upgrade to a Usage-Based Plan to remove rate limits from your InfluxDB Cloud 2.0 account.
aliases:
- /v2.0/cloud/account-management/upgrade-to-payg/
weight: 102
menu:
v2_0_cloud:
parent: Account management
name: Upgrade to Usage-Based Plan
---
Upgrade to a Usage-Based Plan to remove rate limits from your InfluxDB Cloud 2.0 account.
1. Click **Upgrade** in the top right corner of the {{< cloud-name "short" >}} user interface (UI).
2. Review the terms and pricing associated with the Usage-Based Plan.
3. Click **Sounds Good To Me**.
4. Enter your contact information.
Traditionally this would be "shipping" information, but InfluxData does not ship anything.
This information should be the primary location where the service is consumed.
All service updates, security notifications and other important information are
sent using the information you provide.
The address is used to determine any applicable sales tax.
5. Enter your payment information and click **Add Card**.
6. Review the plan details, contact information, and credit card information.
7. Click **Confirm & Order**.

142
content/v2.0/cloud/get-started.md
View File

@ -1,142 +0,0 @@
---
title: Get started with InfluxDB Cloud 2.0
description: >
Sign up now, sign in, and get started exploring and using the InfluxDB Cloud 2.0 time series platform.
weight: 1
menu:
v2_0_cloud:
name: Get started with InfluxDB Cloud
---
{{< cloud-name >}} is a fully managed, hosted, multi-tenanted version of the
InfluxDB 2.0 time series data platform.
The core of {{< cloud-name "short" >}} is built on the foundation of the open source
version of InfluxDB 2.0, which is much more than a database.
It is a time series data platform that collects, stores, processes and visualizes metrics and events.
_See the differences between {{< cloud-name "short">}} and InfluxDB OSS
[below](#differences-between-influxdb-cloud-and-influxdb-oss)._
## Start for free
Start using {{< cloud-name >}} at no cost with the [Free Plan](/v2.0/cloud/pricing-plans/#free-plan).
Use it as much and as long as you like within the plan's rate-limits.
Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably.
## Sign up
1. Choose one of the following:
- To subscribe to an InfluxDB Cloud 2.0 **Free Plan** through InfluxData, go to [InfluxDB Cloud 2.0]({{< cloud-link >}}), enter your credentials, and then click **Start your Free Plan now**. When you're ready to grow, [upgrade to the Usage-Based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/).
- To subscribe to an InfluxDB Cloud **Usage-Based** plan and pay through your AWS account, sign in to AWS, navigate to the [InfluxDB Cloud product on AWS Marketplace](https://aws.amazon.com/marketplace/pp/B08234JZPS), and follow the prompts to subscribe. After you click **Set Up Your Account**, enter your credentials, and then click **Start Now**. All usage charges will be paid through the subscribed AWS account.
{{%note%}} **Note:** Currently, we do **not support** using an existing InfluxDB Cloud 2.0 account to sign up for an InfluxDB Cloud 2.0 plan through AWS Marketplace.
{{%/note%}}
2. InfluxDB Cloud requires email verification to complete the sign up process.
Verify your email address by opening the email sent to the address you provided and clicking **Verify Your Email**.
3. (If you subscribed through InfluxData) Choose your cloud provider.
4. Select a provider and region for your {{< cloud-name >}} instance. The following are available:
- **Amazon Web Services (AWS)**
- **US West (Oregon)**
- **EU Frankfurt**
- **Google Cloud Platform (GCP)**
- **Iowa**
_To suggest regions to add, click **Let us know** under Regions._
5. (If you subscribed through InfluxData) Review the terms of the agreement, and then select **I have viewed and agree to InfluxDB Cloud 2.0 Services Subscription Agreement and InfluxData Global Data Processing Agreement**.
For details on the agreements, see the [InfluxDB Cloud 2.0: Services Subscription Agreement](https://www.influxdata.com/legal/terms-of-use/) and the [InfluxData Global Data Processing Agreement](https://www.influxdata.com/legal/influxdata-global-data-processing-agreement/).
6. Click **Finish**. {{< cloud-name >}} opens with a default organization and bucket (both created from your email address).
_To update organization and bucket names, see [Update an organization](/v2.0/organizations/update-org/)
and [Update a bucket](/v2.0/organizations/buckets/update-bucket/#update-a-bucket-s-name-in-the-influxdb-ui)._
{{% cloud-msg %}}
All InfluxDB 2.0 documentation applies to {{< cloud-name "short" >}} unless otherwise specified.
References to the InfluxDB user interface (UI) or localhost:9999 refer to your
{{< cloud-name >}} UI.
{{% /cloud-msg %}}
## Sign in
Sign in to [InfluxDB Cloud 2.0](https://cloud2.influxdata.com) using your email address and password.
<a class="btn" href="https://cloud2.influxdata.com">Sign in to InfluxDB Cloud 2.0 now</a>
## Collect and write data
Collect and write data to InfluxDB using the Telegraf plugins, the InfluxDB v2 API, the `influx`
command line interface (CLI), the InfluxDB UI (the user interface for InfluxDB 2.0), or the InfluxDB v2 API client libraries.
### Use Telegraf
Use Telegraf to quickly write data to {{< cloud-name >}}.
Create new Telegraf configurations automatically in the InfluxDB UI, or manually update an
existing Telegraf configuration to send data to your {{< cloud-name "short" >}} instance.
For details, see [Automatically configure Telegraf](/v2.0/write-data/use-telegraf/auto-config/#create-a-telegraf-configuration)
and [Manually update Telegraf configurations](/v2.0/write-data/use-telegraf/manual-config/).
### API, CLI, and client libraries
For information about using the InfluxDB v2 API, `influx` CLI, and client libraries to write data,
see [Write data to InfluxDB](/v2.0/write-data/).
{{% note %}}
#### InfluxDB Cloud instance endpoint
When using Telegraf, the InfluxDB v2 API, the `influx` CLI, or the client libraries
to interact with your {{< cloud-name "short" >}}, they each require the URL of your
InfluxDB Cloud instance.
See [InfluxDB Cloud URLs](/v2.0/cloud/urls/) for information about which URL to use
and where to find it in your InfluxDB Cloud UI.
{{% /note %}}
## Query and visualize data
Once you've set up {{< cloud-name "short" >}} to collect data, you can do the following:
- Query data using Flux, the UI, and the `influx` command line interface.
See [Query data](/v2.0/query-data/).
- Build custom dashboards to visualize your data.
See [Visualize data](/v2.0/visualize-data/).
## Process data
Use InfluxDB tasks to process and downsample data. See [Process data](/v2.0/process-data/).
## View data usage
Once you're up and running with {{< cloud-name "short" >}}, [monitor your data usage in
your {{< cloud-name "short" >}} UI](/v2.0/cloud/account-management/data-usage/).
## Differences between InfluxDB Cloud and InfluxDB OSS
{{< cloud-name >}} is API-compatible and functionally compatible with InfluxDB OSS 2.0.
The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud 2.0 are:
- [InfluxDB scrapers](/v2.0/write-data/scrape-data/) that collect data from specified
targets are not available in {{< cloud-name "short" >}}.
- {{< cloud-name "short" >}} instances are currently limited to a single organization with a single user.
- Retrieving data from a file based CSV source using the `file` parameter of the
[`csv.from()`](/v2.0/reference/flux/functions/csv/from) function is not supported;
however you can use raw CSV data with the `csv` parameter.
### New features in InfluxDB Cloud 2.0
- **Free Plan (rate-limited)**: Skip downloading and installing InfluxDB 2.0 and
jump right in to exploring InfluxDB 2.0 technology.
The Free Plan is designed for getting started with InfluxDB and for small hobby projects.
- **Flux support**: [Flux](/v2.0/query-data/get-started/) is a standalone data
scripting and query language that increases productivity and code reuse.
It is the primary language for working with data within InfluxDB 2.0.
Flux can be used with other data sources as well.
This allows users to work with data where it resides.
- **Unified API**: Everything in InfluxDB (ingest, query, storage, and visualization)
is now accessible using a unified [InfluxDB v2 API](/v2.0/reference/api/) that
enables seamless movement between open source and cloud.
- **Integrated visualization and dashboards**: Based on the pioneering Chronograf project,
the new user interface (InfluxDB UI) offers quick and effortless onboarding,
richer user experiences, and significantly quicker results.
- **Usage-based pricing**: The [The Usage-based Plan](/v2.0/cloud/pricing-plans/#usage-based-plan)
offers more flexibility and ensures that you only pay for what you use. <!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/v2.0/cloud/pricing-calculator/). -->

41
content/v2.0/cloud/urls.md
View File

@ -1,41 +0,0 @@
---
title: InfluxDB Cloud 2.0 URLs
description: >
InfluxDB Cloud 2.0 is available on multiple cloud providers in multiple regions,
each with with a unique URL and API endpoint.
weight: 3
menu:
v2_0_cloud:
name: InfluxDB Cloud URLs
---
InfluxDB Cloud 2.0 is available on multiple cloud providers in multiple regions.
Each region has a unique InfluxDB Cloud URL and API endpoint.
Use the URLs below to interact with your InfluxDB Cloud instances with the
[InfluxDB API](/v2.0/reference/api/), [InfluxDB client libraries](/v2.0/reference/api/client-libraries/),
[`influx` CLI](/v2.0/reference/cli/influx/), or [Telegraf](/v2.0/write-data/use-telegraf/).
## Amazon Web Services (AWS)
| Region | URL |
|:------ |:--- |
| US West (Oregon) | https://us-west-2-1.aws.cloud2.influxdata.com |
| EU Frankfurt | https://eu-central-1-1.aws.cloud2.influxdata.com |
## Google Cloud Platform (GCP)
| Region | URL |
|:------ |:--- |
| US Central (Iowa) | https://us-central1-1.gcp.cloud2.influxdata.com/ |
---
### View your Cloud URL in the InfluxDB Cloud UI
For the URL of your specific InfluxDB Cloud instance:
1. Click the **Load Data** icon in the left navigation of your InfluxDB Cloud user interface (UI).
{{< nav-icon "load-data" >}}
2. Go to **Client Libraries**.
3. The URL of your InfluxDB instance is displayed near the top of the page.

118
content/v2.0/example.md
View File

@ -5,21 +5,27 @@ menu:
v2_0:
name: Example post
weight: 1
enterprise_all: true
#enterprise_some: true
#cloud_all: true
cloud_some: true
draft: true
"v2.0/tags": [influxdb, functions]
related:
- /v2.0/write-data/
- /v2.0/write-data/quick-start
- https://influxdata.com, This is an external link
products: [cloud, oss, enterprise]
---
This is a paragraph. Lorem ipsum dolor ({{< icon "trash" >}}) sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo.
{{< nav-icon "dashboards" >}}
This is **bold** text. This is _italic_ text. This is _**bold and italic**_.
{{< nav-icon "account" >}}
{{< nav-icon "data" >}}
{{< nav-icon "explore" >}}
{{< nav-icon "org" >}}
{{< nav-icon "boards" >}}
{{< nav-icon "tasks" >}}
{{< nav-icon "alerts" >}}
{{< nav-icon "settings" >}}
## h2 This is a header2
This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo.
@ -185,13 +191,13 @@ avg_cpu
{{% enterprise %}}
###### This is a table
| Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
| Row 5.1 | `Row 5.2` | Row 5.3 | Row 5.4 |
| Column 1 | Column 2 | Column 3 | Column 4 | Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- | -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 | Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 | Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 | Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 | Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
| Row 5.1 | `Row 5.2` | Row 5.3 | Row 5.4 | Row 5.1 | `Row 5.2` | Row 5.3 | Row 5.4 |
###### This is a table with lots of stuff
| Column 1 | Column 2 | Column 3 | Column 4 |
@ -303,20 +309,36 @@ This is **bold**. This is _italic_.
Nunc rutrum, metus id scelerisque euismod, erat ante, ac congue enim risus id est.
Etiam tristique nisi et tristique auctor.
{{< code-tabs-wrapper >}}
{{% code-tabs %}}
[tab1](#)
[tab2](#)
{{% /code-tabs %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"example-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu" and r._field == "someReallyLongFieldName")
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"my-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu")
```
{{% /code-tab-content %}}
{{< /code-tabs-wrapper >}}
###### This is a table in a blockquote
| Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
| Column 1 | Column 2 | Column 3 | Column 4 | Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- | -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 | Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 | Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 | Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 | Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
{{% /note %}}
@ -416,24 +438,40 @@ This is **bold**. This is _italic_.
Nunc rutrum, metus id scelerisque euismod, erat ante, ac congue enim risus id est.
Etiam tristique nisi et tristique auctor.
{{< code-tabs-wrapper >}}
{{% code-tabs %}}
[tab1](#)
[tab2](#)
{{% /code-tabs %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"example-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu" and r._field == "someReallyLongFieldName")
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"my-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu")
```
{{% /code-tab-content %}}
{{< /code-tabs-wrapper >}}
###### This is a table in a blockquote
| Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
| Column 1 | Column 2 | Column 3 | Column 4 | Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- | -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 | Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 | Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 | Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 | Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
{{% /warn %}}
{{% cloud-msg %}}
{{% cloud %}}
This is a multiple paragraph blockquote with internal elements.
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
@ -524,22 +562,38 @@ This is **bold**. This is _italic_.
Nunc rutrum, metus id scelerisque euismod, erat ante, ac congue enim risus id est.
Etiam tristique nisi et tristique auctor.
{{< code-tabs-wrapper >}}
{{% code-tabs %}}
[tab1](#)
[tab2](#)
{{% /code-tabs %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"example-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu" and r._field == "someReallyLongFieldName")
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
```js
// This is a code block inside of a blockquote
cpu = from(bucket:"my-bucket")
|> range(start:-30m)
|> filter(fn:(r) => r._measurement == "cpu")
```
{{% /code-tab-content %}}
{{< /code-tabs-wrapper >}}
###### This is a table in a blockquote
| Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
| Column 1 | Column 2 | Column 3 | Column 4 | Column 1 | Column 2 | Column 3 | Column 4 |
| -------- | -------- | -------- | -------- | -------- | -------- | -------- | -------- |
| Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 | Row 1.1 | `Row 1.2` | Row 1.3 | Row 1.4 |
| Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 | Row 2.1 | `Row 2.2` | Row 2.3 | Row 2.4 |
| Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 | Row 3.1 | `Row 3.2` | Row 3.3 | Row 3.4 |
| Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 | Row 4.1 | `Row 4.2` | Row 4.3 | Row 4.4 |
{{% /cloud-msg %}}
{{% /cloud %}}
{{< tabs-wrapper >}}
{{% tabs %}}

211
content/v2.0/get-started.md
View File

@ -1,20 +1,108 @@
---
title: Get started with InfluxDB OSS
title: Get started with InfluxDB
description: Download, install, and setup InfluxDB, creating a default organization, user, and bucket.
menu:
v2_0:
name: Get started
weight: 1
v2.0/tags: [get-started, install]
aliases:
- /v2.0/cloud/get-started
---
The InfluxDB 2.0 time series platform is purpose-built to collect, store,
process and visualize metrics and events.
Start with **InfluxDB Cloud 2.0**, a fully managed and hosted version of InfluxDB 2.0,
or **InfluxDB OSS 2.0 _(beta)_**, the open source
version of InfluxDB 2.0.
<div class="get-started-btns">
<a class="btn" href="#start-with-influxdb-cloud-2-0">Start with InfluxDB Cloud</a>
<a class="btn" href="#start-with-influxdb-oss">Start with InfluxDB OSS <span class="oss"></span></a>
</div>
_See [Differences between InfluxDB Cloud and InfluxDB OSS](#differences-between-influxdb-cloud-and-influxdb-oss)._
---
## Start with InfluxDB Cloud 2.0
### Start for free
Start using {{< cloud-name >}} at no cost with the [Free Plan](/v2.0/account-management/pricing-plans/#free-plan).
Use it as much and as long as you like within the plan's rate-limits.
Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably.
### Sign up
1. Choose one of the following:
- **Subscribe through InfluxData**
To subscribe to an InfluxDB Cloud 2.0 **Free Plan** through InfluxData,
go to [InfluxDB Cloud 2.0]({{< cloud-link >}}), enter your credentials,
and then click **Start your Free Plan now**.
When you're ready to grow, [upgrade to the Usage-Based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan).
- **Subscribe through a cloud provider**
To subscribe to an InfluxDB Cloud **Usage-Based** plan and pay through your
**Amazon Web Services (AWS)** or **Google Cloud Platform (GCP)** account:
- **AWS**
Sign in to AWS, navigate to the [InfluxDB Cloud product on AWS Marketplace](https://aws.amazon.com/marketplace/pp/B08234JZPS),
and follow the prompts to subscribe. After you click **Set Up Your Account**,
enter your credentials, and then click **Start Now**.
All usage charges will be paid through the subscribed AWS account.
- **GCP**
Sign in to GCP, navigate to the [InfluxDB Cloud product on GCP Marketplace](https://console.cloud.google.com/marketplace/details/influxdata-public/cloud2-gcp-marketplace-prod),
and follow the prompts to subscribe. After you click **Set Up Your Account**,
enter your credentials, and then click **Start Now**.
All usage charges will be paid through the subscribed GCP account.
{{%note%}}
Currently, we do **not support** using an existing InfluxDB Cloud 2.0 account to sign up for an InfluxDB Cloud 2.0 plan through AWS or GCP Marketplaces.
{{%/note%}}
2. InfluxDB Cloud requires email verification to complete the sign up process.
Verify your email address by opening the email sent to the address you provided and clicking **Verify Your Email**.
3. (If you subscribed through InfluxData) Choose your cloud provider.
4. Select a provider and region for your {{< cloud-name >}} instance. The following are available:
- **Amazon Web Services (AWS)**
- **US West (Oregon)**
- **EU Frankfurt**
- **Google Cloud Platform (GCP)**
- **Iowa**
_To suggest regions to add, click **Let us know** under Regions._
5. (If you subscribed through InfluxData) Review the terms of the agreement, and then select **I have viewed and agree to InfluxDB Cloud 2.0 Services Subscription Agreement and InfluxData Global Data Processing Agreement**.
For details on the agreements, see the [InfluxDB Cloud 2.0: Services Subscription Agreement](https://www.influxdata.com/legal/terms-of-use/) and the [InfluxData Global Data Processing Agreement](https://www.influxdata.com/legal/influxdata-global-data-processing-agreement/).
6. Click **Finish**. {{< cloud-name >}} opens with a default organization and bucket (both created from your email address).
_To update organization and bucket names, see [Update an organization](/v2.0/organizations/update-org/)
and [Update a bucket](/v2.0/organizations/buckets/update-bucket/#update-a-bucket-s-name-in-the-influxdb-ui)._
{{% cloud %}}
All InfluxDB 2.0 documentation applies to {{< cloud-name "short" >}} unless otherwise specified.
References to the InfluxDB user interface (UI) or localhost:9999 refer to your
{{< cloud-name >}} UI.
{{% /cloud %}}
### Sign in
Sign in to [InfluxDB Cloud 2.0](https://cloud2.influxdata.com) using your email address and password.
<a class="btn" href="https://cloud2.influxdata.com">Sign in to InfluxDB Cloud 2.0 now</a>
### Start working with your time series data
With {{< cloud-name "short" >}} setup, see [Next steps](#next-steps) for what to do next.
---
## Start with InfluxDB OSS
Get started with InfluxDB OSS v2.0 by downloading InfluxDB, installing the necessary
executables, and running the initial setup process.
{{% cloud-msg %}}
This article describes how to get started with InfluxDB OSS. To get started with {{< cloud-name "short" >}}, see [Get Started with {{< cloud-name >}}](/v2.0/cloud/get-started/).
{{% /cloud-msg %}}
{{< tabs-wrapper >}}
{{% tabs %}}
[macOS](#)
@ -28,7 +116,7 @@ This article describes how to get started with InfluxDB OSS. To get started with
### Download and install InfluxDB v2.0 beta
Download InfluxDB v2.0 beta for macOS.
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.7_darwin_amd64.tar.gz" download>InfluxDB v2.0 beta (macOS)</a>
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.9_darwin_amd64.tar.gz" download>InfluxDB v2.0 beta (macOS)</a>
### Unpackage the InfluxDB binaries
To unpackage the downloaded archive, **double click the archive file in Finder**
@ -37,7 +125,7 @@ or run the following command in a macOS command prompt application such
```sh
# Unpackage contents to the current working directory
tar zxvf ~/Downloads/influxdb_2.0.0-beta.7_darwin_amd64.tar.gz
tar zxvf ~/Downloads/influxdb_2.0.0-beta.9_darwin_amd64.tar.gz
```
#### (Optional) Place the binaries in your $PATH
@ -46,7 +134,7 @@ prefix the executables with `./` to run then in place.
```sh
# (Optional) Copy the influx and influxd binary to your $PATH
sudo cp influxdb_2.0.0-beta.7_darwin_amd64/{influx,influxd} /usr/local/bin/
sudo cp influxdb_2.0.0-beta.9_darwin_amd64/{influx,influxd} /usr/local/bin/
```
{{% note %}}
@ -56,11 +144,11 @@ or rename them before putting them in your `$PATH`.
If you rename the binaries, all references to `influx` and `influxd` in this documentation refer to your renamed binaries.
{{% /note %}}
### Networking ports
#### Networking ports
By default, InfluxDB uses TCP port `9999` for client-server communication over
the [InfluxDB HTTP API](/v2.0/reference/api/).
## Start InfluxDB
### Start InfluxDB
Start InfluxDB by running the `influxd` daemon:
```bash
@ -106,8 +194,8 @@ influxd --reporting-disabled
### Download and install InfluxDB v2.0 beta
Download the InfluxDB v2.0 beta package appropriate for your chipset.
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.7_linux_amd64.tar.gz" download >InfluxDB v2.0 beta (amd64)</a>
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.7_linux_arm64.tar.gz" download >InfluxDB v2.0 beta (arm)</a>
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.9_linux_amd64.tar.gz" download >InfluxDB v2.0 beta (amd64)</a>
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_2.0.0-beta.9_linux_arm64.tar.gz" download >InfluxDB v2.0 beta (arm)</a>
### Place the executables in your $PATH
Unpackage the downloaded archive and place the `influx` and `influxd` executables in your system `$PATH`.
@ -116,10 +204,10 @@ _**Note:** The following commands are examples. Adjust the file names, paths, an
```sh
# Unpackage contents to the current working directory
tar xvzf path/to/influxdb_2.0.0-beta.7_linux_amd64.tar.gz
tar xvzf path/to/influxdb_2.0.0-beta.9_linux_amd64.tar.gz
# Copy the influx and influxd binary to your $PATH
sudo cp influxdb_2.0.0-beta.7_linux_amd64/{influx,influxd} /usr/local/bin/
sudo cp influxdb_2.0.0-beta.9_linux_amd64/{influx,influxd} /usr/local/bin/
```
{{% note %}}
@ -129,11 +217,11 @@ or rename them before putting them in your `$PATH`.
If you rename the binaries, all references to `influx` and `influxd` in this documentation refer to your renamed binaries.
{{% /note %}}
### Networking ports
#### Networking ports
By default, InfluxDB uses TCP port `9999` for client-server communication over
the [InfluxDB HTTP API](/v2.0/reference/api/).
## Start InfluxDB
### Start InfluxDB
Start InfluxDB by running the `influxd` daemon:
```bash
@ -209,13 +297,13 @@ The instructions below use Minikube, but the steps should be similar in any Kube
2. Start Minikube:
```
```sh
minikube start
```
3. Apply the [sample InfluxDB configuration](https://github.com/influxdata/docs-v2/blob/master/static/downloads/influxdb-k8-minikube.yaml) by running:
```
```sh
kubectl apply -f https://raw.githubusercontent.com/influxdata/docs-v2/master/static/downloads/influxdb-k8-minikube.yaml
```
@ -230,13 +318,13 @@ The instructions below use Minikube, but the steps should be similar in any Kube
4. Ensure the Pod is running:
```
```sh
kubectl get pods -n influxdb
```
5. Ensure the Service is available:
```
```sh
kubectl describe service -n influxdb influxdb
```
@ -244,7 +332,7 @@ The instructions below use Minikube, but the steps should be similar in any Kube
6. Forward port 9999 from inside the cluster to localhost:
```
```sh
kubectl port-forward -n influxdb service/influxdb 9999:9999
```
@ -290,6 +378,10 @@ use one of the following methods to provide your [authentication token](/v2.0/us
1. Pass your token to the `influx` CLI using the `-t` or `--token` flag.
2. Set the `INFLUX_TOKEN` environment variable using your token.
```bash
export INFLUX_TOKEN=oOooYourAuthTokenOoooOoOO==
```
3. Store your token in `~/.influxdbv2/credentials`.
_The content of the `credentials` file should be only your token._
@ -329,3 +421,80 @@ to provide the required information.
{{% /tab-content %}}
<!------------------------------- END UI Setup -------------------------------->
{{< /tabs-wrapper >}}
---
## Next Steps
### Collect and write data
Collect and write data to InfluxDB using the Telegraf plugins, the InfluxDB v2 API, the `influx`
command line interface (CLI), the InfluxDB UI (the user interface for InfluxDB 2.0), or the InfluxDB v2 API client libraries.
#### Use Telegraf
Use Telegraf to quickly write data to {{< cloud-name >}}.
Create new Telegraf configurations automatically in the InfluxDB UI, or manually update an
existing Telegraf configuration to send data to your {{< cloud-name "short" >}} instance.
For details, see [Automatically configure Telegraf](/v2.0/write-data/use-telegraf/auto-config/#create-a-telegraf-configuration)
and [Manually update Telegraf configurations](/v2.0/write-data/use-telegraf/manual-config/).
#### Scrape data
**InfluxDB OSS** lets you scrape Prometheus-formatted metrics from HTTP endpoints.
For details, see [Scrape data](/v2.0/write-data/scrape-data/).
#### API, CLI, and client libraries
For information about using the InfluxDB v2 API, `influx` CLI, and client libraries to write data,
see [Write data to InfluxDB](/v2.0/write-data/).
### Query data
Query data using Flux, the UI, and the `influx` command line interface.
See [Query data](/v2.0/query-data/).
### Process data
Use InfluxDB tasks to process and downsample data. See [Process data](/v2.0/process-data/).
### Visualize data
Build custom dashboards to visualize your data.
See [Visualize data](/v2.0/visualize-data/).
### Monitor and alert
Monitor your data and sends alerts based on specified logic.
See [Monitor and alert](/v2.0/monitor-alert/).
## Differences between InfluxDB Cloud and InfluxDB OSS
{{< cloud-name >}} is API-compatible and functionally compatible with InfluxDB OSS 2.0.
The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud 2.0 are:
- [InfluxDB scrapers](/v2.0/write-data/scrape-data/) that collect data from specified
targets are not available in {{< cloud-name "short" >}}.
- {{< cloud-name "short" >}} instances are currently limited to a single organization with a single user.
- **InfluxDB Cloud** does not support retrieving data from a file based CSV source
using the `file` parameter of the [`csv.from()`](/v2.0/reference/flux/functions/csv/from);
however you can use raw CSV data with the `csv` parameter.
#### New features in InfluxDB Cloud 2.0
- **Free Plan (rate-limited)**: Skip downloading and installing InfluxDB 2.0 and
jump into exploring InfluxDB 2.0 technology.
The Free Plan is designed for getting started with InfluxDB and for small hobby projects.
- **Flux support**: [Flux](/v2.0/query-data/get-started/) is a standalone data
scripting and query language that increases productivity and code reuse.
It is the primary language for working with data within InfluxDB 2.0.
Flux can be used with other data sources as well, letting you work with data where it resides.
- **Unified API**: Everything in InfluxDB (ingest, query, storage, and visualization)
is now accessible using a unified [InfluxDB v2 API](/v2.0/reference/api/) that
enables seamless movement between open source and cloud.
- **Integrated visualization and dashboards**: Based on the pioneering Chronograf project,
the new user interface (InfluxDB UI) offers quick and effortless onboarding,
richer user experiences, and significantly quicker results.
- **Usage-based pricing**: The [Usage-based Plan](/v2.0/account-management/pricing-plans/#usage-based-plan)
offers more flexibility and ensures that you only pay for what you use.

2
content/v2.0/influxdb-templates/_index.md
View File

@ -4,7 +4,7 @@ description: >
InfluxDB templates are prepackaged InfluxDB configurations that contain everything
from dashboards and Telegraf configurations to notifications and alerts.
menu: v2_0
weight: 10
weight: 9
v2.0/tags: [templates]
---

10
content/v2.0/influxdb-templates/use.md
View File

@ -137,12 +137,12 @@ influx pkg -u <template-url>
# Examples
# Install a single template from a URL
influx pkg -u https://mydomain.com/templates/template.yml
influx pkg -u https://example.com/templates/template.yml
# Install multiple templates from URLs
influx pkg \
-u https://mydomain.com/templates/template1.yml \
-u https://mydomain.com/templates/template2.yml
-u https://example.com/templates/template1.yml \
-u https://example.com/templates/template2.yml
```
### Install templates from both files and URLs
@ -155,8 +155,8 @@ influx pkg -u <template-url> -f <template-path>
# Example
influx pkg \
-u https://mydomain.com/templates/template1.yml \
-u https://mydomain.com/templates/template2.yml \
-u https://example.com/templates/template1.yml \
-u https://example.com/templates/template2.yml \
-f ~/templates/custom-template.yml \
-f ~/templates/iot/home/ \
--recurse

5
content/v2.0/monitor-alert/checks/create.md
View File

@ -43,12 +43,11 @@ A deadman check assigns a status to data when a series or group doesn't report
in a specified amount of time.
## Create a check in the InfluxDB UI
1. Click **Monitoring & Alerting** in the sidebar in the InfluxDB UI.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. In the top right corner of the **Checks** column, click **{{< icon "plus" >}} Create**
and select the [type of check](#check-types) to create.
2. Click **{{< icon "plus" >}} Create** and select the [type of check](#check-types) to create.
3. Click **Name this check** in the top left corner and provide a unique name for the check.
#### Configure the check query

6
content/v2.0/monitor-alert/checks/delete.md
View File

@ -18,12 +18,12 @@ If you no longer need a check, use the InfluxDB user interface (UI) to delete it
Deleting a check cannot be undone.
{{% /warn %}}
1. Click **Monitoring & Alerting** in the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. In the **Checks** column, hover over the check you want to delete, click the
**{{< icon "delete" >}}** icon, then **Delete**.
2. Hover over the check you want to delete, click the **{{< icon "delete" >}}**
icon, and then **Delete**.
After a check is deleted, all statuses generated by the check remain in the `_monitoring`
bucket until the retention period for the bucket expires.

18
content/v2.0/monitor-alert/checks/update.md
View File

@ -21,37 +21,35 @@ Common updates include:
- [Add or update a check description](#add-or-update-a-check-description)
- [Add a label to a check](#add-a-label-to-a-check)
To update checks, click **Monitoring & Alerting** in the InfluxDB UI sidebar.
To update checks, select **Alerts** in the navigation menu on the left.
{{< nav-icon "alerts" >}}
## Update check queries and logic
1. In the **Checks** column, click the name of the check you want to update.
The check builder appears.
2. To edit the check query, click **1. Query** at the top of the check builder window.
3. To edit the check logic, click **2. Check** at the top of the check builder window.
1. Click the name of the check you want to update. The check builder appears.
2. To edit the check query, click **1. Define Query** at the top of the check builder window.
3. To edit the check logic, click **2. Configure Check** at the top of the check builder window.
_For details about using the check builder, see [Create checks](/v2.0/monitor-alert/checks/create/)._
## Enable or disable a check
In the **Checks** column, click the {{< icon "toggle" >}} toggle next to a check
to enable or disable it.
Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it.
## Rename a check
1. In the **Checks** column, hover over the name of the check you want to update.
1. Hover over the name of the check you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the check name.
2. Enter a new name and click out of the name field or press enter to save.
_You can also rename a check in the [check builder](#update-check-queries-and-logic)._
## Add or update a check description
1. In the **Checks** column, hover over the check description you want to update.
1. Hover over the check description you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the description.
2. Enter a new description and click out of the name field or press enter to save.
## Add a label to a check
1. In the **Checks** column, click **Add a label** next to the check you want to add a label to.
1. Click **Add a label** next to the check you want to add a label to.
The **Add Labels** box opens.
2. To add an existing label, select the label from the list.
3. To create and add a new label:

20
content/v2.0/monitor-alert/checks/view.md
View File

@ -19,25 +19,25 @@ View check details and statuses and notifications generated by checks in the Inf
- [View statuses generated by a check](#view-statuses-generated-by-a-check)
- [View notifications triggered by a check](#view-notifications-triggered-by-a-check)
To view checks, click **Monitoring & Alerting** in the InfluxDB UI sidebar.
To view checks, click **Alerts** in navigation menu on the left.
{{< nav-icon "alerts" >}}
## View a list of all checks
The **Checks** column on the Monitoring & Alerting landing page displays all existing checks.
The **Checks** section of the Alerts landing page displays all existing checks.
## View check details
In the **Checks** column, click the name of the check you want to view.
Click the name of the check you want to view.
The check builder appears.
Here you can view the check query and logic.
## View statuses generated by a check
1. In the **Checks** column, hover over the check, click the **{{< icon "view" >}}**
icon, then **View History**.
The Statuses History page displays statuses generated by the selected check.
1. Hover over the check and click the **{{< icon "view" >}}** icon.
2. Click **View History**.
The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a check
1. In the **Checks** column, hover over the check, click the **{{< icon "view" >}}**
icon, then **View History**.
2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected check.
1. Hover over the check, click the **{{< icon "view" >}}**
icon, then **View History**.
2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected check.

11
content/v2.0/monitor-alert/notification-endpoints/create.md
View File

@ -16,12 +16,13 @@ To send notifications about changes in your data, start by creating a notificati
## Create a notification endpoint in the UI
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Next to **Notification Endpoints**, click **Create**.
3. From the **Destination** drop-down list, select a destination endpoint to send notifications.
2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "plus" >}} Create**.
4. From the **Destination** drop-down list, select a destination endpoint to send notifications.
The following endpoints are available for InfluxDB 2.0 OSS, the InfluxDB Cloud 2.0 Free Plan,
and the InfluxDB Cloud 2.0 Usage-based Plan:
@ -31,8 +32,8 @@ To send notifications about changes in your data, start by creating a notificati
| **PagerDuty** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
| **HTTP** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
4. In the **Name** and **Description** fields, enter a name and description for the endpoint.
5. Enter enter information to connect to the endpoint:
5. In the **Name** and **Description** fields, enter a name and description for the endpoint.
6. Enter enter information to connect to the endpoint:
- For HTTP, enter the **URL** to send the notification. Select the **auth method** to use: **None** for no authentication. To authenticate with a username and password, select **Basic** and then enter credentials in the **Username** and **Password** fields. To authenticate with a token, select **Bearer**, and then enter the authentication token in the **Token** field.

8
content/v2.0/monitor-alert/notification-endpoints/delete.md
View File

@ -16,9 +16,11 @@ If notifications are no longer sent to an endpoint, complete the steps below to
## Delete a notification endpoint in the UI
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, find the rule you want to delete.
3. Click the delete icon, then click **Delete** to confirm.
2. Select **Notification Endpoints** near to top of the page.
find the rule you want to delete.
3. Hover over the endpoint you want to delete and click the **{{< icon "trash" >}}** icon.
4. Click **Delete** to confirm.

37
content/v2.0/monitor-alert/notification-endpoints/update.md
View File

@ -16,50 +16,51 @@ To update the notification endpoint details, complete the procedures below as ne
## Add a label to notification endpoint
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Endpoints**, click **Add a label** next to the endpoint you want to add a label to. The **Add Labels** box opens.
3. To add an existing label, select the label from the list.
4. To create and add a new label:
2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the endpoint you want to add a label to.
The **Add Labels** box opens.
4. To add an existing label, select the label from the list.
5. To create and add a new label:
- In the search field, enter the name of the new label. The **Create Label** box opens.
- In the **Description** field, enter an optional description for the label.
- Select a color for the label.
- Click **Create Label**.
5. To remove a label, hover over the label under an endpoint and click X.
6. To remove a label, hover over the label under an endpoint and click X.
## Disable notification endpoint
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Endpoints**, find the endpoint you want to disable.
3. Click the blue toggle to disable the notification endpoint.
2. Select **Notification Endpoints** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification endpoint.
## Update the name or description for notification endpoint
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Endpoints**, hover over the name or description of the endpoint.
3. Click the pencil icon to edit the field.
2. Select **Notification Endpoints** near to top of the page.
3. Hover over the name or description of the endpoint and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field.
4. Click outside of the field to save your changes.
## Change endpoint details
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Endpoints**, click the endpoint to update.
3. Update details as needed, and then click **Edit a Notification Endpoint**. For details about each field, see [Create notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/).
2. Select **Notification Endpoints** near to top of the page.
3. Click the endpoint to update.
4. Update details as needed, and then click **Edit Notification Endpoint**.
For details about each field, see [Create notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/).

28
content/v2.0/monitor-alert/notification-endpoints/view.md
View File

@ -21,23 +21,31 @@ View notification endpoint details and history in the InfluxDB user interface (U
## View notification endpoints
- Click **Monitoring & Alerting** in the InfluxDB UI sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
In the **Notification Endpoints** column, view existing notification endpoints.
2. Select **Notification Endpoints** near to top of the page.
## View notification endpoint details
1. Click **Monitoring & Alerting** in the InfluxDB UI sidebar.
2. In the **Notification Endpoints** column, click the name of the notification endpoint you want to view.
3. View the notification endpoint destination, name, and information to connect to the endpoint.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page.
3. Click the name of the notification endpoint you want to view.
4. View the notification endpoint destination, name, and information to connect to the endpoint.
## View notification endpoint history
1. Click **Monitoring & Alerting** in the InfluxDB UI sidebar.
2. In the **Notification Endpoints** column, hover over the notification endpoint, click the **{{< icon "view" >}}** icon, then **View History**.
The Check Statuses History page displays:
1. In the navigation menu on the left, select **Alerts**.
- Statuses generated for the selected notification endpoint
- Notifications sent to the selected notification endpoint
{{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page.
3. Hover over the notification endpoint, click the **{{< icon "view" >}}** icon, then **View History**.
The Check Statuses History page displays:
- Statuses generated for the selected notification endpoint
- Notifications sent to the selected notification endpoint

20
content/v2.0/monitor-alert/notification-rules/create.md
View File

@ -17,26 +17,28 @@ _For details, see [Manage checks](/v2.0/monitor-alert/checks/) and
## Create a new notification rule in the UI
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, click **+Create**.
3. Complete the **About** section:
2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "plus" >}} Create**.
4. Complete the **About** section:
1. In the **Name** field, enter a name for the notification rule.
2. In the **Schedule Every** field, enter how frequently the rule should run.
3. In the **Offset** field, enter an offset time. For example,if a task runs on the hour, a 10m offset delays the task to 10 minutes after the hour. Time ranges defined in the task are relative to the specified execution time.
4. In the **Conditions** section, build a condition using a combination of status and tag keys.
5. In the **Conditions** section, build a condition using a combination of status and tag keys.
- Next to **When status is equal to**, select a status from the drop-down field.
- Next to **AND When**, enter one or more tag key-value pairs to filter by.
5. In the **Message** section, select an endpoint to notify.
6. Click **Create Notification Rule**.
6. In the **Message** section, select an endpoint to notify.
7. Click **Create Notification Rule**.
## Clone an existing notification rule in the UI
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. 1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, hover over the rule you want to clone.
3. Click the clone icon and select **Clone**. The cloned rule appears.
2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to clone and click the **{{< icon "clone" >}}** icon and select **Clone**.
The cloned rule appears.

7
content/v2.0/monitor-alert/notification-rules/delete.md
View File

@ -13,9 +13,10 @@ related:
## Delete a notification rule in the UI
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, find the rule you want to delete.
3. Click the delete icon, then click **Delete** to confirm.
2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to delete and click the **{{< icon "trash" >}}** icon.
4. Click **Delete** to confirm.

29
content/v2.0/monitor-alert/notification-rules/update.md
View File

@ -13,39 +13,38 @@ related:
## Add a label to notification rules
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, click **Add a label** next to the rule you want to add a label to. The **Add Labels** box opens.
3. To add an existing label, select the label from the list.
4. To create and add a new label:
2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the rule you want to add a label to.
The **Add Labels** box opens.
4. To add an existing label, select the label from the list.
5. To create and add a new label:
- In the search field, enter the name of the new label. The **Create Label** box opens.
- In the **Description** field, enter an optional description for the label.
- Select a color for the label.
- Click **Create Label**.
5. To remove a label, hover over the label under to a rule and click X.
6. To remove a label, hover over the label under to a rule and click **{{< icon "x" >}}**.
## Disable notification rules
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, find the rule you want to disable.
3. Click the blue toggle to disable the notification rule.
2. Select **Notification Rules** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification rule.
## Update the name or description for notification rules
1. Select the **Monitoring and Alerting** icon from the sidebar.
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Under **Notification Rules**, hover over the name or description of a rule.
3. Click the pencil icon to edit the field.
2. Select **Notification Rules** near to top of the page.
3. Hover over the name or description of a rule and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field.
4. Click outside of the field to save your changes.

25
content/v2.0/monitor-alert/notification-rules/view.md
View File

@ -18,25 +18,28 @@ View notification rule details and statuses and notifications generated by notif
- [View statuses generated by a check](#view-statuses-generated-by-a-notification-rule)
- [View notifications triggered by a notification rule](#view-notifications-triggered-by-a-notification-rule)
To view notification rules, click **Monitoring & Alerting** in the InfluxDB UI sidebar.
**To view notification rules:**
{{< nav-icon "alerts" >}}
1. In the navigation menu on the left, select **Alerts**.
{{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page.
## View a list of all notification rules
The **Notification Rules** column on the Monitoring & Alerting landing page displays all existing checks.
The **Notification Rules** section of the Alerts landing page displays all existing checks.
## View notification rule details
In the **Notification Rules** column, click the name of the check you want to view.
Click the name of the check you want to view.
The check builder appears.
Here you can view the check query and logic.
## View statuses generated by a notification rule
1. In the **Notification Rules** column, hover over the check, click the **{{< icon "view" >}}**
icon, then **View History**.
The Statuses History page displays statuses generated by the selected check.
Hover over the check, click the **{{< icon "view" >}}** icon, and then **View History**.
The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a notification rule
1. In the **Notification Rules** column, hover over the notification rule, click the **{{< icon "view" >}}**
icon, then **View History**.
2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected notification rule.
1. Hover over the notification rule, click the **{{< icon "view" >}}**
icon, and then **View History**.
2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected notification rule.

11
content/v2.0/organizations/buckets/create-bucket.md
View File

@ -14,14 +14,13 @@ to create a bucket.
## Create a bucket in the InfluxDB UI
1. Click **Load Data** in the navigation bar.
1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
{{< nav-icon "load data" >}}
{{< nav-icon "data" >}}
2. Select **Buckets**.
3. Click **{{< icon "plus" >}} Create Bucket** in the upper right.
4. Enter a **Name** for the bucket.
5. Select when to **Delete Data**:
2. Click **{{< icon "plus" >}} Create Bucket** in the upper right.
3. Enter a **Name** for the bucket.
4. Select when to **Delete Data**:
- **Never** to retain data forever.
- **Older than** to choose a specific retention policy.
5. Click **Create** to create the bucket.

9
content/v2.0/organizations/buckets/delete-bucket.md
View File

@ -14,13 +14,12 @@ to delete a bucket.
## Delete a bucket in the InfluxDB UI
1. Click **Load Data** in the navigation bar.
1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
{{< nav-icon "load data" >}}
{{< nav-icon "data" >}}
2. Select **Buckets**.
3. Hover over the bucket you would like to delete.
4. Click **{{< icon "delete" >}} Delete Bucket** and **Confirm** to delete the bucket.
2. Hover over the bucket you would like to delete.
3. Click **{{< icon "delete" >}} Delete Bucket** and **Confirm** to delete the bucket.
## Delete a bucket using the influx CLI

23
content/v2.0/organizations/buckets/update-bucket.md
View File

@ -24,25 +24,24 @@ If you change a bucket name, be sure to update the bucket in the above places as
## Update a bucket's name in the InfluxDB UI
1. Click **Load Data** in the navigation bar.
1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
{{< nav-icon "load data" >}}
{{< nav-icon "data" >}}
2. Select **Buckets**.
3. Click **Rename** under the bucket you want to rename.
4. Review the information in the window that appears and click **I understand, let's rename my bucket**.
5. Update the bucket's name and click **Change Bucket Name**.
2. Click **Settings** under the bucket you want to rename.
3. Click **Rename**.
3. Review the information in the window that appears and click **I understand, let's rename my bucket**.
4. Update the bucket's name and click **Change Bucket Name**.
## Update a bucket's retention policy in the InfluxDB UI
1. Click **Load Data** in the navigation bar.
1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
{{< nav-icon "load data" >}}
{{< nav-icon "data" >}}
2. Select **Buckets**.
3. Click the name of the bucket you want to update from the list.
4. In the window that appears, edit the bucket's retention policy.
5. Click **Save Changes**.
2. Click **Settings** next to the bucket you want to update.
3. In the window that appears, edit the bucket's retention policy.
4. Click **Save Changes**.
## Update a bucket using the influx CLI

7
content/v2.0/organizations/buckets/view-buckets.md
View File

@ -11,12 +11,11 @@ weight: 202
## View buckets in the InfluxDB UI
1. Click **Load Data** in the navigation bar.
1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
{{< nav-icon "load data" >}}
{{< nav-icon "data" >}}
2. Select **Buckets**.
3. Click a bucket to open it **Data Explorer**.
2. Click a bucket to open it **Data Explorer**.
## View buckets using the influx CLI

14
content/v2.0/organizations/create-org.md
View File

@ -7,23 +7,25 @@ menu:
name: Create an organization
parent: Manage organizations
weight: 101
products: [oss]
---
Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
to create an organization.
{{% cloud-msg %}}
You cannot currently create additional organizations in {{< cloud-name >}}. Only the default organization is available.
{{% /cloud-msg %}}
{{% cloud %}}
You cannot currently create additional organizations in {{< cloud-name >}}.
Only the default organization is available.
{{% /cloud %}}
## Create an organization in the InfluxDB UI
1. Click the **Influx** icon in the navigation bar.
1. In the navigation menu on the left, click the **Account dropdown**.
{{< nav-icon "admin" >}}
{{< nav-icon "account" >}}
2. Select **Create Organization**.
3. In the window that appears, enter a name for the organization and associated bucket and click **Create**.
3. In the window that appears, enter an **Organization Name** and **Bucket Name** and click **Create**.
## Create an organization using the influx CLI

5
content/v2.0/organizations/delete-org.md
View File

@ -7,6 +7,7 @@ menu:
name: Delete an organization
parent: Manage organizations
weight: 104
products: [oss]
---
Use the `influx` command line interface (CLI)
@ -15,9 +16,9 @@ to delete an organization.
<!--
## Delete an organization in the InfluxDB UI
1. Click the **Influx** icon in the navigation bar.
1. In the navigation menu on the left, click the **Account dropdown**.
{{< nav-icon "admin" >}}
{{< nav-icon "account" >}}
The list of organizations appears.

12
content/v2.0/organizations/members/add-member.md
View File

@ -11,17 +11,15 @@ weight: 201
Use the `influx` command line interface (CLI) to add a member to an organization.
{{% cloud-msg %}}
{{% cloud %}}
Adding members is currently unavailable in {{< cloud-name >}}.
{{% /cloud-msg %}}
{{% /cloud %}}
<!-- ## Add a member to an organization in the InfluxDB UI
1. Click the **Settings** tab in the navigation bar.
1. In the navigation menu on the left, select **Org (Organization)** > **Members**.
{{< nav-icon "settings" >}}
2. Click the name of an organization, then select the **Members** tab.
{{< nav-icon "org" >}}
_Complete content coming soon_ -->
@ -36,7 +34,7 @@ influx user list
2. To add a user to an organization, run the following command:
```sh
influx org members add -n <org-name> -o <user-ID>
influx org members add -n <org-name> -m <user-ID>
```
For more information, see the [`influx org members add` command](/v2.0/reference/cli/influx/org/members/add).

9
content/v2.0/organizations/members/remove-member.md
View File

@ -20,13 +20,12 @@ For information about deleting a user from InfluxDB, see [Delete a user](/v2.0/u
## Remove a member from an organization in the InfluxDB UI
1. Click **Settings** in the left navigation bar.
1. In the navigation menu on the left, select **Org (Organization)** > **Members**.
{{< nav-icon "settings" >}}
{{< nav-icon "org" >}}
2. Select **Members**.
3. Hover over the member you would like to delete and click the **{{< icon "delete" >}}** icon.
4. Click **Delete**.
2. Hover over the member you would like to delete and click the **{{< icon "delete" >}}** icon.
3. Click **Delete**.
## Remove a member from an organization using the influx CLI

6
content/v2.0/organizations/members/view-members.md
View File

@ -14,11 +14,9 @@ to view members of an organization.
## View members of organization in the InfluxDB UI
* Click the **Settings** tab in the navigation bar.
In the navigation menu on the left, select **Org (Organization)** > **Members**.
{{< nav-icon "settings" >}}
* Click the name of an organization, then select the **Members** tab. The list of organization members appears.
{{< nav-icon "org" >}}
## View members of organization using the influx CLI

7
content/v2.0/organizations/switch-org.md
View File

@ -7,15 +7,16 @@ menu:
name: Switch organizations
parent: Manage organizations
weight: 105
products: [oss]
---
Use the InfluxDB user interface (UI) to switch from one organization to another. The organization you're currently viewing determines what dashboards, tasks, buckets, members, and other assets you can access.
## Switch organizations in the InfluxDB UI
1. Click the **Influx** icon in the navigation bar.
1. In the navigation menu on the left, click the **Account dropdown**.
{{< nav-icon "admin" >}}
{{< nav-icon "account" >}}
2. Select **Switch Organizations**. The list of organizations appears.
2. Select **Switch Organizations**.
3. Click the organization you want to switch to.

13
content/v2.0/organizations/update-org.md
View File

@ -23,15 +23,14 @@ If you change an organization name, be sure to update the organization in the ab
## Update an organization in the InfluxDB UI
1. Click the **Settings** icon in the navigation bar.
1. In the navigation menu on the left, click the **Org (Organization)** > **About**.
{{< nav-icon "settings" >}}
{{< nav-icon "org" >}}
2. Click the **Org Profile** tab.
3. Click **Rename**.
4. In the window that appears, review the information and click **I understand, let's rename my organization**.
5. Enter a new name for your organization.
6. Click **Change organization name**.
2. Click **{{< icon "edit" >}} Rename**.
3. In the window that appears, review the information and click **I understand, let's rename my organization**.
4. Enter a new name for your organization.
5. Click **Change organization name**.
## Update an organization using the influx CLI

10
content/v2.0/organizations/view-orgs.md
View File

@ -14,12 +14,15 @@ to view organizations.
## View organizations in the InfluxDB UI
* Click the **Influx** icon in the navigation bar.
1. In the navigation menu on the left, click the **Account dropdown**.
{{< nav-icon "admin" >}}
{{< nav-icon "account" >}}
* Select **Switch Organizations**. The list of organizations appears.
2. Select **Switch Organizations**. The list of organizations appears.
{{% cloud %}}
**{{< cloud-name "short" >}}** does not support viewing and switching between multiple organizations.
{{% /cloud %}}
## View organizations using the influx CLI
@ -40,6 +43,7 @@ Use the InfluxDB UI or `influx` CLI to view your organization ID.
### Organization ID in the UI
After logging in to the InfluxDB UI, your organization ID appears in the URL.
<pre class="highlight">
http://localhost:9999/orgs/<span class="bp" style="font-weight:bold;margin:0 .15rem">03a2bbf46249a000</span>/...
</pre>

16
content/v2.0/process-data/manage-tasks/create-task.md
View File

@ -30,11 +30,11 @@ The InfluxDB UI provides multiple ways to create a task:
- [Clone a task](#clone-a-task)
### Create a task from the Data Explorer
1. Click the **Data Explorer** icon in the left navigation menu.
1. In the navigation menu on the left, select **Explore** (**Data Explorer**).
{{< nav-icon "data-explorer" >}}
2. Building a query and click **Save As** in the upper right.
2. Build a query and click **Save As** in the upper right.
3. Select the **Task** option.
4. Specify the task options. See [Task options](/v2.0/process-data/task-options)
for detailed information about each option.
@ -43,7 +43,7 @@ The InfluxDB UI provides multiple ways to create a task:
### Create a task in the Task UI
1. Click the **Tasks** icon in the left navigation menu.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}
@ -56,7 +56,7 @@ The InfluxDB UI provides multiple ways to create a task:
7. Click **Save** in the upper right.
### Import a task
1. Click the **Tasks** icon in the left navigation menu.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}
@ -69,7 +69,7 @@ The InfluxDB UI provides multiple ways to create a task:
5. Click **Import JSON as Task**.
### Create a task from a template
1. Click the **Settings** icon in the left navigation menu.
1. In the navigation menu on the left, select **Settings** > **Templates**.
{{< nav-icon "Settings" >}}
@ -78,7 +78,7 @@ The InfluxDB UI provides multiple ways to create a task:
### Clone a task
1. Click the **Tasks** icon in the left navigation menu.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}
@ -92,10 +92,10 @@ It accepts either a file path or raw Flux.
###### Create a task using a file
```sh
# Syntax
influx task create --org <org-name> @</path/to/task-script>
influx task create --org <org-name> -f </path/to/task-script>
# Example
influx task create --org my-org @/tasks/cq-mean-1h.flux
influx task create --org my-org -f /tasks/cq-mean-1h.flux
```
###### Create a task using raw Flux

2
content/v2.0/process-data/manage-tasks/delete-task.md
View File

@ -13,7 +13,7 @@ related:
---
## Delete a task in the InfluxDB UI
1. Click the **Tasks** icon in the left navigation menu.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}

2
content/v2.0/process-data/manage-tasks/export-task.md
View File

@ -13,7 +13,7 @@ InfluxDB lets you export tasks from the InfluxDB user interface (UI).
Tasks are exported as downloadable JSON files.
## Export a task in the InfluxDB UI
1. Click the **Tasks** icon in the left navigation menu.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}

2
content/v2.0/process-data/manage-tasks/run-task.md
View File

@ -18,7 +18,7 @@ however, you can manually run a task from the InfluxDB user interface (UI) or th
`influx` command line interface (CLI).
## Run a task from the InfluxDB UI
1. Click the **Tasks** icon in the left navigation to view the lists of tasks.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}

2
content/v2.0/process-data/manage-tasks/task-run-history.md
View File

@ -20,7 +20,7 @@ to view task run histories and associated logs.
## View a task's run history in the InfluxDB UI
1. Click the **Tasks** icon in the left navigation to view the lists of tasks.
1. In the navigation menu on the left, select **Tasks**.
{{< nav-icon "tasks" >}}

6
content/v2.0/process-data/manage-tasks/update-task.md
View File

@ -13,7 +13,7 @@ related:
---
## Update a task in the InfluxDB UI
To view your tasks, click the **Tasks** icon in the left navigation menu.
Click the **Tasks** icon in the left navigation to view the lists of tasks.
{{< nav-icon "tasks" >}}
@ -48,10 +48,10 @@ script are also updated.
```sh
# Syntax
influx task update -i <task-id> @/path/to/updated-task-script
influx task update -i <task-id> -f </path/to/updated-task-script>
# Example
influx task update -i 0343698431c35000 @/tasks/cq-mean-1h.flux
influx task update -i 0343698431c35000 -f /tasks/cq-mean-1h.flux
```
#### Update the status of a task

4
content/v2.0/query-data/execute-queries.md
View File

@ -21,7 +21,7 @@ This guide covers the different options:
## Data Explorer
Queries can be built, executed, and visualized in InfluxDB UI's Data Explorer.
![Data Explorer with Flux](/img/2-0-data-explorer-ui.png)
![Data Explorer with Flux](/img/data-explorer-beta-8.png)
## Influx REPL
The [`influx repl` command](/v2.0/reference/cli/influx/repl) starts an interactive
@ -41,7 +41,7 @@ as either a file or raw Flux via stdin.
###### Run a query from a file
```bash
influx query @/path/to/query.flux
influx query --file /path/to/query.flux
```
###### Pass raw Flux via stdin pipe

16
content/v2.0/reference/api/_index.md
View File

@ -15,27 +15,11 @@ Access the InfluxDB API using the `/api/v2/` endpoint.
InfluxDB uses [authentication tokens](/v2.0/security/tokens/) to authorize API requests.
Include your authentication token as an `Authorization` header in each request.
{{< code-tabs-wrapper >}}
{{% code-tabs %}}
[InfluxDB OSS](#)
[InfluxDB Cloud](#)
{{% /code-tabs %}}
{{% code-tab-content %}}
```sh
curl --request POST \
--url http://localhost:9999/api/v2/write?org=my-org&bucket=example-bucket \
--header 'Authorization: Token YOURAUTHTOKEN'
```
{{% /code-tab-content %}}
{{% code-tab-content %}}
```sh
# Use the hostname of your InfluxDB Cloud UI
curl --request POST \
--url https://us-west-2-1.aws.cloud2.influxdata.com/api/v2/write?org=my-org&bucket=example-bucket \
--header 'Authorization: Token YOURAUTHTOKEN'
```
{{% /code-tab-content %}}
{{< /code-tabs-wrapper >}}
## View InfluxDB v2 API Documentation
<a class="btn" href="/v2.0/api/">InfluxDB v2.0 API documentation</a>

3
content/v2.0/reference/api/client-libraries/python.md
View File

@ -13,7 +13,7 @@ aliases:
weight: 201
---
Use the [InfluxDB Python client libary](https://github.com/influxdata/influxdb-client-python) to integrate InfluxDB into Python scripts and applications.
Use the [InfluxDB Python client library](https://github.com/influxdata/influxdb-client-python) to integrate InfluxDB into Python scripts and applications.
This guide presumes some familiarity with Python and InfluxDB.
If just getting started, see [Getting started with InfluxDB](/v2.0/get-started/).
@ -97,7 +97,6 @@ client = influxdb_client.InfluxDBClient(
org=org
)
client = influxdb_client.InfluxDBClient(url=url, token=token, org=org)
write_api = client.write_api(write_options=SYNCHRONOUS)
p = influxdb_client.Point("my_measurement").tag("location", "Prague").field("temperature", 25.3)

6
content/v2.0/reference/cli/influx/config/_index.md
View File

@ -30,6 +30,12 @@ influx config <config-name>
influx config local-config
```
To quickly switch back to the previous configuration, use the following command:
```sh
influx config -
```
## Subcommands
| Subcommand | Description |
|:---- |:----------- |

2
content/v2.0/reference/cli/influx/org/members/add.md
View File

@ -20,7 +20,7 @@ influx org members add [flags]
|:---- |:----------- |:----------: |:------------------ |
| `-h`, `--help` | Help for the `add` command | | |
| `-i`, `--id` | Organization ID | string | `INFLUX_ORG_ID` |
| `-o`, `--member` | Member ID | string | |
| `-m`, `--member` | Member ID | string | |
| `-n`, `--name` | Organization name | string | `INFLUX_ORG` |
{{% cli/influx-global-flags %}}

10
content/v2.0/reference/cli/influx/query/_index.md
View File

@ -16,14 +16,16 @@ or a literal Flux query contained in a file by specifying the file prefixed with
## Usage
```
influx query [query literal or @/path/to/query.flux] [flags]
influx query [query literal] [flags]
```
## Flags
| Flag | Description | Input type | {{< cli/mapped >}} |
|:---- |:----------- |:----------:|:------------------ |
|----------------|------------------------------|:----------:|--------------------|
| `-f`, `--file` | Path to Flux script file | string | |
| `-h`, `--help` | Help for the `query` command | | |
| `-o`, `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organization ID | string | `INFLUX_ORG_ID` |
| `-o`, `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organization ID | string | `INFLUX_ORG_ID` |
{{% cli/influx-global-flags %}}

18
content/v2.0/reference/cli/influx/task/create.md
View File

@ -12,16 +12,18 @@ The `influx task create` command creates a new task in InfluxDB.
## Usage
```
influx task create [query literal or @/path/to/query.flux] [flags]
influx task create [query literal] [flags]
```
## Flags
| Flag | Description | Input type | {{< cli/mapped >}} |
|:---- |:----------- |:----------: |:------------------ |
| `-h`, `--help` | Help for the `create` command | | |
| `--hide-headers` | Hide table headers (default `false`) | | `INFLUX_HIDE_HEADERS` |
| `--json` | Output data as JSON (default `false`) | | `INFLUX_OUTPUT_JSON` |
| `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organiztion ID | string | `INFLUX_ORG_ID` |
| Flag | Description | Input type | {{< cli/mapped >}} |
|------------------|---------------------------------------|:----------:|-----------------------|
| `-f`, `--file` | Path to Flux script file | string | |
| `-h`, `--help` | Help for the `create` command | | |
| `--hide-headers` | Hide table headers (default `false`) | | `INFLUX_HIDE_HEADERS` |
| `--json` | Output data as JSON (default `false`) | | `INFLUX_OUTPUT_JSON` |
| `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organization ID | string | `INFLUX_ORG_ID` |
{{% cli/influx-global-flags %}}

2
content/v2.0/reference/cli/influx/task/update.md
View File

@ -18,10 +18,12 @@ influx task update [flags]
## Flags
| Flag | Description | Input type | {{< cli/mapped >}} |
|:---- |:----------- |:----------: |:------------------ |
| `-f`, `--file` | Path to Flux script file | string | |
| `-h`, `--help` | Help for the `update` command | | |
| `--hide-headers` | Hide table headers (default `false`) | | `INFLUX_HIDE_HEADERS` |
| `-i`, `--id` | **(Required)** Task ID | string | |
| `--json` | Output data as JSON (default `false`) | | `INFLUX_OUTPUT_JSON` |
| `--status` | Update task status | string | |
{{% cli/influx-global-flags %}}

21
content/v2.0/reference/cli/influx/write/_index.md
View File

@ -1,8 +1,8 @@
---
title: influx write
description: >
The 'influx write' command writes line protocol to InfluxDB either via a single
line of line protocol, or a via a file containing line protocol.
The `influx write` command writes data to InfluxDB via stdin or from a specified file.
Write data using line protocol or annotated CSV.
menu:
v2_0_ref:
name: influx write
@ -11,20 +11,29 @@ weight: 101
v2.0/tags: [write]
---
The `influx write` writes a single line of line protocol to InfluxDB,
or adds an entire file specified with an `@` prefix.
The `influx write` command writes data to InfluxDB via stdin or from a specified file.
Write data using [line protocol](/v2.0/reference/syntax/line-protocol) or
[annotated CSV](/v2.0/reference/syntax/annotated-csv).
## Usage
```
influx write [line protocol or @/path/to/points.txt] [flags]
influx write [flags]
influx write [command]
```
## Subcommands
| Subcommand | Description |
|:---------- |:----------- |
| [dryrun](/v2.0/reference/cli/influx/write/dryrun) | Write to stdout instead of InfluxDB |
## Flags
| Flag | Description | Input type | {{< cli/mapped >}} |
|:---- |:----------- |:----------:|:------------------ |
| `-b`, `--bucket` | Bucket name | string | `INFLUX_BUCKET_NAME` |
| `--bucket-id` | Bucket ID | string | `INFLUX_BUCKET_ID` |
| `-h`, `--help` | Help for the `write` command | | |
| `-f`, `--file` | File to import | string | |
| `--format` | Input format (`lp` or `csv`, default `lp`) | string | |
| `-h`, `--help` | Help for the `dryrun` command | | |
| `-o`, `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organization ID | string | `INFLUX_ORG_ID` |
| `-p`, `--precision` | Precision of the timestamps (default `ns`) | string | `INFLUX_PRECISION` |

38
content/v2.0/reference/cli/influx/write/dryrun.md Normal file
View File

@ -0,0 +1,38 @@
---
title: influx write dryrun
description: >
The 'influx write dryrun' command prints write output to stdout instead of writing
to InfluxDB. Use this command to test writing data.
menu:
v2_0_ref:
name: influx write dryrun
parent: influx write
weight: 101
v2.0/tags: [write]
---
The `influx write dryrun` command prints write output to stdout instead of writing
to InfluxDB. Use this command to test writing data.
Supports [line protocol](/v2.0/reference/syntax/line-protocol) and
[annotated CSV](/v2.0/reference/syntax/annotated-csv).
Output is always **line protocol**.
## Usage
```
influx write dryrun [flags]
```
## Flags
| Flag | Description | Input type | {{< cli/mapped >}} |
|:---- |:----------- |:----------:|:------------------ |
| `-b`, `--bucket` | Bucket name | string | `INFLUX_BUCKET_NAME` |
| `--bucket-id` | Bucket ID | string | `INFLUX_BUCKET_ID` |
| `-f`, `--file` | File to import | string | |
| `--format` | Input format (`lp` or `csv`, defaults `lp`) | string | |
| `-h`, `--help` | Help for the `dryrun` command | | |
| `-o`, `--org` | Organization name | string | `INFLUX_ORG` |
| `--org-id` | Organization ID | string | `INFLUX_ORG_ID` |
| `-p`, `--precision` | Precision of the timestamps (default `ns`) | string | `INFLUX_PRECISION` |
{{% cli/influx-global-flags %}}

34
content/v2.0/reference/cli/influxd/_index.md
View File

@ -7,6 +7,9 @@ menu:
name: influxd
parent: Command line tools
weight: 102
related:
- /v2.0/reference/config-options/
products: [oss]
---
The `influxd` daemon starts and runs all the processes necessary for InfluxDB to function.
@ -30,33 +33,4 @@ influxd [command]
## Flags
| Flag | Description | Input type |
|:---- |:----------- | :--------: |
| `--assets-path` | Override default assets by serving from a specific directory (developer mode) | string |
| `--bolt-path` | Path to boltdb database (default `~/.influxdbv2/influxd.bolt`) | string |
| `--e2e-testing` | Add /debug/flush endpoint to clear stores; used for end-to-end tests (default `false`) | |
| `--engine-path` | Path to persistent engine files (default `~/.influxdbv2/engine`) | string |
| `-h`, `--help` | Help for the `influxd` command | |
| `--http-bind-address` | Bind address for the REST HTTP API (default `:9999`) | string |
| `--log-level` | Supported log levels are debug, info, and error (default `info`) | string |
| `--new-meta-store` | Enables the new meta store | |
| `--new-meta-store-read-only` | Toggle read-only mode for the new meta store and duplicate reads between old and new store (default `true`) | |
| `--no-tasks` | Disables the task scheduler | |
| `--reporting-disabled` | Disable sending telemetry data to **https:<nolink>//telemetry.influxdata.com** | |
| `--secret-store` | Data store for secrets (bolt or vault) (default `bolt`) | string |
| `--session-length` | TTL in minutes for newly created sessions (default `60`) | integer |
| `--session-renew-disabled` | Disables automatically extending session TTL on request | |
| `--store` | Data store for REST resources (bolt or memory) (default `bolt`) | string |
| `--tls-cert` | Path to TLS certificate file | string |
| `--tls-key` | Path to TLS private key file | string |
| `--tracing-type` | Supported tracing types (log or jaeger) | string |
| `--vault-addr ` | Address of the Vault server (example: `https://127.0.0.1:8200/`) | string |
| `--vault-cacert` | Path to a PEM-encoded CA certificate file | string |
| `--vault-capath` | Path to a directory of PEM-encoded CA certificate files | string |
| `--vault-client-cert` | Path to a PEM-encoded client certificate | string |
| `--vault-client-key` | Path to an unencrypted, PEM-encoded private key which corresponds to the matching client certificate | string |
| `--vault-max-retries` | Maximum number of retries when encountering a 5xx error code (default `2`) | integer |
| `--vault-client-timeout` | Vault client timeout (default `60s`) | duration |
| `--vault-skip-verify` | Skip certificate verification when communicating with Vault | |
| `--vault-tls-server-name` | Name to use as the SNI host when connecting to Vault via TLS | string |
| `--vault-token` | Vault authentication token | string |
{{% cli/influxd-flags %}}

1
content/v2.0/reference/cli/influxd/generate/_index.md
View File

@ -8,6 +8,7 @@ menu:
v2_0_ref:
parent: influxd
weight: 201
products: [oss]
---
The `influxd generate` command generates time series data direct to disk using a schema defined in a TOML file.

1
content/v2.0/reference/cli/influxd/generate/help-schema.md
View File

@ -8,6 +8,7 @@ menu:
v2_0_ref:
parent: influxd generate
weight: 301
products: [oss]
---
The `influxd generate help-schema` command outputs an example TOML schema to stdout that includes

1
content/v2.0/reference/cli/influxd/generate/simple.md
View File

@ -8,6 +8,7 @@ menu:
v2_0_ref:
parent: influxd generate
weight: 301
products: [oss]
---
The `influxd generate simple` command generates and writes a simple data set using

1
content/v2.0/reference/cli/influxd/inspect/_index.md
View File

@ -6,6 +6,7 @@ menu:
v2_0_ref:
parent: influxd
weight: 201
products: [oss]
---
The `influxd inspect` commands and subcommands inspecting on-disk InfluxDB time series data.

1
content/v2.0/reference/cli/influxd/inspect/build-tsi.md
View File

@ -8,6 +8,7 @@ menu:
v2_0_ref:
parent: influxd inspect
weight: 301
products: [oss]
---
The `influxd inspect build-tsi` command rebuilds the TSI index and, if necessary,

Some files were not shown because too many files have changed in this diff Show More