From be21841d7b9b544db4372064fb4342a67ba0551c Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Mon, 31 Aug 2020 13:47:22 -0600 Subject: [PATCH] Latest link fixes (#1375) * products should not use latest references to themselves * updated v2 links with influxdb namespace --- .../release-notes-changelog.md | 24 +++--- .../v1.6/administration/chrono-on-clusters.md | 2 +- .../v1.6/administration/config-options.md | 2 +- .../v1.6/administration/configuration.md | 6 +- .../administration/managing-influxdb-users.md | 4 +- .../administration/managing-organizations.md | 6 +- .../transition-web-admin-interface.md | 2 +- .../v1.6/administration/upgrading.md | 2 +- content/chronograf/v1.6/guides/_index.md | 2 +- .../guides/configuring-alert-endpoints.md | 6 +- .../v1.6/guides/create-a-dashboard.md | 10 +-- .../v1.6/guides/create-alert-rules.md | 8 +- .../monitoring-influxenterprise-clusters.md | 4 +- .../guides/using-precreated-dashboards.md | 4 +- .../chronograf/v1.6/introduction/_index.md | 6 +- .../v1.6/introduction/getting-started.md | 16 ++-- .../chronograf/v1.6/troubleshooting/_index.md | 2 +- .../frequently-asked-questions.md | 2 +- .../release-notes-changelog.md | 22 +++--- .../v1.7/administration/chrono-on-clusters.md | 2 +- .../v1.7/administration/config-options.md | 2 +- .../administration/creating-connections.md | 2 +- .../administration/managing-influxdb-users.md | 2 +- .../v1.7/administration/managing-security.md | 4 +- .../transition-web-admin-interface.md | 2 +- .../v1.7/administration/upgrading.md | 2 +- content/chronograf/v1.7/guides/_index.md | 2 +- .../guides/configuring-alert-endpoints.md | 4 +- .../v1.7/guides/create-a-dashboard.md | 10 +-- .../v1.7/guides/create-alert-rules.md | 8 +- .../monitoring-influxenterprise-clusters.md | 4 +- .../chronograf/v1.7/guides/querying-data.md | 4 +- .../guides/using-precreated-dashboards.md | 4 +- .../v1.7/guides/visualization-types.md | 2 +- .../chronograf/v1.7/introduction/_index.md | 6 +- .../v1.7/introduction/getting-started.md | 18 ++--- .../chronograf/v1.7/troubleshooting/_index.md | 2 +- .../frequently-asked-questions.md | 2 +- .../release-notes-changelog.md | 22 +++--- .../v1.8/administration/config-options.md | 2 +- .../administration/creating-connections.md | 2 +- .../administration/managing-influxdb-users.md | 2 +- .../v1.8/administration/managing-security.md | 4 +- .../guides/configuring-alert-endpoints.md | 4 +- .../v1.8/guides/create-a-dashboard.md | 10 +-- .../v1.8/guides/create-alert-rules.md | 8 +- .../monitoring-influxenterprise-clusters.md | 4 +- .../chronograf/v1.8/guides/querying-data.md | 4 +- .../guides/using-precreated-dashboards.md | 4 +- .../v1.8/introduction/getting-started.md | 18 ++--- .../chronograf/v1.8/troubleshooting/_index.md | 2 +- .../frequently-asked-questions.md | 2 +- .../v1.3/query_language/data_download.md | 2 +- .../v1.4/query_language/data_download.md | 2 +- .../v1.5/query_language/data_download.md | 2 +- .../v1.5/supported_protocols/_index.md | 10 +-- .../v1.5/supported_protocols/collectd.md | 2 +- .../v1.6/query_language/data_download.md | 2 +- .../v1.6/supported_protocols/_index.md | 10 +-- .../v1.6/supported_protocols/collectd.md | 2 +- content/influxdb/v1.7/_index.md | 2 +- content/influxdb/v1.7/flux/_index.md | 2 +- .../influxdb/v1.7/flux/get-started/_index.md | 2 +- .../v1.7/query_language/data_download.md | 2 +- .../v1.7/supported_protocols/collectd.md | 2 +- content/influxdb/v1.7/tools/api.md | 2 +- .../influxdb/v1.7/tools/influxd-cli/_index.md | 10 +-- content/influxdb/v1.8/flux/_index.md | 2 +- .../influxdb/v1.8/flux/get-started/_index.md | 2 +- .../v1.8/query_language/sample-data.md | 2 +- .../v1.8/supported_protocols/collectd.md | 2 +- content/influxdb/v1.8/tools/api.md | 2 +- content/influxdb/v1.8/tools/influxd/_index.md | 10 +-- .../v2.0/account-management/billing.md | 2 +- .../v2.0/account-management/data-usage.md | 4 +- .../v2.0/account-management/offboarding.md | 4 +- .../account-management/pricing-calculator.md | 2 +- .../v2.0/account-management/pricing-plans.md | 6 +- .../influxdb/v2.0/backup-restore/backup.md | 4 +- .../influxdb/v2.0/backup-restore/restore.md | 12 +-- .../v2.0/influxdb-templates/_index.md | 2 +- .../influxdb/v2.0/influxdb-templates/cloud.md | 12 +-- .../v2.0/influxdb-templates/create.md | 28 +++---- .../v2.0/influxdb-templates/stacks/_index.md | 4 +- .../v2.0/influxdb-templates/stacks/init.md | 12 +-- .../v2.0/influxdb-templates/stacks/remove.md | 4 +- .../v2.0/influxdb-templates/stacks/update.md | 6 +- .../v2.0/influxdb-templates/stacks/view.md | 4 +- .../influxdb/v2.0/influxdb-templates/use.md | 14 ++-- content/influxdb/v2.0/monitor-alert/_index.md | 14 ++-- .../v2.0/monitor-alert/checks/create.md | 6 +- .../v2.0/monitor-alert/checks/delete.md | 2 +- .../v2.0/monitor-alert/checks/update.md | 2 +- .../notification-endpoints/create.md | 2 +- .../notification-endpoints/delete.md | 2 +- .../notification-endpoints/update.md | 4 +- .../notification-rules/create.md | 4 +- .../templates/infrastructure/aws.md | 14 ++-- .../templates/infrastructure/docker.md | 32 ++++---- .../templates/infrastructure/vshpere.md | 22 +++--- .../templates/infrastructure/windows.md | 20 ++--- .../templates/networks/haproxy.md | 22 +++--- .../organizations/buckets/create-bucket.md | 2 +- .../organizations/buckets/delete-bucket.md | 2 +- .../organizations/buckets/update-bucket.md | 2 +- .../organizations/buckets/view-buckets.md | 4 +- .../influxdb/v2.0/organizations/create-org.md | 2 +- .../influxdb/v2.0/organizations/delete-org.md | 2 +- .../v2.0/organizations/members/add-member.md | 4 +- .../organizations/members/remove-member.md | 8 +- .../organizations/members/view-members.md | 2 +- .../influxdb/v2.0/organizations/update-org.md | 2 +- .../influxdb/v2.0/organizations/view-orgs.md | 4 +- .../common-tasks/downsample-data.md | 6 +- .../influxdb/v2.0/process-data/get-started.md | 12 +-- .../process-data/manage-tasks/create-task.md | 6 +- .../process-data/manage-tasks/update-task.md | 2 +- .../process-data/manage-tasks/view-tasks.md | 2 +- .../v2.0/query-data/execute-queries.md | 6 +- .../query-data/flux/calculate-percentages.md | 18 ++--- .../v2.0/query-data/flux/conditional-logic.md | 18 ++--- .../v2.0/query-data/flux/cumulativesum.md | 8 +- .../flux/custom-functions/_index.md | 6 +- .../flux/custom-functions/custom-aggregate.md | 18 ++--- .../influxdb/v2.0/query-data/flux/exists.md | 10 +-- .../v2.0/query-data/flux/explore-schema.md | 16 ++-- content/influxdb/v2.0/query-data/flux/fill.md | 8 +- .../v2.0/query-data/flux/first-last.md | 12 +-- .../v2.0/query-data/flux/geo/_index.md | 12 +-- .../query-data/flux/geo/filter-by-region.md | 4 +- .../query-data/flux/geo/group-geo-data.md | 8 +- .../query-data/flux/geo/shape-geo-data.md | 10 +-- .../v2.0/query-data/flux/group-data.md | 8 +- .../v2.0/query-data/flux/histograms.md | 16 ++-- .../influxdb/v2.0/query-data/flux/increase.md | 4 +- content/influxdb/v2.0/query-data/flux/join.md | 8 +- .../query-data/flux/manipulate-timestamps.md | 34 ++++----- .../query-data/flux/mathematic-operations.md | 22 +++--- .../influxdb/v2.0/query-data/flux/median.md | 12 +-- .../v2.0/query-data/flux/monitor-states.md | 12 +-- .../v2.0/query-data/flux/moving-average.md | 8 +- .../query-data/flux/percentile-quantile.md | 10 +-- .../v2.0/query-data/flux/query-fields.md | 16 ++-- content/influxdb/v2.0/query-data/flux/rate.md | 16 ++-- .../query-data/flux/regular-expressions.md | 4 +- .../v2.0/query-data/flux/scalar-values.md | 22 +++--- .../v2.0/query-data/flux/sort-limit.md | 18 ++--- content/influxdb/v2.0/query-data/flux/sql.md | 34 ++++----- .../v2.0/query-data/flux/window-aggregate.md | 16 ++-- .../v2.0/query-data/get-started/_index.md | 2 +- .../query-data/get-started/query-influxdb.md | 10 +-- .../query-data/get-started/syntax-basics.md | 4 +- .../query-data/get-started/transform-data.md | 26 +++---- content/influxdb/v2.0/query-data/influxql.md | 20 ++--- .../v2.0/query-data/optimize-queries.md | 28 +++---- content/influxdb/v2.0/reference/api/_index.md | 6 +- .../v2.0/reference/api/client-libraries/go.md | 8 +- .../v2.0/reference/api/client-libraries/js.md | 10 +-- .../reference/api/client-libraries/python.md | 8 +- .../v2.0/reference/api/influxdb-1x/_index.md | 4 +- .../v2.0/reference/api/influxdb-1x/dbrp.md | 12 +-- .../v2.0/reference/api/influxdb-1x/query.md | 18 ++--- .../v2.0/reference/api/influxdb-1x/write.md | 14 ++-- .../influxdb/v2.0/reference/api/postman.md | 4 +- .../v2.0/reference/cli/influx/_index.md | 44 +++++------ .../v2.0/reference/cli/influx/apply/_index.md | 2 +- .../v2.0/reference/cli/influx/auth/_index.md | 10 +-- .../reference/cli/influx/bucket/_index.md | 8 +- .../reference/cli/influx/config/_index.md | 8 +- .../reference/cli/influx/delete/_index.md | 6 +- .../reference/cli/influx/export/_index.md | 6 +- .../v2.0/reference/cli/influx/export/all.md | 2 +- .../v2.0/reference/cli/influx/org/_index.md | 10 +-- .../cli/influx/org/members/_index.md | 6 +- .../v2.0/reference/cli/influx/repl/_index.md | 2 +- .../reference/cli/influx/secret/_index.md | 6 +- .../reference/cli/influx/stacks/_index.md | 4 +- .../v2.0/reference/cli/influx/task/_index.md | 12 +-- .../reference/cli/influx/task/log/_index.md | 2 +- .../reference/cli/influx/task/run/_index.md | 4 +- .../reference/cli/influx/telegrafs/_index.md | 6 +- .../reference/cli/influx/template/_index.md | 2 +- .../v2.0/reference/cli/influx/user/_index.md | 10 +-- .../v2.0/reference/cli/influx/write/_index.md | 6 +- .../v2.0/reference/cli/influx/write/dryrun.md | 4 +- .../v2.0/reference/cli/influxd/_index.md | 12 +-- .../reference/cli/influxd/generate/_index.md | 4 +- .../cli/influxd/generate/help-schema.md | 2 +- .../reference/cli/influxd/inspect/_index.md | 22 +++--- .../influxd/inspect/compact-series-file.md | 2 +- .../v2.0/reference/cli/influxd/restore.md | 6 +- .../v2.0/reference/cli/influxd/run.md | 2 +- .../influxdb/v2.0/reference/config-options.md | 6 +- .../reference/flux/language/expressions.md | 2 +- .../v2.0/reference/flux/language/operators.md | 2 +- .../flux/language/string-interpolation.md | 8 +- .../v2.0/reference/flux/language/types.md | 4 +- .../flux/stdlib/built-in/inputs/from.md | 6 +- .../flux/stdlib/built-in/misc/intervals.md | 2 +- .../flux/stdlib/built-in/misc/linearbins.md | 2 +- .../stdlib/built-in/misc/logarithmicbins.md | 2 +- .../flux/stdlib/built-in/misc/now.md | 2 +- .../flux/stdlib/built-in/outputs/to.md | 2 +- .../transformations/aggregates/_index.md | 14 ++-- .../aggregates/aggregatewindow.md | 8 +- .../transformations/aggregates/count.md | 6 +- .../transformations/aggregates/median.md | 6 +- .../transformations/aggregates/reduce.md | 4 +- .../built-in/transformations/doubleema.md | 4 +- .../stdlib/built-in/transformations/drop.md | 2 +- .../stdlib/built-in/transformations/filter.md | 2 +- .../stdlib/built-in/transformations/group.md | 2 +- .../built-in/transformations/histogram.md | 4 +- .../built-in/transformations/holtwinters.md | 8 +- .../stdlib/built-in/transformations/join.md | 2 +- .../stdlib/built-in/transformations/keep.md | 4 +- .../built-in/transformations/keyvalues.md | 2 +- .../stdlib/built-in/transformations/map.md | 2 +- .../stdlib/built-in/transformations/range.md | 2 +- .../stdlib/built-in/transformations/rename.md | 2 +- .../transformations/selectors/_index.md | 4 +- .../built-in/transformations/statecount.md | 2 +- .../built-in/transformations/stateduration.md | 2 +- .../transformations/stream-table/getcolumn.md | 2 +- .../transformations/stream-table/getrecord.md | 2 +- .../transformations/stream-table/tablefind.md | 6 +- .../built-in/transformations/tripleema.md | 6 +- .../tripleexponentialderivative.md | 2 +- .../type-conversions/duration.md | 2 +- .../type-conversions/tobool.md | 4 +- .../type-conversions/toduration.md | 4 +- .../type-conversions/tofloat.md | 4 +- .../transformations/type-conversions/toint.md | 4 +- .../type-conversions/tostring.md | 4 +- .../type-conversions/totime.md | 4 +- .../type-conversions/touint.md | 4 +- .../stdlib/built-in/transformations/union.md | 2 +- .../stdlib/built-in/transformations/window.md | 2 +- .../flux/stdlib/contrib/discord/endpoint.md | 2 +- .../flux/stdlib/contrib/influxdb/select.md | 4 +- .../reference/flux/stdlib/contrib/rows/map.md | 6 +- .../flux/stdlib/contrib/teams/endpoint.md | 2 +- .../flux/stdlib/contrib/telegram/endpoint.md | 4 +- .../flux/stdlib/contrib/telegram/message.md | 2 +- .../v2.0/reference/flux/stdlib/csv/from.md | 4 +- .../stdlib/experimental/aggregate/rate.md | 12 +-- .../flux/stdlib/experimental/bigtable/from.md | 2 +- .../flux/stdlib/experimental/chain.md | 2 +- .../flux/stdlib/experimental/csv/from.md | 4 +- .../flux/stdlib/experimental/geo/_index.md | 4 +- .../stdlib/experimental/geo/filterrows.md | 10 +-- .../stdlib/experimental/geo/gridfilter.md | 10 +-- .../flux/stdlib/experimental/geo/shapedata.md | 2 +- .../stdlib/experimental/geo/st_contains.md | 4 +- .../stdlib/experimental/geo/st_distance.md | 6 +- .../stdlib/experimental/geo/st_dwithin.md | 6 +- .../stdlib/experimental/geo/st_intersects.md | 4 +- .../flux/stdlib/experimental/geo/st_length.md | 4 +- .../stdlib/experimental/geo/st_linestring.md | 4 +- .../stdlib/experimental/geo/strictfilter.md | 6 +- .../flux/stdlib/experimental/group.md | 4 +- .../flux/stdlib/experimental/join.md | 8 +- .../flux/stdlib/experimental/query/_index.md | 2 +- .../stdlib/experimental/query/filterfields.md | 6 +- .../experimental/query/filtermeasurement.md | 2 +- .../stdlib/experimental/query/fromrange.md | 4 +- .../stdlib/experimental/query/inbucket.md | 8 +- .../reference/flux/stdlib/experimental/set.md | 2 +- .../reference/flux/stdlib/experimental/to.md | 4 +- .../reference/flux/stdlib/http/endpoint.md | 2 +- .../flux/stdlib/influxdb-v1/fieldkeys.md | 2 +- .../flux/stdlib/influxdb-v1/fieldsascols.md | 2 +- .../influxdb-v1/measurementfieldkeys.md | 2 +- .../flux/stdlib/influxdb-v1/measurements.md | 2 +- .../stdlib/influxdb-v1/measurementtagkeys.md | 2 +- .../influxdb-v1/measurementtagvalues.md | 2 +- .../flux/stdlib/influxdb-v1/tagkeys.md | 12 +-- .../flux/stdlib/influxdb-v1/tagvalues.md | 12 +-- .../v2.0/reference/flux/stdlib/json/encode.md | 4 +- .../v2.0/reference/flux/stdlib/math/ldexp.md | 2 +- .../reference/flux/stdlib/monitor/from.md | 2 +- .../reference/flux/stdlib/monitor/logs.md | 2 +- .../flux/stdlib/pagerduty/endpoint.md | 2 +- .../flux/stdlib/pagerduty/sendevent.md | 4 +- .../flux/stdlib/pushbullet/endpoint.md | 2 +- .../v2.0/reference/flux/stdlib/secrets/get.md | 2 +- .../reference/flux/stdlib/slack/endpoint.md | 2 +- .../v2.0/reference/flux/stdlib/sql/from.md | 2 +- .../v2.0/reference/flux/stdlib/sql/to.md | 2 +- .../v2.0/reference/flux/stdlib/system/time.md | 2 +- .../flux/stdlib/testing/assertempty.md | 2 +- content/influxdb/v2.0/reference/glossary.md | 64 ++++++++-------- .../reference/internals/storage-engine.md | 6 +- .../reference/key-concepts/data-elements.md | 20 ++--- .../reference/key-concepts/data-schema.md | 10 +-- .../key-concepts/design-principles.md | 2 +- .../v2.0/reference/release-notes/flux.md | 48 ++++++------ .../reference/release-notes/influxdb-cloud.md | 8 +- .../v2.0/reference/release-notes/influxdb.md | 16 ++-- .../influxdb/v2.0/reference/sample-data.md | 8 +- .../reference/syntax/annotated-csv/_index.md | 12 +-- .../syntax/annotated-csv/extended.md | 40 +++++----- .../v2.0/reference/syntax/delete-predicate.md | 6 +- .../influxdb/v2.0/reference/syntax/flux.md | 6 +- .../v2.0/reference/syntax/line-protocol.md | 6 +- content/influxdb/v2.0/reference/urls.md | 6 +- .../influxdb/v2.0/security/secrets/_index.md | 4 +- .../security/secrets/manage-secrets/_index.md | 4 +- .../security/secrets/manage-secrets/add.md | 6 +- .../security/secrets/manage-secrets/delete.md | 6 +- .../security/secrets/manage-secrets/update.md | 6 +- .../security/secrets/manage-secrets/view.md | 6 +- .../v2.0/security/secrets/use-vault.md | 14 ++-- .../v2.0/security/tokens/create-token.md | 6 +- .../v2.0/security/tokens/delete-token.md | 2 +- .../v2.0/security/tokens/view-tokens.md | 4 +- .../influxdb/v2.0/telegraf-configs/_index.md | 2 +- .../influxdb/v2.0/telegraf-configs/create.md | 14 ++-- .../influxdb/v2.0/telegraf-configs/remove.md | 6 +- .../influxdb/v2.0/telegraf-configs/update.md | 8 +- .../influxdb/v2.0/telegraf-configs/view.md | 6 +- content/influxdb/v2.0/tools/repl.md | 2 +- content/influxdb/v2.0/users/_index.md | 4 +- .../influxdb/v2.0/users/change-password.md | 2 +- content/influxdb/v2.0/users/create-user.md | 6 +- content/influxdb/v2.0/users/delete-user.md | 4 +- content/influxdb/v2.0/users/update-user.md | 2 +- content/influxdb/v2.0/users/view-users.md | 4 +- .../v2.0/visualize-data/dashboards/_index.md | 2 +- .../visualize-data/dashboards/_index.md~HEAD | 2 +- .../dashboards/control-dashboard.md | 4 +- .../dashboards/create-dashboard.md | 4 +- .../v2.0/visualize-data/explore-metrics.md | 8 +- .../visualize-data/other-tools/grafana.md | 20 ++--- .../templates/create-template.md | 2 +- .../visualize-data/templates/use-template.md | 2 +- .../visualize-data/templates/view-template.md | 74 +++++++++---------- .../v2.0/visualize-data/variables/_index.md | 6 +- .../variables/common-variables.md | 30 ++++---- .../variables/create-variable.md | 12 +-- .../variables/variable-types.md | 10 +-- .../visualization-types/heatmap.md | 6 +- .../visualization-types/histogram.md | 2 +- .../visualization-types/scatter.md | 6 +- .../visualization-types/table.md | 2 +- content/influxdb/v2.0/write-data/_index.md | 46 ++++++------ .../best-practices/duplicate-points.md | 2 +- .../best-practices/optimize-writes.md | 12 +-- .../v2.0/write-data/developer-tools/api.md | 4 +- .../developer-tools/client-libraries.md | 2 +- .../v2.0/write-data/developer-tools/csv.md | 38 +++++----- .../write-data/developer-tools/influx-cli.md | 4 +- .../manage-scrapers/update-a-scraper.md | 2 +- .../write-data/no-code/use-telegraf/_index.md | 2 +- .../no-code/use-telegraf/auto-config.md | 12 +-- .../no-code/use-telegraf/manual-config.md | 20 ++--- .../use-telegraf-plugins/use-http-plugin.md | 2 +- .../releasenotes-changelog.md | 4 +- .../v1.4/guides/continuous_queries.md | 2 +- .../v1.4/guides/event-handler-setup.md | 6 +- .../v1.4/introduction/getting-started.md | 2 +- content/kapacitor/v1.4/nodes/alert_node.md | 10 +-- content/kapacitor/v1.4/nodes/from_node.md | 4 +- content/kapacitor/v1.4/working/api.md | 2 +- .../releasenotes-changelog.md | 4 +- .../v1.5/guides/continuous_queries.md | 2 +- .../v1.5/guides/event-handler-setup.md | 6 +- .../v1.5/guides/two-measurement-alert.md | 2 +- content/kapacitor/v1.5/nodes/alert_node.md | 2 +- content/kapacitor/v1.5/nodes/from_node.md | 4 +- content/kapacitor/v1.5/nodes/join_node.md | 2 +- content/kapacitor/v1.5/working/api.md | 2 +- 372 files changed, 1326 insertions(+), 1326 deletions(-) diff --git a/content/chronograf/v1.6/about_the_project/release-notes-changelog.md b/content/chronograf/v1.6/about_the_project/release-notes-changelog.md index b03e2d284..aae0232a0 100644 --- a/content/chronograf/v1.6/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.6/about_the_project/release-notes-changelog.md @@ -615,9 +615,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#bar) option added to dashboard + * [Bar graph](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#bar) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -633,7 +633,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/#writing-data) + * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.6/guides/transition-web-admin-interface/#writing-data) ### UI improvements @@ -653,26 +653,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.6/administration/configuration/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support) * Add a query for windows uptime - thank you, @brianbaker! ### Features - * Add log [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick! + * Add log [event handler](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) dropdowns + * Add autocomplete functionality to [template variable](/chronograf/v1.6/guides/dashboard-template-variables/) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) manager more space efficient + * Make the [template variables](/chronograf/v1.6/guides/dashboard-template-variables/) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -682,25 +682,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/chronograf/v1.6/administration/configuration/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.6/administration/configuration/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) visualization type + * Show legend on [Line+Stat](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#line-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxDB Enterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.6/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.6/administration/chrono-on-clusters.md b/content/chronograf/v1.6/administration/chrono-on-clusters.md index bda55c88d..264fcf105 100644 --- a/content/chronograf/v1.6/administration/chrono-on-clusters.md +++ b/content/chronograf/v1.6/administration/chrono-on-clusters.md @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/). +For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/). diff --git a/content/chronograf/v1.6/administration/config-options.md b/content/chronograf/v1.6/administration/config-options.md index 5a3b9ade9..e8d33659e 100644 --- a/content/chronograf/v1.6/administration/config-options.md +++ b/content/chronograf/v1.6/administration/config-options.md @@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) files. +The path to the directory of [canned dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.6/administration/configuration.md b/content/chronograf/v1.6/administration/configuration.md index e7741ae8b..3fa30e00d 100644 --- a/content/chronograf/v1.6/administration/configuration.md +++ b/content/chronograf/v1.6/administration/configuration.md @@ -47,12 +47,12 @@ It is neither created nor used in macOS. ## Enabling security, multi-organization, and multi-user support -See [Managing security](/{{< latest "chronograf" >}}/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols. +See [Managing security](/chronograf/v1.6/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols. After you configure OAuth 2.0 authentication in Chronograf, you can use the multi-organization and multi-user support described in detail here: -* [Managing organizations](/{{< latest "chronograf" >}}/administration/managing-organizations) -* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users) +* [Managing organizations](/chronograf/v1.6/administration/managing-organizations) +* [Managing Chronograf users](/chronograf/v1.6/administration/managing-chronograf-users) diff --git a/content/chronograf/v1.6/administration/managing-influxdb-users.md b/content/chronograf/v1.6/administration/managing-influxdb-users.md index 8948867e6..097aa534b 100644 --- a/content/chronograf/v1.6/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.6/administration/managing-influxdb-users.md @@ -13,7 +13,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.6/administration/managing-security/). **On this page:** @@ -77,7 +77,7 @@ A successful `CREATE USER` query returns a blank result: ### Step 4: Edit the InfluxDB source in Chronograf. -If you've already [connected your database to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password. +If you've already [connected your database to Chronograf](/chronograf/v1.6/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password. Edit existing InfluxDB database sources by navigating to the Chronograf configuration page and clicking on the name of the source. ## InfluxDB OSS User Management diff --git a/content/chronograf/v1.6/administration/managing-organizations.md b/content/chronograf/v1.6/administration/managing-organizations.md index 52c76ab81..05575d2ec 100644 --- a/content/chronograf/v1.6/administration/managing-organizations.md +++ b/content/chronograf/v1.6/administration/managing-organizations.md @@ -22,7 +22,7 @@ menu: > ***Note:*** Support for organizations and distinct users with role-based access control is new in Chronograf 1.4. > -> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/). +> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.6/administration/managing-chronograf-users/). A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations. @@ -67,8 +67,8 @@ You can configure existing and new organizations in the **Organizations** tab of See the following pages for more information about managing Chronograf users and security: -* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) -* [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/) +* [Managing Chronograf users](/chronograf/v1.6/administration/managing-chronograf-users/) +* [Managing security](/chronograf/v1.6/administration/managing-security/) ## Mapping organizations diff --git a/content/chronograf/v1.6/administration/transition-web-admin-interface.md b/content/chronograf/v1.6/administration/transition-web-admin-interface.md index 043283212..1abb51bbf 100644 --- a/content/chronograf/v1.6/administration/transition-web-admin-interface.md +++ b/content/chronograf/v1.6/administration/transition-web-admin-interface.md @@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma ### Chronograf In Chronograf, the `Admin` page includes a complete interface for user management. -The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/{{< latest "chronograf" >}}/administration/user-management/) page for more information. +The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/chronograf/v1.6/administration/user-management/) page for more information. The `Admin` page allows users to: * View, create, and delete users diff --git a/content/chronograf/v1.6/administration/upgrading.md b/content/chronograf/v1.6/administration/upgrading.md index 522619336..08f70e393 100644 --- a/content/chronograf/v1.6/administration/upgrading.md +++ b/content/chronograf/v1.6/administration/upgrading.md @@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix. InfluxData recommends migrating to the open source Chronograf product. -See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running! +See [Getting Started](/chronograf/v1.6/introduction/getting-started/) to get up and running! diff --git a/content/chronograf/v1.6/guides/_index.md b/content/chronograf/v1.6/guides/_index.md index 5abc7167a..4625d09c0 100644 --- a/content/chronograf/v1.6/guides/_index.md +++ b/content/chronograf/v1.6/guides/_index.md @@ -17,7 +17,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts. -## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) +## [Creating dashboards](/chronograf/v1.6/guides/create-a-dashboard/) Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. Learn how to create customized dashboards in Chronograf. diff --git a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md index efae94b5a..10b530115 100644 --- a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md @@ -38,7 +38,7 @@ Chronograf supports the following event handlers: * TCP * VictorOps -To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/chronograf/v1.6/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/chronograf/v1.6/introduction/getting-started/#4-connect-chronograf-to-kapacitor). The **Configure Kapacitor** page includes the event handler configuration options. @@ -46,10 +46,10 @@ The **Configure Kapacitor** page includes the event handler configuration option Alert endpoint configurations appear on the Chronograf Configure Kapacitor page. You must have a connected Kapacitor instance to access the configurations. -For more information, see [Kapacitor installation instructions](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf. +For more information, see [Kapacitor installation instructions](/chronograf/v1.6/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/chronograf/v1.6/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.6/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat diff --git a/content/chronograf/v1.6/guides/create-a-dashboard.md b/content/chronograf/v1.6/guides/create-a-dashboard.md index 4e766aa47..39949eee4 100644 --- a/content/chronograf/v1.6/guides/create-a-dashboard.md +++ b/content/chronograf/v1.6/guides/create-a-dashboard.md @@ -9,7 +9,7 @@ menu: --- Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. -Use Chronograf's [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements. +Use Chronograf's [pre-created dashboards](/chronograf/v1.6/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements. This guide shows you how to create custom Chronograf dashboards. By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example: @@ -20,7 +20,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). +For more information, see [Configuring Chronograf](/chronograf/v1.6/administration/configuration). ## Build a Dashboard @@ -55,7 +55,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/chronograf/v1.6/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -77,7 +77,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > Note: -These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support). +These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support). #### Configure dashboard-wide settings: * You can change the dashboard's *auto-refresh interval* at the top of the page - the default interval selected is **Every 15 seconds**. @@ -93,4 +93,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/chronograf/v1.6/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.6/guides/create-alert-rules.md b/content/chronograf/v1.6/guides/create-alert-rules.md index 0b773cf0e..a1b5949b7 100644 --- a/content/chronograf/v1.6/guides/create-alert-rules.md +++ b/content/chronograf/v1.6/guides/create-alert-rules.md @@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/chronograf/v1.6/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/chronograf/v1.6/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/chronograf/v1.6/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configuring Chronograf alert rules diff --git a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md index 42f0e8c04..a36d25602 100644 --- a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md @@ -23,7 +23,7 @@ See the InfluxDB Enterprise documentation for This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/chronograf/v1.6/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.6/guides/using-precreated-dashboards.md b/content/chronograf/v1.6/guides/using-precreated-dashboards.md index f8bb28236..1534ecd61 100644 --- a/content/chronograf/v1.6/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.6/guides/using-precreated-dashboards.md @@ -11,7 +11,7 @@ menu: ## Overview -Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). +Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/chronograf/v1.6/guides/create-a-dashboard/). > Note that these pre-created dashboards do not appear in the Dashboards tab, which only include custom dashboards that your organization has created. @@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files. -The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page. +The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/v1.6/administration/config-options/#) page. You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf). See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details. diff --git a/content/chronograf/v1.6/introduction/_index.md b/content/chronograf/v1.6/introduction/_index.md index 3028b85b3..e7157118a 100644 --- a/content/chronograf/v1.6/introduction/_index.md +++ b/content/chronograf/v1.6/introduction/_index.md @@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf: Chronograf is supported on several operating systems and hardware architectures. See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries. -## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) +## [Installing Chronograf](/chronograf/v1.6/introduction/installation/) -[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. +[Installing Chronograf](/chronograf/v1.6/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. ## Getting Started -[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. +[Getting started with Chronograf](/chronograf/v1.6/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. By the end of the guide, you will have downloaded, installed, and configured all four packages of the TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure. diff --git a/content/chronograf/v1.6/introduction/getting-started.md b/content/chronograf/v1.6/introduction/getting-started.md index 528f528be..930ee184f 100644 --- a/content/chronograf/v1.6/introduction/getting-started.md +++ b/content/chronograf/v1.6/introduction/getting-started.md @@ -10,18 +10,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/v1.6/introduction/installation), get started with key features using the guides below. ### Data visualization * Investigate your data by building queries using [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/). -* Use pre-created [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). +* Use pre-created [pre-created dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.6/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/chronograf/v1.6/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/chronograf/v1.6/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/chronograf/v1.6/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/chronograf/v1.6/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.6/troubleshooting/_index.md b/content/chronograf/v1.6/troubleshooting/_index.md index 85c191d78..86ac0e9ab 100644 --- a/content/chronograf/v1.6/troubleshooting/_index.md +++ b/content/chronograf/v1.6/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/chronograf/v1.6/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md index 4316d442b..3b1574662 100644 --- a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/chronograf/v1.7/about_the_project/release-notes-changelog.md b/content/chronograf/v1.7/about_the_project/release-notes-changelog.md index 825dc3bc7..42d8f438e 100644 --- a/content/chronograf/v1.7/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.7/about_the_project/release-notes-changelog.md @@ -836,9 +836,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard + * [Bar graph](/chronograf/v1.7/guides/visualization-types/#bar-graph) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/chronograf/v1.7/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -854,7 +854,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/) + * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.7/guides/querying-data/) ### UI improvements @@ -874,26 +874,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.7/administration/config-options/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/v1.7/guides/visualization-types) * Add a query for windows uptime - thank you, @brianbaker! ### Features * Add log event handler- thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns + * Add autocomplete functionality to [template variable](/chronograf/v1.7/guides/dashboard-template-variables) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient + * Make the [template variables](/chronograf/v1.7/guides/dashboard-template-variables) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -903,25 +903,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/chronograf/v1.7/administration/config-options/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.7/administration/config-options/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type + * Show legend on [Line+Stat](/chronograf/v1.7/guides/visualization-types/#line-graph-single-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.7/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.7/administration/chrono-on-clusters.md b/content/chronograf/v1.7/administration/chrono-on-clusters.md index cec4d2bb4..22e93e47b 100644 --- a/content/chronograf/v1.7/administration/chrono-on-clusters.md +++ b/content/chronograf/v1.7/administration/chrono-on-clusters.md @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters). +For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters). diff --git a/content/chronograf/v1.7/administration/config-options.md b/content/chronograf/v1.7/administration/config-options.md index 91c94505d..36bcddab6 100644 --- a/content/chronograf/v1.7/administration/config-options.md +++ b/content/chronograf/v1.7/administration/config-options.md @@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files. +The path to the directory of [canned dashboards](/chronograf/v1.7/guides/using-precreated-dashboards) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.7/administration/creating-connections.md b/content/chronograf/v1.7/administration/creating-connections.md index d0904a063..b84874b82 100644 --- a/content/chronograf/v1.7/administration/creating-connections.md +++ b/content/chronograf/v1.7/administration/creating-connections.md @@ -39,7 +39,7 @@ To create an InfluxDB connection in the Chronograf UI: * **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched. 4. Click **Add Connection** - * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard). + * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/v1.7/guides/create-a-dashboard). * If the connection cannot be created, the following error message appears: "Unable to create source: Error contacting source." If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible. diff --git a/content/chronograf/v1.7/administration/managing-influxdb-users.md b/content/chronograf/v1.7/administration/managing-influxdb-users.md index 72269d909..720cf0e7d 100644 --- a/content/chronograf/v1.7/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.7/administration/managing-influxdb-users.md @@ -13,7 +13,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.7/administration/managing-security/). **On this page:** diff --git a/content/chronograf/v1.7/administration/managing-security.md b/content/chronograf/v1.7/administration/managing-security.md index 466b37a1a..d8b5e12eb 100644 --- a/content/chronograf/v1.7/administration/managing-security.md +++ b/content/chronograf/v1.7/administration/managing-security.md @@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA ## Configure OAuth 2.0 > After configuring OAuth 2.0, the Chronograf Admin tab becomes visible. -> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/) -> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/). +> You can then set up [multiple organizations](/chronograf/v1.7/administration/managing-organizations/) +> and [users](/chronograf/v1.7/administration/managing-influxdb-users/). Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls. diff --git a/content/chronograf/v1.7/administration/transition-web-admin-interface.md b/content/chronograf/v1.7/administration/transition-web-admin-interface.md index ab9d9ba13..bbea6d635 100644 --- a/content/chronograf/v1.7/administration/transition-web-admin-interface.md +++ b/content/chronograf/v1.7/administration/transition-web-admin-interface.md @@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma ### Chronograf In Chronograf, the `Admin` page includes a complete interface for user management. -The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) page for more information. +The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/chronograf/v1.7/administration/managing-chronograf-users/) page for more information. The `Admin` page allows users to: * View, create, and delete users diff --git a/content/chronograf/v1.7/administration/upgrading.md b/content/chronograf/v1.7/administration/upgrading.md index ff9141d8a..91ebe742d 100644 --- a/content/chronograf/v1.7/administration/upgrading.md +++ b/content/chronograf/v1.7/administration/upgrading.md @@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix. InfluxData recommends migrating to the open source Chronograf product. -See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running! +See [Getting Started](/chronograf/v1.7/introduction/getting-started/) to get up and running! diff --git a/content/chronograf/v1.7/guides/_index.md b/content/chronograf/v1.7/guides/_index.md index 20a8bb473..9d36a3650 100644 --- a/content/chronograf/v1.7/guides/_index.md +++ b/content/chronograf/v1.7/guides/_index.md @@ -22,7 +22,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts. -## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) +## [Creating dashboards](/chronograf/v1.7/guides/create-a-dashboard/) Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. Learn how to create customized dashboards in Chronograf. diff --git a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md index 26f3d88bf..f61a9b780 100644 --- a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md @@ -50,7 +50,7 @@ You must have a connected Kapacitor instance to access the configurations. For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.7/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat @@ -87,7 +87,7 @@ The following steps describe how to create the API access token: Your token appears in the table just above the **Create new token** section: -![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png) +![HipChat token](/img/chronograf/1-6-g-eventhandlers-hipchattoken.png) ### Kafka diff --git a/content/chronograf/v1.7/guides/create-a-dashboard.md b/content/chronograf/v1.7/guides/create-a-dashboard.md index c6e0f8f46..97e3f82e8 100644 --- a/content/chronograf/v1.7/guides/create-a-dashboard.md +++ b/content/chronograf/v1.7/guides/create-a-dashboard.md @@ -10,7 +10,7 @@ menu: Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure: -* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. +* View [pre-created dashboards](/chronograf/v1.7/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. * Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard). * Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details. @@ -23,7 +23,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). +For more information, see [Configuring Chronograf](/chronograf/v1.7/administration/configuration). ## Build a Dashboard @@ -58,7 +58,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/chronograf/v1.7/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -80,7 +80,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > **Note:** - These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). + These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/v1.7/guides/visualization-types/). #### Configure dashboard-wide settings: * Change the dashboard's *selected time* at the top of the page - the default time is **Local**, which uses your browser's local time. Select **UTC** to use Coordinated Universal Time. @@ -119,4 +119,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/chronograf/v1.7/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.7/guides/create-alert-rules.md b/content/chronograf/v1.7/guides/create-alert-rules.md index 219fa132f..c451b4432 100644 --- a/content/chronograf/v1.7/guides/create-alert-rules.md +++ b/content/chronograf/v1.7/guides/create-alert-rules.md @@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/chronograf/v1.7/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/chronograf/v1.7/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/chronograf/v1.7/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/chronograf/v1.7/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configuring Chronograf alert rules diff --git a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md index 6712b1198..e2c243583 100644 --- a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md @@ -23,7 +23,7 @@ See the InfluxEnterprise documentation for This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.7/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/chronograf/v1.7/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.7/guides/querying-data.md b/content/chronograf/v1.7/guides/querying-data.md index cc22f8a98..d5e105b06 100644 --- a/content/chronograf/v1.7/guides/querying-data.md +++ b/content/chronograf/v1.7/guides/querying-data.md @@ -7,7 +7,7 @@ menu: weight: 130 parent: Guides --- -Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query. +Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/v1.7/guides/visualization-types/) for your query. To open the **Data Explorer**, click the **Explore** icon in the navigation bar: @@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin ## Visualize your query -Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/). +Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/v1.7/guides/visualization-types/). ## Add queries to dashboards diff --git a/content/chronograf/v1.7/guides/using-precreated-dashboards.md b/content/chronograf/v1.7/guides/using-precreated-dashboards.md index c8e1fbf9c..bbb88a026 100644 --- a/content/chronograf/v1.7/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.7/guides/using-precreated-dashboards.md @@ -13,7 +13,7 @@ menu: Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. -> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates). +> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/v1.7/guides/create-a-dashboard/#dashboard-templates). ## Requirements @@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files. -The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page. +The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/v1.7/administration/config-options/#) page. You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf). See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details. diff --git a/content/chronograf/v1.7/guides/visualization-types.md b/content/chronograf/v1.7/guides/visualization-types.md index 592a1a1d9..5d415cb9a 100644 --- a/content/chronograf/v1.7/guides/visualization-types.md +++ b/content/chronograf/v1.7/guides/visualization-types.md @@ -8,7 +8,7 @@ menu: parent: Guides --- -Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/{{< latest "chronograf" >}}/querying-data) . +Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/chronograf/v1.7/querying-data) . [Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png) diff --git a/content/chronograf/v1.7/introduction/_index.md b/content/chronograf/v1.7/introduction/_index.md index cd2b2f236..e4897dd7c 100644 --- a/content/chronograf/v1.7/introduction/_index.md +++ b/content/chronograf/v1.7/introduction/_index.md @@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf: Chronograf is supported on several operating systems and hardware architectures. See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries. -## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) +## [Installing Chronograf](/chronograf/v1.7/introduction/installation/) -[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. +[Installing Chronograf](/chronograf/v1.7/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. ## Getting Started -[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. +[Getting started with Chronograf](/chronograf/v1.7/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. By the end of the guide, you will have downloaded, installed, and configured all four packages of the TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure. diff --git a/content/chronograf/v1.7/introduction/getting-started.md b/content/chronograf/v1.7/introduction/getting-started.md index 34905e772..a845bda80 100644 --- a/content/chronograf/v1.7/introduction/getting-started.md +++ b/content/chronograf/v1.7/introduction/getting-started.md @@ -10,18 +10,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/v1.7/introduction/installation), get started with key features using the guides below. ### Data visualization -* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/). -* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). +* Investigate your data by building queries using the [Data Explorer](/chronograf/v1.7/guides/querying-data/). +* Use [pre-created dashboards](/chronograf/v1.7/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.7/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/chronograf/v1.7/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/chronograf/v1.7/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/chronograf/v1.7/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/chronograf/v1.7/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/chronograf/v1.7/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.7/troubleshooting/_index.md b/content/chronograf/v1.7/troubleshooting/_index.md index 637a53ec4..0577c6d30 100644 --- a/content/chronograf/v1.7/troubleshooting/_index.md +++ b/content/chronograf/v1.7/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/chronograf/v1.7/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md index 9d4bdfb9a..da7fa6fda 100644 --- a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/chronograf/v1.8/about_the_project/release-notes-changelog.md b/content/chronograf/v1.8/about_the_project/release-notes-changelog.md index b676c3d1e..1129bc863 100644 --- a/content/chronograf/v1.8/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.8/about_the_project/release-notes-changelog.md @@ -935,9 +935,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard + * [Bar graph](/chronograf/v1.8/guides/visualization-types/#bar-graph) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/chronograf/v1.8/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -953,7 +953,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/) + * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.8/guides/querying-data/) ### UI improvements @@ -973,26 +973,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.8/administration/config-options/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/v1.8/guides/visualization-types) * Add a query for windows uptime - thank you, @brianbaker! ### Features * Add log event handler- thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns + * Add autocomplete functionality to [template variable](/chronograf/v1.8/guides/dashboard-template-variables) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient + * Make the [template variables](/chronograf/v1.8/guides/dashboard-template-variables) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -1002,25 +1002,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/chronograf/v1.8/administration/config-options/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.8/administration/config-options/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type + * Show legend on [Line+Stat](/chronograf/v1.8/guides/visualization-types/#line-graph-single-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.8/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.8/administration/config-options.md b/content/chronograf/v1.8/administration/config-options.md index a2118fccd..0ddf5ce1a 100644 --- a/content/chronograf/v1.8/administration/config-options.md +++ b/content/chronograf/v1.8/administration/config-options.md @@ -95,7 +95,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files. +The path to the directory of [canned dashboards](/chronograf/v1.8/guides/using-precreated-dashboards) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.8/administration/creating-connections.md b/content/chronograf/v1.8/administration/creating-connections.md index 972caf1d1..dbf6248d6 100644 --- a/content/chronograf/v1.8/administration/creating-connections.md +++ b/content/chronograf/v1.8/administration/creating-connections.md @@ -39,7 +39,7 @@ To create an InfluxDB connection in the Chronograf UI: * **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched. 4. Click **Add Connection** - * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard). + * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/v1.8/guides/create-a-dashboard). * If the connection cannot be created, the following error message appears: "Unable to create source: Error contacting source." If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible. diff --git a/content/chronograf/v1.8/administration/managing-influxdb-users.md b/content/chronograf/v1.8/administration/managing-influxdb-users.md index 4fb98bc4f..ed3e41383 100644 --- a/content/chronograf/v1.8/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.8/administration/managing-influxdb-users.md @@ -14,7 +14,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.8/administration/managing-security/). **On this page:** diff --git a/content/chronograf/v1.8/administration/managing-security.md b/content/chronograf/v1.8/administration/managing-security.md index b4b7ee735..8bfae35a5 100644 --- a/content/chronograf/v1.8/administration/managing-security.md +++ b/content/chronograf/v1.8/administration/managing-security.md @@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA ## Configure OAuth 2.0 > After configuring OAuth 2.0, the Chronograf Admin tab becomes visible. -> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/) -> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/). +> You can then set up [multiple organizations](/chronograf/v1.8/administration/managing-organizations/) +> and [users](/chronograf/v1.8/administration/managing-influxdb-users/). Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls. diff --git a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md index ccc2b4e1d..68237ae85 100644 --- a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md @@ -50,7 +50,7 @@ You must have a connected Kapacitor instance to access the configurations. For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.8/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat @@ -87,7 +87,7 @@ The following steps describe how to create the API access token: Your token appears in the table just above the **Create new token** section: -![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png) +![HipChat token](/img/chronograf/1-6-g-eventhandlers-hipchattoken.png) ### Kafka diff --git a/content/chronograf/v1.8/guides/create-a-dashboard.md b/content/chronograf/v1.8/guides/create-a-dashboard.md index 4854638f1..51f41379f 100644 --- a/content/chronograf/v1.8/guides/create-a-dashboard.md +++ b/content/chronograf/v1.8/guides/create-a-dashboard.md @@ -10,7 +10,7 @@ menu: Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure: -* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. +* View [pre-created dashboards](/chronograf/v1.8/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. * Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard). * Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details. @@ -22,7 +22,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). +For more information, see [Configuring Chronograf](/chronograf/v1.8/administration/configuration). ## Build a dashboard @@ -57,7 +57,7 @@ In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [ ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/chronograf/v1.8/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -82,7 +82,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > **Note:** - These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). + These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/v1.8/guides/visualization-types/). #### Configure dashboard-wide settings @@ -127,4 +127,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/chronograf/v1.8/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.8/guides/create-alert-rules.md b/content/chronograf/v1.8/guides/create-alert-rules.md index 93a61a483..506962784 100644 --- a/content/chronograf/v1.8/guides/create-alert-rules.md +++ b/content/chronograf/v1.8/guides/create-alert-rules.md @@ -27,13 +27,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/chronograf/v1.8/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/chronograf/v1.8/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/chronograf/v1.8/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/chronograf/v1.8/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configure Chronograf alert rules diff --git a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md index 8f5ae8696..185e8bf9e 100644 --- a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md @@ -23,7 +23,7 @@ See the InfluxEnterprise documentation for This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.8/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -284,6 +284,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/chronograf/v1.8/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chronograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.8/guides/querying-data.md b/content/chronograf/v1.8/guides/querying-data.md index 4f0e2a296..83356ae62 100644 --- a/content/chronograf/v1.8/guides/querying-data.md +++ b/content/chronograf/v1.8/guides/querying-data.md @@ -7,7 +7,7 @@ menu: weight: 130 parent: Guides --- -Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query. +Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/v1.8/guides/visualization-types/) for your query. To open the **Data Explorer**, click the **Explore** icon in the navigation bar: @@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin ## Visualize your query -Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/). +Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/v1.8/guides/visualization-types/). ## Add queries to dashboards diff --git a/content/chronograf/v1.8/guides/using-precreated-dashboards.md b/content/chronograf/v1.8/guides/using-precreated-dashboards.md index d216dc6fd..d710b4f95 100644 --- a/content/chronograf/v1.8/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.8/guides/using-precreated-dashboards.md @@ -14,7 +14,7 @@ menu: Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. -> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates). +> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/v1.8/guides/create-a-dashboard/#dashboard-templates). ## Requirements @@ -38,7 +38,7 @@ Find a list of apps (pre-created dashboards) available to use with Chronograf be - JSON files included in the app - Cell titles included in each JSON file -The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/) page. +The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/chronograf/v1.8/administration/config-options/) page. Enable and disable apps in your [Telegraf configuration file](by default, `/etc/telegraf/telegraf.conf`). See [Configuring Telegraf](/telegraf/v1.13/administration/configuration/) for details. diff --git a/content/chronograf/v1.8/introduction/getting-started.md b/content/chronograf/v1.8/introduction/getting-started.md index 85fd10bcd..479e0631f 100644 --- a/content/chronograf/v1.8/introduction/getting-started.md +++ b/content/chronograf/v1.8/introduction/getting-started.md @@ -12,18 +12,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/v1.8/introduction/installation), get started with key features using the guides below. ### Data visualization -* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/). -* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). +* Investigate your data by building queries using the [Data Explorer](/chronograf/v1.8/guides/querying-data/). +* Use [pre-created dashboards](/chronograf/v1.8/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.8/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/chronograf/v1.8/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/chronograf/v1.8/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/chronograf/v1.8/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/chronograf/v1.8/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/chronograf/v1.8/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.8/troubleshooting/_index.md b/content/chronograf/v1.8/troubleshooting/_index.md index 48e9a9e9b..c67000ae5 100644 --- a/content/chronograf/v1.8/troubleshooting/_index.md +++ b/content/chronograf/v1.8/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/chronograf/v1.8/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md index f35386464..08681533f 100644 --- a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md @@ -20,4 +20,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/influxdb/v1.3/query_language/data_download.md b/content/influxdb/v1.3/query_language/data_download.md index c8d0b9314..df991b36e 100644 --- a/content/influxdb/v1.3/query_language/data_download.md +++ b/content/influxdb/v1.3/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.3.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.3/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.4/query_language/data_download.md b/content/influxdb/v1.4/query_language/data_download.md index 9bec2ad3c..ce09709bf 100644 --- a/content/influxdb/v1.4/query_language/data_download.md +++ b/content/influxdb/v1.4/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.4/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.5/query_language/data_download.md b/content/influxdb/v1.5/query_language/data_download.md index 7866c02b4..dfde44c48 100644 --- a/content/influxdb/v1.5/query_language/data_download.md +++ b/content/influxdb/v1.5/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.5/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.5/supported_protocols/_index.md b/content/influxdb/v1.5/supported_protocols/_index.md index 002873cd4..aa451d0db 100644 --- a/content/influxdb/v1.5/supported_protocols/_index.md +++ b/content/influxdb/v1.5/supported_protocols/_index.md @@ -10,18 +10,18 @@ menu: InfluxData supports the following protocols for interacting with InfluxDB: -### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd) +### [CollectD](/influxdb/v1.5/supported_protocols/collectd) Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP. -### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite) +### [Graphite](/influxdb/v1.5/supported_protocols/graphite) The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. -### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb) +### [OpenTSDB](/influxdb/v1.5/supported_protocols/opentsdb) InfluxDB supports both the telnet and HTTP OpenTSDB protocol. This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system. -### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus) +### [Prometheus](/influxdb/v1.5/supported_protocols/prometheus) InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints. -### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp) +### [UDP](/influxdb/v1.5/supported_protocols/udp) UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP. diff --git a/content/influxdb/v1.5/supported_protocols/collectd.md b/content/influxdb/v1.5/supported_protocols/collectd.md index f9d2b492e..4fc1173bb 100644 --- a/content/influxdb/v1.5/supported_protocols/collectd.md +++ b/content/influxdb/v1.5/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.5/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.6/query_language/data_download.md b/content/influxdb/v1.6/query_language/data_download.md index 51e7cbe0b..402c96ab9 100644 --- a/content/influxdb/v1.6/query_language/data_download.md +++ b/content/influxdb/v1.6/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.6/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.6/supported_protocols/_index.md b/content/influxdb/v1.6/supported_protocols/_index.md index 2591658cf..81e0d9798 100644 --- a/content/influxdb/v1.6/supported_protocols/_index.md +++ b/content/influxdb/v1.6/supported_protocols/_index.md @@ -10,18 +10,18 @@ menu: InfluxData supports the following protocols for interacting with InfluxDB: -### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd) +### [CollectD](/influxdb/v1.6/supported_protocols/collectd) Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP. -### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite) +### [Graphite](/influxdb/v1.6/supported_protocols/graphite) The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. -### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb) +### [OpenTSDB](/influxdb/v1.6/supported_protocols/opentsdb) InfluxDB supports both the telnet and HTTP OpenTSDB protocol. This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system. -### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus) +### [Prometheus](/influxdb/v1.6/supported_protocols/prometheus) InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints. -### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp) +### [UDP](/influxdb/v1.6/supported_protocols/udp) UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP. diff --git a/content/influxdb/v1.6/supported_protocols/collectd.md b/content/influxdb/v1.6/supported_protocols/collectd.md index 6db666522..e826fb867 100644 --- a/content/influxdb/v1.6/supported_protocols/collectd.md +++ b/content/influxdb/v1.6/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.6/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.7/_index.md b/content/influxdb/v1.7/_index.md index cb73da825..1cfd0ea04 100644 --- a/content/influxdb/v1.7/_index.md +++ b/content/influxdb/v1.7/_index.md @@ -28,4 +28,4 @@ It compiles into a single binary with no external dependencies. * Continuous queries automatically compute aggregate data to make frequent queries more efficient. The open source edition of InfluxDB runs on a single node. -If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "influxdb" "v1" >}}/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/influxdb/v1.7/high_availability/). diff --git a/content/influxdb/v1.7/flux/_index.md b/content/influxdb/v1.7/flux/_index.md index 03d71e498..88bb1f370 100644 --- a/content/influxdb/v1.7/flux/_index.md +++ b/content/influxdb/v1.7/flux/_index.md @@ -9,7 +9,7 @@ menu: --- Flux is a functional data scripting language designed for querying, analyzing, and acting on time series data. -Its takes the power of [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax. +Its takes the power of [InfluxQL](/influxdb/v1.7/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax. > Flux v0.50 is a technical preview included with [InfluxDB v1.7](/influxdb/v1.7). > It is still in active development and many functions provided by InfluxQL and TICKscript diff --git a/content/influxdb/v1.7/flux/get-started/_index.md b/content/influxdb/v1.7/flux/get-started/_index.md index 45af8149d..41c2b51f5 100644 --- a/content/influxdb/v1.7/flux/get-started/_index.md +++ b/content/influxdb/v1.7/flux/get-started/_index.md @@ -28,7 +28,7 @@ interactive Flux Read-Eval-Print-Loop (REPL) allowing you to write and run Flux --- -_For information about downloading and installing InfluxDB, see [InfluxDB installation](/{{< latest "influxdb" "v1" >}}/introduction/installation)._ +_For information about downloading and installing InfluxDB, see [InfluxDB installation](/influxdb/v1.7/introduction/installation)._ --- diff --git a/content/influxdb/v1.7/query_language/data_download.md b/content/influxdb/v1.7/query_language/data_download.md index 44a16e694..1f860b5aa 100644 --- a/content/influxdb/v1.7/query_language/data_download.md +++ b/content/influxdb/v1.7/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.7/supported_protocols/collectd.md b/content/influxdb/v1.7/supported_protocols/collectd.md index b6e8436f0..f739e8294 100644 --- a/content/influxdb/v1.7/supported_protocols/collectd.md +++ b/content/influxdb/v1.7/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.7/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.7/tools/api.md b/content/influxdb/v1.7/tools/api.md index 3b89efded..ea54a83f4 100644 --- a/content/influxdb/v1.7/tools/api.md +++ b/content/influxdb/v1.7/tools/api.md @@ -810,7 +810,7 @@ Errors are returned in JSON. | 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. | | 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. | | 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. | -| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details. +| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/influxdb/v1.7/administration/config/#max-body-size-25000000) parameter for more details. | 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. | #### Examples diff --git a/content/influxdb/v1.7/tools/influxd-cli/_index.md b/content/influxdb/v1.7/tools/influxd-cli/_index.md index 20098231d..4244472be 100644 --- a/content/influxdb/v1.7/tools/influxd-cli/_index.md +++ b/content/influxdb/v1.7/tools/influxd-cli/_index.md @@ -19,9 +19,9 @@ influxd [[command] [arguments]] ## Commands | Command | Description | |-------------------------------------------------------|----------------------------------------------------------| -| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. | -| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/config) | Display the default configuration. | +| [backup](/influxdb/v1.7/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. | +| [config](/influxdb/v1.7/tools/influxd-cli/config) | Display the default configuration. | | help | Display the help message. | -| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. | -| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/run) | Run node with existing configuration. | -| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/version) | Display the InfluxDB version. | +| [restore](/influxdb/v1.7/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. | +| [run](/influxdb/v1.7/tools/influxd-cli/run) | Run node with existing configuration. | +| [version](/influxdb/v1.7/tools/influxd-cli/version) | Display the InfluxDB version. | diff --git a/content/influxdb/v1.8/flux/_index.md b/content/influxdb/v1.8/flux/_index.md index 3dd78c6f5..bd0b65a8e 100644 --- a/content/influxdb/v1.8/flux/_index.md +++ b/content/influxdb/v1.8/flux/_index.md @@ -9,7 +9,7 @@ menu: --- Flux is a functional data scripting language designed for querying, analyzing, and acting on time series data. -Its takes the power of [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax. +Its takes the power of [InfluxQL](/influxdb/v1.8/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax. > Flux v0.65 is production-ready and included with [InfluxDB v1.8](/influxdb/v1.8). > The InfluxDB v1.8 implementation of Flux is read-only and does not support diff --git a/content/influxdb/v1.8/flux/get-started/_index.md b/content/influxdb/v1.8/flux/get-started/_index.md index a6381e525..e543561fa 100644 --- a/content/influxdb/v1.8/flux/get-started/_index.md +++ b/content/influxdb/v1.8/flux/get-started/_index.md @@ -28,7 +28,7 @@ interactive Flux Read-Eval-Print-Loop (REPL) allowing you to write and run Flux --- -_For information about downloading and installing InfluxDB, see [InfluxDB installation](/{{< latest "influxdb" "v1" >}}/introduction/installation)._ +_For information about downloading and installing InfluxDB, see [InfluxDB installation](/influxdb/v1.8/introduction/installation)._ --- diff --git a/content/influxdb/v1.8/query_language/sample-data.md b/content/influxdb/v1.8/query_language/sample-data.md index 35da0180c..863dfa7ac 100644 --- a/content/influxdb/v1.8/query_language/sample-data.md +++ b/content/influxdb/v1.8/query_language/sample-data.md @@ -34,7 +34,7 @@ InfluxDB shell 1.4.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.8/supported_protocols/collectd.md b/content/influxdb/v1.8/supported_protocols/collectd.md index 5915dba10..706b1e174 100644 --- a/content/influxdb/v1.8/supported_protocols/collectd.md +++ b/content/influxdb/v1.8/supported_protocols/collectd.md @@ -17,7 +17,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.8/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.8/tools/api.md b/content/influxdb/v1.8/tools/api.md index eb3a0b3a9..68c56050a 100644 --- a/content/influxdb/v1.8/tools/api.md +++ b/content/influxdb/v1.8/tools/api.md @@ -941,7 +941,7 @@ Errors are returned in JSON. | 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. | | 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. | | 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. | -| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details. +| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/influxdb/v1.8/administration/config/#max-body-size-25000000) parameter for more details. | 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. | #### Examples diff --git a/content/influxdb/v1.8/tools/influxd/_index.md b/content/influxdb/v1.8/tools/influxd/_index.md index 15da09720..239eef985 100644 --- a/content/influxdb/v1.8/tools/influxd/_index.md +++ b/content/influxdb/v1.8/tools/influxd/_index.md @@ -20,9 +20,9 @@ influxd [[command] [arguments]] ## Commands | Command | Description | |-------------------------------------------------------|----------------------------------------------------------| -| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. | -| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd/config) | Display the default configuration. | +| [backup](/influxdb/v1.8/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. | +| [config](/influxdb/v1.8/tools/influxd/config) | Display the default configuration. | | help | Display the help message. | -| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. | -| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd/run) | Run node with existing configuration. | -| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd/version) | Display the InfluxDB version. | +| [restore](/influxdb/v1.8/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. | +| [run](/influxdb/v1.8/tools/influxd/run) | Run node with existing configuration. | +| [version](/influxdb/v1.8/tools/influxd/version) | Display the InfluxDB version. | diff --git a/content/influxdb/v2.0/account-management/billing.md b/content/influxdb/v2.0/account-management/billing.md index 4e94c7b70..96faa260c 100644 --- a/content/influxdb/v2.0/account-management/billing.md +++ b/content/influxdb/v2.0/account-management/billing.md @@ -100,7 +100,7 @@ On the **Billing page**, view the total limits available for the Free Plan. ## Exceeded rate limits -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. +If you exceed your plan's [rate limits](/influxdb/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._ diff --git a/content/influxdb/v2.0/account-management/data-usage.md b/content/influxdb/v2.0/account-management/data-usage.md index 87dd38ebf..fbbe1946f 100644 --- a/content/influxdb/v2.0/account-management/data-usage.md +++ b/content/influxdb/v2.0/account-management/data-usage.md @@ -33,14 +33,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/account-management/pricing-plans/), {{< cloud-name >}} +If you exceed your plan's [rate limits](/influxdb/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/account-management/billing/#upgrade-to-usage-based-plan)._ +_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/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: diff --git a/content/influxdb/v2.0/account-management/offboarding.md b/content/influxdb/v2.0/account-management/offboarding.md index a68d5d5cf..34a436808 100644 --- a/content/influxdb/v2.0/account-management/offboarding.md +++ b/content/influxdb/v2.0/account-management/offboarding.md @@ -34,11 +34,11 @@ Exported data and artifacts can be used in an InfluxDB OSS instance. #### Export tasks -For details, see [Export a task](/v2.0/process-data/manage-tasks/export-task/). +For details, see [Export a task](/influxdb/v2.0/process-data/manage-tasks/export-task/). #### Export dashboards -For details, see [Export a dashboard](/v2.0/visualize-data/dashboards/export-dashboard/). +For details, see [Export a dashboard](/influxdb/v2.0/visualize-data/dashboards/export-dashboard/). #### Save Telegraf configurations diff --git a/content/influxdb/v2.0/account-management/pricing-calculator.md b/content/influxdb/v2.0/account-management/pricing-calculator.md index 9cfa92fdc..97e6cf0d0 100644 --- a/content/influxdb/v2.0/account-management/pricing-calculator.md +++ b/content/influxdb/v2.0/account-management/pricing-calculator.md @@ -48,4 +48,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/get-started/). +6. Click **Get started with InfluxDB Cloud** [to get started](/influxdb/v2.0/get-started/). diff --git a/content/influxdb/v2.0/account-management/pricing-plans.md b/content/influxdb/v2.0/account-management/pricing-plans.md index 86e6f897f..4b30eac3d 100644 --- a/content/influxdb/v2.0/account-management/pricing-plans.md +++ b/content/influxdb/v2.0/account-management/pricing-plans.md @@ -21,7 +21,7 @@ InfluxDB Cloud 2.0 offers two pricing plans: - [Free Plan](#free-plan) - [Usage-based Plan](#usage-based-plan) - + ## Free Plan @@ -46,11 +46,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/account-management/billing/#upgrade-to-usage-based-plan)._ +_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/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/account-management/data-usage/). +The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/influxdb/v2.0/account-management/data-usage/). #### Usage-based Plan rate limits diff --git a/content/influxdb/v2.0/backup-restore/backup.md b/content/influxdb/v2.0/backup-restore/backup.md index 904b03d3e..640c6e1e2 100644 --- a/content/influxdb/v2.0/backup-restore/backup.md +++ b/content/influxdb/v2.0/backup-restore/backup.md @@ -15,7 +15,7 @@ related: products: [oss] --- -Use the [`influx backup` command](/v2.0/reference/cli/influx/backup/) to back up +Use the [`influx backup` command](/influxdb/v2.0/reference/cli/influx/backup/) to back up data and metadata stored in InfluxDB. InfluxDB copies all data and metadata to a set of files stored in a specified directory on your local filesystem. @@ -34,7 +34,7 @@ The `influx backup` command requires: - The directory path for where to store the backup file set - The **root authorization token** (the token created for the first user in the - [InfluxDB setup process](/v2.0/get-started/)). + [InfluxDB setup process](/influxdb/v2.0/get-started/)). ##### Back up data with the influx CLI ```sh diff --git a/content/influxdb/v2.0/backup-restore/restore.md b/content/influxdb/v2.0/backup-restore/restore.md index 63b6b738c..363e7ac2c 100644 --- a/content/influxdb/v2.0/backup-restore/restore.md +++ b/content/influxdb/v2.0/backup-restore/restore.md @@ -43,12 +43,12 @@ _See [Recover from a failed restore](#recover-from-a-failed-restore)._ ``` _For more information about restore options and flags, see the - [`influxd restore` documentation](/v2.0/reference/cli/influxd/restore/)._ + [`influxd restore` documentation](/influxdb/v2.0/reference/cli/influxd/restore/)._ ## Customize the TSI rebuild process -By default, InfluxDB rebuilds the index and [series file](/v2.0/reference/glossary/#series-file) when restoring data. +By default, InfluxDB rebuilds the index and [series file](/influxdb/v2.0/reference/glossary/#series-file) when restoring data. When rebuilding the Time Series Index (TSI), it uses the -[default `build-tsi` options](/v2.0/reference/cli/influxd/inspect/build-tsi/). +[default `build-tsi` options](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/). To customize the Time Series Index (TSI) rebuild process: 1. Disable rebuilding the index and series files when restoring data: @@ -58,7 +58,7 @@ To customize the Time Series Index (TSI) rebuild process: ``` 2. Manually run `influxd inspect build-tsi` with any - [custom options](/v2.0/reference/cli/influxd/inspect/build-tsi/#flags). + [custom options](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/#flags). ```sh influxd inspect build-tsi \ @@ -67,13 +67,13 @@ To customize the Time Series Index (TSI) rebuild process: ``` {{% note %}} -Manually rebuild the TSI index to [adjust the performance](/v2.0/reference/cli/influxd/inspect/build-tsi/#adjust-performance) +Manually rebuild the TSI index to [adjust the performance](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/#adjust-performance) of the TSI rebuild process. {{% /note %}} ## Recover from a failed restore If the restoration process fails, InfluxDB preserves existing data in a `tmp` -directory in the [target engine path](/v2.0/reference/cli/influxd/restore/#flags) +directory in the [target engine path](/influxdb/v2.0/reference/cli/influxd/restore/#flags) (default is `~/.influxdbv2/engine`). To recover from a failed restore: diff --git a/content/influxdb/v2.0/influxdb-templates/_index.md b/content/influxdb/v2.0/influxdb-templates/_index.md index 651399ce3..137aaafda 100644 --- a/content/influxdb/v2.0/influxdb-templates/_index.md +++ b/content/influxdb/v2.0/influxdb-templates/_index.md @@ -42,7 +42,7 @@ The `metadata.name` field in manifests uniquely identifies each resource in the If resources in the template depend on other InfluxDB resources, all dependencies must be included in the template. -_See [Create an InfluxDB template](/v2.0/influxdb-templates/create/) for information about +_See [Create an InfluxDB template](/influxdb/v2.0/influxdb-templates/create/) for information about generating template manifests._ ### Template resources diff --git a/content/influxdb/v2.0/influxdb-templates/cloud.md b/content/influxdb/v2.0/influxdb-templates/cloud.md index 8ec167a94..fa4cae6aa 100644 --- a/content/influxdb/v2.0/influxdb-templates/cloud.md +++ b/content/influxdb/v2.0/influxdb-templates/cloud.md @@ -16,16 +16,16 @@ influxdb/v2.0/tags: [templates] products: [cloud] --- -Use the [`influx` command line interface (CLI)](/v2.0/reference/cli/influx/) +Use the [`influx` command line interface (CLI)](/influxdb/v2.0/reference/cli/influx/) to apply and manage templates in your InfluxDB Cloud account. If you haven’t already, do the following: -1. [Download and install `influx` CLI](/v2.0/get-started/#optional-download-and-install-the-influx-cli). -2. [Configure the `influx` CLI](/v2.0/get-started/#set-up-influxdb) to use your +1. [Download and install `influx` CLI](/influxdb/v2.0/get-started/#optional-download-and-install-the-influx-cli). +2. [Configure the `influx` CLI](/influxdb/v2.0/get-started/#set-up-influxdb) to use your InfluxDB Cloud instance URL, organization, and tokens. -3. [Use the `influx` CLI](/v2.0/reference/cli/influx/) to use, manage, and create +3. [Use the `influx` CLI](/influxdb/v2.0/reference/cli/influx/) to use, manage, and create InfluxDB templates: - - [Use templates](/v2.0/influxdb-templates/use/) - - [Create templates](/v2.0/influxdb-templates/create/) + - [Use templates](/influxdb/v2.0/influxdb-templates/use/) + - [Create templates](/influxdb/v2.0/influxdb-templates/create/) diff --git a/content/influxdb/v2.0/influxdb-templates/create.md b/content/influxdb/v2.0/influxdb-templates/create.md index b9da82112..b726a069f 100644 --- a/content/influxdb/v2.0/influxdb-templates/create.md +++ b/content/influxdb/v2.0/influxdb-templates/create.md @@ -36,19 +36,19 @@ In **InfluxDB Cloud**, your user account is an organization. **To create a template:** -1. [Start InfluxDB](/v2.0/get-started/). -2. [Create a new organization](/v2.0/organizations/create-org/). +1. [Start InfluxDB](/influxdb/v2.0/get-started/). +2. [Create a new organization](/influxdb/v2.0/organizations/create-org/). 3. In the InfluxDB UI add one or more of the following templatable resources: - - [buckets](/v2.0/organizations/buckets/create-bucket/) - - [checks](/v2.0/monitor-alert/checks/create/) - - [dashboards](/v2.0/visualize-data/dashboards/create-dashboard/) - - [dashboard variables](/v2.0/visualize-data/variables/create-variable/) - - [labels](/v2.0/visualize-data/labels/) - - [notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/) - - [notification rules](/v2.0/monitor-alert/notification-rules/create/) - - [tasks](/v2.0/process-data/manage-tasks/create-task/) - - [Telegraf configurations](/v2.0/write-data/use-telegraf/) + - [buckets](/influxdb/v2.0/organizations/buckets/create-bucket/) + - [checks](/influxdb/v2.0/monitor-alert/checks/create/) + - [dashboards](/influxdb/v2.0/visualize-data/dashboards/create-dashboard/) + - [dashboard variables](/influxdb/v2.0/visualize-data/variables/create-variable/) + - [labels](/influxdb/v2.0/visualize-data/labels/) + - [notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/) + - [notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create/) + - [tasks](/influxdb/v2.0/process-data/manage-tasks/create-task/) + - [Telegraf configurations](/influxdb/v2.0/write-data/use-telegraf/) 4. Export the template _(see [below](#export-a-template))_. @@ -108,7 +108,7 @@ influx export all \ ``` For information about flags, see the -[`influx export all` documentation](/v2.0/reference/cli/influx/export/all/). +[`influx export all` documentation](/influxdb/v2.0/reference/cli/influx/export/all/). ### Export specific resources To export specific resources within an organization to a template manifest, @@ -122,7 +122,7 @@ Provide the following: **JSON** (`.json`) are supported. - **Resource flags** with corresponding lists of resource IDs to include in the template. For information about what resource flags are available, see the - [`influx export` documentation](/v2.0/reference/cli/influx/export/). + [`influx export` documentation](/influxdb/v2.0/reference/cli/influx/export/). ###### Export specific resources to a template ```sh @@ -219,7 +219,7 @@ metadata: {{< /code-tabs-wrapper >}} Using the example above, users are prompted to provide a value for `bucket-name-1` -when [applying the template](/v2.0/influxdb-templates/use/#apply-templates). +when [applying the template](/influxdb/v2.0/influxdb-templates/use/#apply-templates). Users can also include the `--env-ref` flag with the appropriate key-value pair when installing the template. diff --git a/content/influxdb/v2.0/influxdb-templates/stacks/_index.md b/content/influxdb/v2.0/influxdb-templates/stacks/_index.md index 11238ad95..54dd973c6 100644 --- a/content/influxdb/v2.0/influxdb-templates/stacks/_index.md +++ b/content/influxdb/v2.0/influxdb-templates/stacks/_index.md @@ -15,7 +15,7 @@ related: - /influxdb/v2.0/reference/cli/stacks/ --- -**InfluxDB stacks** are **stateful [InfluxDB templates](/v2.0/influxdb-templates)** +**InfluxDB stacks** are **stateful [InfluxDB templates](/influxdb/v2.0/influxdb-templates)** that let you add, update, and remove templated resources over time, avoid duplicating resources when applying the same or similar templates more than once, and apply changes to distributed instances of InfluxDB OSS or InfluxDB Cloud. @@ -43,7 +43,7 @@ apply updates without creating duplicate resources. In many cases, users have more than one instance of InfluxDB running and apply the same template to each separate instance. By using stacks, you can make changes to a stack on one instance, -[export the stack as a template](/v2.0/influxdb-templates/create/#export-a-stack) +[export the stack as a template](/influxdb/v2.0/influxdb-templates/create/#export-a-stack) and then apply the changes to your other InfluxDB instances. ## Manage InfluxDB Stacks diff --git a/content/influxdb/v2.0/influxdb-templates/stacks/init.md b/content/influxdb/v2.0/influxdb-templates/stacks/init.md index b3ac98023..9e14733df 100644 --- a/content/influxdb/v2.0/influxdb-templates/stacks/init.md +++ b/content/influxdb/v2.0/influxdb-templates/stacks/init.md @@ -2,9 +2,9 @@ title: Initialize an InfluxDB stack list_title: Initialize a stack description: > - InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/v2.0/influxdb-templates/use/) + InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/) **without providing a stack ID**. - To manually create or initialize a new stack, use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/). + To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/). menu: influxdb_2_0: parent: InfluxDB stacks @@ -30,12 +30,12 @@ list_code_example: | ``` --- -InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/v2.0/influxdb-templates/use/) +InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/) **without providing a stack ID**. -To manually create or initialize a new stack, use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/). +To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/). ## Initialize a stack when applying a template -To automatically create a new stack when [applying an InfluxDB template](/v2.0/influxdb-templates/use/) +To automatically create a new stack when [applying an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/) **don't provide a stack ID**. InfluxDB applies the resources in the template to a new stack and provides the **stack ID** the output. @@ -46,7 +46,7 @@ influx apply \ ``` ## Manually initialize a new stack -Use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/) +Use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/) to create or initialize a new InfluxDB stack. **Provide the following:** diff --git a/content/influxdb/v2.0/influxdb-templates/stacks/remove.md b/content/influxdb/v2.0/influxdb-templates/stacks/remove.md index d9bf10476..e7e7e931b 100644 --- a/content/influxdb/v2.0/influxdb-templates/stacks/remove.md +++ b/content/influxdb/v2.0/influxdb-templates/stacks/remove.md @@ -2,7 +2,7 @@ title: Remove an InfluxDB stack list_title: Remove a stack description: > - Use the [`influx stacks remove` command](/v2.0/reference/cli/influx/stacks/remove/) + Use the [`influx stacks remove` command](/influxdb/v2.0/reference/cli/influx/stacks/remove/) to remove an InfluxDB stack and all its associated resources. menu: influxdb_2_0: @@ -21,7 +21,7 @@ list_code_example: | ``` --- -Use the [`influx stacks remove` command](/v2.0/reference/cli/influx/stacks/remove/) +Use the [`influx stacks remove` command](/influxdb/v2.0/reference/cli/influx/stacks/remove/) to remove an InfluxDB stack and all its associated resources. **Provide the following:** diff --git a/content/influxdb/v2.0/influxdb-templates/stacks/update.md b/content/influxdb/v2.0/influxdb-templates/stacks/update.md index 5df7bd1c8..2873e2b4c 100644 --- a/content/influxdb/v2.0/influxdb-templates/stacks/update.md +++ b/content/influxdb/v2.0/influxdb-templates/stacks/update.md @@ -2,7 +2,7 @@ title: Update an InfluxDB stack list_title: Update a stack description: > - Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/) + Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/) to update a stack with a modified template. When applying a template to an existing stack, InfluxDB checks to see if the resources in the template match existing resources. @@ -28,7 +28,7 @@ list_code_example: | ``` --- -Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/) +Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/) to update a stack with a modified template. When applying a template to an existing stack, InfluxDB checks to see if the resources in the template match existing resources. @@ -36,7 +36,7 @@ InfluxDB updates, adds, and removes resources to resolve differences between the current state of the stack and the newly applied template. Each stack is uniquely identified by a **stack ID**. -For information about retrieving your stack ID, see [View stacks](/v2.0/influxdb-templates/stacks/view/). +For information about retrieving your stack ID, see [View stacks](/influxdb/v2.0/influxdb-templates/stacks/view/). **Provide the following:** diff --git a/content/influxdb/v2.0/influxdb-templates/stacks/view.md b/content/influxdb/v2.0/influxdb-templates/stacks/view.md index 6cd8d7f0d..34a300033 100644 --- a/content/influxdb/v2.0/influxdb-templates/stacks/view.md +++ b/content/influxdb/v2.0/influxdb-templates/stacks/view.md @@ -2,7 +2,7 @@ title: View InfluxDB stacks list_title: View stacks description: > - Use the [`influx stacks` command](/v2.0/reference/cli/influx/stacks/) + Use the [`influx stacks` command](/influxdb/v2.0/reference/cli/influx/stacks/) to view installed InfluxDB stacks and their associated resources. menu: influxdb_2_0: @@ -19,7 +19,7 @@ list_code_example: | ``` --- -Use the [`influx stacks` command](/v2.0/reference/cli/influx/stacks/) +Use the [`influx stacks` command](/influxdb/v2.0/reference/cli/influx/stacks/) to view installed InfluxDB stacks and their associated resources. **Provide the following:** diff --git a/content/influxdb/v2.0/influxdb-templates/use.md b/content/influxdb/v2.0/influxdb-templates/use.md index f51c0db10..0394e5e85 100644 --- a/content/influxdb/v2.0/influxdb-templates/use.md +++ b/content/influxdb/v2.0/influxdb-templates/use.md @@ -54,7 +54,7 @@ https://raw.githubusercontent.com/influxdata/community-templates/master/docker/d ## View a template summary To view a summary of what's included in a template before applying the template, -use the [`influx template` command](/v2.0/reference/cli/influx/template/). +use the [`influx template` command](/influxdb/v2.0/reference/cli/influx/template/). View a summary of a template stored in your local filesystem or from a URL. {{% code-tabs-wrapper %}} @@ -84,7 +84,7 @@ influx template -u https://raw.githubusercontent.com/influxdata/community-templa ## Validate a template To validate a template before you install it or troubleshoot a template, use -the [`influx template validate` command](/v2.0/reference/cli/influx/template/validate/). +the [`influx template validate` command](/influxdb/v2.0/reference/cli/influx/template/validate/). Validate a template stored in your local filesystem or from a URL. {{% code-tabs-wrapper %}} @@ -113,7 +113,7 @@ influx template validate -u https://raw.githubusercontent.com/influxdata/communi {{% /code-tabs-wrapper %}} ## Apply templates -Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/) to install templates +Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/) to install templates from your local filesystem or from URLs. - [Apply a template from a file](#apply-a-template-from-a-file) @@ -128,7 +128,7 @@ from your local filesystem or from URLs. To apply a template to an existing stack, include the stack ID when applying the template. Any time you apply a template without a stack ID, InfluxDB initializes a new stack and all new resources. -For more information, see [InfluxDB stacks](/v2.0/influxdb-templates/stacks/). +For more information, see [InfluxDB stacks](/influxdb/v2.0/influxdb-templates/stacks/). {{% /note %}} ### Apply a template from a file @@ -204,7 +204,7 @@ influx apply -o example-org \ ``` ### Define environment references -Some templates include [environment references](/v2.0/influxdb-templates/create/#include-user-definable-resource-names) that let you provide custom resource names. +Some templates include [environment references](/influxdb/v2.0/influxdb-templates/create/#include-user-definable-resource-names) that let you provide custom resource names. The `influx apply` command prompts you to provide a value for each environment reference in the template. You can also provide values for environment references by including an `--env-ref` @@ -219,7 +219,7 @@ influx apply -o example-org -f /path/to/template.yml \ ``` ### Include a secret when installing a template -Some templates use [secrets](/v2.0/security/secrets/) in queries. +Some templates use [secrets](/influxdb/v2.0/security/secrets/) in queries. Secret values are not included in templates. To define secret values when installing a template, include the `--secret` flag with the secret key-value pair. @@ -240,4 +240,4 @@ influx apply -o example-org -f /path/to/template.yml \ --secret=BAZ=quz ``` -_To add a secret after applying a template, see [Add secrets](/v2.0/security/secrets/manage-secrets/add/)._ +_To add a secret after applying a template, see [Add secrets](/influxdb/v2.0/security/secrets/manage-secrets/add/)._ diff --git a/content/influxdb/v2.0/monitor-alert/_index.md b/content/influxdb/v2.0/monitor-alert/_index.md index 7ffbcd277..8caf83c71 100644 --- a/content/influxdb/v2.0/monitor-alert/_index.md +++ b/content/influxdb/v2.0/monitor-alert/_index.md @@ -14,25 +14,25 @@ influxdb/v2.0/tags: [monitor, alert, checks, notification, endpoints] --- Monitor your time series data and send alerts by creating checks, notification -rules, and notification endpoints. Or use [community templates to monitor](/v2.0/monitor-alert/templates/) supported environments. +rules, and notification endpoints. Or use [community templates to monitor](/influxdb/v2.0/monitor-alert/templates/) supported environments. ## Overview -1. A [check](/v2.0/reference/glossary/#check) in InfluxDB queries data and assigns a status with a `_level` based on specific conditions. +1. A [check](/influxdb/v2.0/reference/glossary/#check) in InfluxDB queries data and assigns a status with a `_level` based on specific conditions. 2. InfluxDB stores the output of a check in the `statuses` measurement in the `_monitoring` system bucket. -3. [Notification rules](/v2.0/reference/glossary/#notification-rule) check data in the `statuses` +3. [Notification rules](/influxdb/v2.0/reference/glossary/#notification-rule) check data in the `statuses` measurement and, based on conditions set in the notification rule, send a message - to a [notification endpoint](/v2.0/reference/glossary/#notification-endpoint). + to a [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint). 4. InfluxDB stores notifications in the `notifications` measurement in the `_monitoring` system bucket. ## Create an alert To get started, do the following: -1. [Create checks](/v2.0/monitor-alert/checks/create/) to monitor data and assign a status. -2. [Add notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/) +1. [Create checks](/influxdb/v2.0/monitor-alert/checks/create/) to monitor data and assign a status. +2. [Add notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/) to send notifications to third parties. -3. [Create notification rules](/v2.0/monitor-alert/notification-rules/create) to check +3. [Create notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create) to check statuses and send notifications to your notifications endpoints. ## Manage your monitoring and alerting pipeline diff --git a/content/influxdb/v2.0/monitor-alert/checks/create.md b/content/influxdb/v2.0/monitor-alert/checks/create.md index 8aae6bb37..b24b3a3da 100644 --- a/content/influxdb/v2.0/monitor-alert/checks/create.md +++ b/content/influxdb/v2.0/monitor-alert/checks/create.md @@ -87,16 +87,16 @@ in a specified amount of time. Use custom tags to associate additional metadata with the check. Common metadata tags across different checks lets you easily group and organize checks. - You can also use custom tags in [notification rules](/v2.0/monitor-alert/notification-rules/create/). + You can also use custom tags in [notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create/). 3. In the **Status Message Template** column, enter the status message template for the check. - Use [Flux string interpolation](/v2.0/reference/flux/language/string-interpolation/) + Use [Flux string interpolation](/influxdb/v2.0/reference/flux/language/string-interpolation/) to populate the message with data from the query. {{% note %}} #### Flux only interpolates string values Flux currently interpolates only string values. -Use the [string() function](/v2.0/reference/flux/stdlib/built-in/transformations/type-conversions/string/) +Use the [string() function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/type-conversions/string/) to convert non-string values to strings. ```js diff --git a/content/influxdb/v2.0/monitor-alert/checks/delete.md b/content/influxdb/v2.0/monitor-alert/checks/delete.md index 70bd646ea..59f06b0dd 100644 --- a/content/influxdb/v2.0/monitor-alert/checks/delete.md +++ b/content/influxdb/v2.0/monitor-alert/checks/delete.md @@ -31,6 +31,6 @@ After a check is deleted, all statuses generated by the check remain in the `_mo bucket until the retention period for the bucket expires. {{% note %}} -You can also [disable a check](/v2.0/monitor-alert/checks/update/#enable-or-disable-a-check) +You can also [disable a check](/influxdb/v2.0/monitor-alert/checks/update/#enable-or-disable-a-check) without having to delete it. {{% /note %}} diff --git a/content/influxdb/v2.0/monitor-alert/checks/update.md b/content/influxdb/v2.0/monitor-alert/checks/update.md index 7d4060f78..0acb4f468 100644 --- a/content/influxdb/v2.0/monitor-alert/checks/update.md +++ b/content/influxdb/v2.0/monitor-alert/checks/update.md @@ -33,7 +33,7 @@ To update checks, select **Alerts** in the navigation menu on the left. 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/)._ +_For details about using the check builder, see [Create checks](/influxdb/v2.0/monitor-alert/checks/create/)._ ## Enable or disable a check Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it. diff --git a/content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md b/content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md index d1efca478..121e9e482 100644 --- a/content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md +++ b/content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md @@ -14,7 +14,7 @@ related: - /influxdb/v2.0/monitor-alert/notification-rules/ --- -To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/v2.0/monitor-alert/checks/create). +To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/influxdb/v2.0/monitor-alert/checks/create). ## Create a notification endpoint in the UI diff --git a/content/influxdb/v2.0/monitor-alert/notification-endpoints/delete.md b/content/influxdb/v2.0/monitor-alert/notification-endpoints/delete.md index 96d48abea..937d20e88 100644 --- a/content/influxdb/v2.0/monitor-alert/notification-endpoints/delete.md +++ b/content/influxdb/v2.0/monitor-alert/notification-endpoints/delete.md @@ -14,7 +14,7 @@ related: - /influxdb/v2.0/monitor-alert/notification-rules/ --- -If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed. +If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/influxdb/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed. ## Delete a notification endpoint in the UI diff --git a/content/influxdb/v2.0/monitor-alert/notification-endpoints/update.md b/content/influxdb/v2.0/monitor-alert/notification-endpoints/update.md index 7770f7c30..454472e82 100644 --- a/content/influxdb/v2.0/monitor-alert/notification-endpoints/update.md +++ b/content/influxdb/v2.0/monitor-alert/notification-endpoints/update.md @@ -14,7 +14,7 @@ related: - /influxdb/v2.0/monitor-alert/notification-rules/ --- -To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/). +To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/influxdb/v2.0/monitor-alert/notification-rules/update/). ## Add a label to notification endpoint @@ -65,4 +65,4 @@ To update the notification endpoint details, complete the procedures below as ne 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/). + For details about each field, see [Create notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/). diff --git a/content/influxdb/v2.0/monitor-alert/notification-rules/create.md b/content/influxdb/v2.0/monitor-alert/notification-rules/create.md index 2b37c6a92..284e5b5b8 100644 --- a/content/influxdb/v2.0/monitor-alert/notification-rules/create.md +++ b/content/influxdb/v2.0/monitor-alert/notification-rules/create.md @@ -14,8 +14,8 @@ related: --- Once you've set up checks and notification endpoints, create notification rules to alert you. -_For details, see [Manage checks](/v2.0/monitor-alert/checks/) and -[Manage notification endpoints](/v2.0/monitor-alert/notification-endpoints/)._ +_For details, see [Manage checks](/influxdb/v2.0/monitor-alert/checks/) and +[Manage notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/)._ ## Create a new notification rule in the UI diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md index 5ae8cc299..4798ae208 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md @@ -13,23 +13,23 @@ Use the [AWS CloudWatch Monitoring template](https://github.com/influxdata/commu The AWS CloudWatch Monitoring template includes the following: -- two [dashboards](/v2.0/reference/glossary/#dashboard): +- two [dashboards](/influxdb/v2.0/reference/glossary/#dashboard): - **AWS CloudWatch NLB (Network Load Balancers) Monitoring**: Displays data from the `cloudwatch_aws_network_elb measurement` - **AWS CloudWatch Instance Monitoring**: Displays data from the `cloudwatch_aws_ec2` measurement -- two [buckets](/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch` +- two [buckets](/influxdb/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch` - two labels: `inputs.cloudwatch`, `AWS` - one variable: `v.bucket` -- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/v2.0/reference/telegraf-plugins/#cloudwatch) +- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/influxdb/v2.0/reference/telegraf-plugins/#cloudwatch) ## Apply the template -1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command: +1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command: ```sh influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/aws_cloudwatch/aws_cloudwatch.yml ``` - For more information, see [influx apply](/v2.0/reference/cli/influx/apply/). -2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/v2.0/reference/api/). + For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/). +2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). 3. In your Telegraf configuration file (`telegraf.conf`), find the following example `influxdb_v2` output plugins, and then **replace** the `urls` to specify the servers to monitor: ```sh @@ -47,7 +47,7 @@ The AWS CloudWatch Monitoring template includes the following: organization = "$INFLUX_ORG" bucket = “cloudwatch" ``` -4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). +4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). ## View the incoming data diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md index 6a1dd63a1..d6f6679ad 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md @@ -10,41 +10,41 @@ weight: 202 --- Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data). -This template uses the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard. +This template uses the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard. The Docker Monitoring template includes the following: -- one [dashboard](/v2.0/reference/glossary/#dashboard): **Docker** -- one [bucket](/v2.0/reference/glossary/#bucket): `docker, 7d retention` +- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Docker** +- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `docker, 7d retention` - labels: Docker input plugin labels -- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin +- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin - one variable: `bucket` -- four [checks](/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit` -- one [notification endpoint](/v2.0/reference/glossary/#notification-endpoint): `Http Post` -- one [notification rule](/v2.0/reference/glossary/#notification-rule): `Crit Alert` +- four [checks](/influxdb/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit` +- one [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint): `Http Post` +- one [notification rule](/influxdb/v2.0/reference/glossary/#notification-rule): `Crit Alert` -For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/v2.0/monitor-alert/). +For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/influxdb/v2.0/monitor-alert/). ## Apply the template -1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command: +1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command: ```sh influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml ``` - For more information, see [influx apply](/v2.0/reference/cli/influx/apply/). + For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/). > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). -2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: - - Depending on how you run Docker, you may need to customize the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value. +2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: + - Depending on how you run Docker, you may need to customize the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value. - Set the following environment variables: - - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/). - - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/). + - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). + - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud. -4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). +4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). ## View incoming data diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md index da815446c..f6e7d399d 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md @@ -10,32 +10,32 @@ weight: 206 --- Use the [vSphere Dashboard for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/vsphere) to monitor your vSphere host. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data). -This template uses the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard. +This template uses the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard. The Docker Monitoring template includes the following: -- one [dashboard](/v2.0/reference/glossary/#dashboard): **vsphere** -- one [bucket](/v2.0/reference/glossary/#bucket): `vsphere` +- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **vsphere** +- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `vsphere` - label: vsphere -- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, vSphere input plugin +- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, vSphere input plugin - one variable: `bucket` ## Apply the template -1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command: +1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command: ```sh influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/vsphere/vsphere.yml ``` - For more information, see [influx apply](/v2.0/reference/cli/influx/apply/). + For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/). > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). -2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: - Set the following environment variables: - - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/). - - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/). + - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). + - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud. - INFLUX_BUCKET: Bucket to store data in. To use the bucket included, you must export the variable: `export INFLUX_BUCKET=vsphere` 4. - Set the host address to the vSphere and provide the `username` and `password` as variables: @@ -45,7 +45,7 @@ The Docker Monitoring template includes the following: password = "$vsphere-password" ``` -4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). +4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). ## View incoming data diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md index d39febcf4..ebde10b53 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md @@ -13,31 +13,31 @@ Use the [Windows System Monitoring template](https://github.com/influxdata/commu The Windows System Monitoring template includes the following: -- one [dashboard](/v2.0/reference/glossary/#dashboard): **Windows System** -- one [bucket](/v2.0/reference/glossary/#bucket): `telegraf`, 7d retention +- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Windows System** +- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `telegraf`, 7d retention - label: `Windows System Template`, Telegraf plugin labels: `outputs.influxdb_v2` -- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, Windows Performance Counters input plugin +- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, Windows Performance Counters input plugin - two variables: `bucket`, `windows_host` ## Apply the template -1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command: +1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command: ```sh influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/windows_system/windows_system.yml ``` - For more information, see [influx apply](/v2.0/reference/cli/influx/apply/). + For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/). > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). -2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Windows system and [InfluxDB v2 API](/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Windows system and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: - Set the following environment variables: - - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/). - - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/). + - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). + - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). - INFLUX_URL: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud. -4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). +4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). 5. To monitor multiple Windows systems, repeat steps 1-4 for each system. ## View incoming data diff --git a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md index 47008324c..fb9afa08d 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md +++ b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md @@ -10,35 +10,35 @@ weight: 201 --- Use the [HAProxy for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/haproxy) to monitor your HAProxy instances. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data). -This template uses the [HAProxy input plugin](/v2.0/reference/telegraf-plugins/#haproxy) to collect metrics stored in an HAProxy instance and display these metrics in a dashboard. +This template uses the [HAProxy input plugin](/influxdb/v2.0/reference/telegraf-plugins/#haproxy) to collect metrics stored in an HAProxy instance and display these metrics in a dashboard. The HAProxy for InfluxDB v2 template includes the following: -- one [dashboard](/v2.0/reference/glossary/#dashboard): **HAProxy** -- one [bucket](/v2.0/reference/glossary/#bucket): `haproxy` +- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **HAProxy** +- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `haproxy` - label: `haproxy` -- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): HAProxy input plugin, InfluxDB v2 output plugin +- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): HAProxy input plugin, InfluxDB v2 output plugin - one variable: `bucket` ## Apply the template -1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command: +1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command: ```sh influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/haproxy/haproxy.yml ``` - For more information, see [influx apply](/v2.0/reference/cli/influx/apply/). + For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/). > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). -2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: - Set the following environment variables: - - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/). - - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/). + - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). + - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud. -4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). +4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf). ## View incoming data diff --git a/content/influxdb/v2.0/organizations/buckets/create-bucket.md b/content/influxdb/v2.0/organizations/buckets/create-bucket.md index 2af11c11a..1aaa9dcae 100644 --- a/content/influxdb/v2.0/organizations/buckets/create-bucket.md +++ b/content/influxdb/v2.0/organizations/buckets/create-bucket.md @@ -46,7 +46,7 @@ There are two places you can create a bucket in the UI. ## Create a bucket using the influx CLI -Use the [`influx bucket create` command](/v2.0/reference/cli/influx/bucket/create) +Use the [`influx bucket create` command](/influxdb/v2.0/reference/cli/influx/bucket/create) to create a new bucket. A bucket requires the following: - bucket name diff --git a/content/influxdb/v2.0/organizations/buckets/delete-bucket.md b/content/influxdb/v2.0/organizations/buckets/delete-bucket.md index 41813972b..8ecb05a0e 100644 --- a/content/influxdb/v2.0/organizations/buckets/delete-bucket.md +++ b/content/influxdb/v2.0/organizations/buckets/delete-bucket.md @@ -25,7 +25,7 @@ to delete a bucket. ## Delete a bucket using the influx CLI -Use the [`influx bucket delete` command](/v2.0/reference/cli/influx/bucket/delete) +Use the [`influx bucket delete` command](/influxdb/v2.0/reference/cli/influx/bucket/delete) to delete a bucket a bucket by name or ID. ### Delete a bucket by name diff --git a/content/influxdb/v2.0/organizations/buckets/update-bucket.md b/content/influxdb/v2.0/organizations/buckets/update-bucket.md index e6cc83143..edd87a9b8 100644 --- a/content/influxdb/v2.0/organizations/buckets/update-bucket.md +++ b/content/influxdb/v2.0/organizations/buckets/update-bucket.md @@ -46,7 +46,7 @@ If you change a bucket name, be sure to update the bucket in the above places as ## Update a bucket using the influx CLI -Use the [`influx bucket update` command](/v2.0/reference/cli/influx/bucket/update) +Use the [`influx bucket update` command](/influxdb/v2.0/reference/cli/influx/bucket/update) to update a bucket. Updating a bucket requires the following: - The bucket ID _(provided in the output of `influx bucket list`)_ diff --git a/content/influxdb/v2.0/organizations/buckets/view-buckets.md b/content/influxdb/v2.0/organizations/buckets/view-buckets.md index 89dba7299..5f9dcf7bc 100644 --- a/content/influxdb/v2.0/organizations/buckets/view-buckets.md +++ b/content/influxdb/v2.0/organizations/buckets/view-buckets.md @@ -26,7 +26,7 @@ aliases: ### View buckets using the influx CLI -Use the [`influx bucket list` command](/v2.0/reference/cli/influx/bucket/list) +Use the [`influx bucket list` command](/influxdb/v2.0/reference/cli/influx/bucket/list) to view a buckets in an organization. ```sh @@ -34,5 +34,5 @@ influx bucket list ``` Other filtering options such as filtering by organization, name, or ID are available. -See the [`influx bucket list` documentation](/v2.0/reference/cli/influx/bucket/list) +See the [`influx bucket list` documentation](/influxdb/v2.0/reference/cli/influx/bucket/list) for information about other available flags. diff --git a/content/influxdb/v2.0/organizations/create-org.md b/content/influxdb/v2.0/organizations/create-org.md index 37b9fb000..afdbc59cd 100644 --- a/content/influxdb/v2.0/organizations/create-org.md +++ b/content/influxdb/v2.0/organizations/create-org.md @@ -31,7 +31,7 @@ Only the default organization is available. ## Create an organization using the influx CLI -Use the [`influx org create` command](/v2.0/reference/cli/influx/org/create) +Use the [`influx org create` command](/influxdb/v2.0/reference/cli/influx/org/create) to create a new organization. A new organization requires the following: - A name for the organization diff --git a/content/influxdb/v2.0/organizations/delete-org.md b/content/influxdb/v2.0/organizations/delete-org.md index 638c0d5cd..734fee3bf 100644 --- a/content/influxdb/v2.0/organizations/delete-org.md +++ b/content/influxdb/v2.0/organizations/delete-org.md @@ -29,7 +29,7 @@ to delete an organization. ## Delete an organization using the influx CLI -Use the [`influx org delete` command](/v2.0/reference/cli/influx/org/delete) +Use the [`influx org delete` command](/influxdb/v2.0/reference/cli/influx/org/delete) to delete an organization. Deleting an organization requires the following: - The organization ID _(provided in the output of `influx org list`)_ diff --git a/content/influxdb/v2.0/organizations/members/add-member.md b/content/influxdb/v2.0/organizations/members/add-member.md index 987e5886d..d41c7fc44 100644 --- a/content/influxdb/v2.0/organizations/members/add-member.md +++ b/content/influxdb/v2.0/organizations/members/add-member.md @@ -14,7 +14,7 @@ aliases: Use the `influx` command line interface (CLI) to add a member to an organization. {{% cloud %}} -To manage members of an organization in {{< cloud-name >}}, see [Manage multiple users](/v2.0/account-management/multi-user/). +To manage members of an organization in {{< cloud-name >}}, see [Manage multiple users](/influxdb/v2.0/account-management/multi-user/). {{% /cloud %}} diff --git a/content/influxdb/v2.0/security/secrets/manage-secrets/delete.md b/content/influxdb/v2.0/security/secrets/manage-secrets/delete.md index 1ee098abd..b201d60cc 100644 --- a/content/influxdb/v2.0/security/secrets/manage-secrets/delete.md +++ b/content/influxdb/v2.0/security/secrets/manage-secrets/delete.md @@ -13,7 +13,7 @@ aliases: Delete secrets using the `influx` command line interface (CLI) or the InfluxDB API. ## Delete a secret using the influx CLI -Use the [`influx secret delete` command](/v2.0/reference/cli/influx/secret/delete/) +Use the [`influx secret delete` command](/influxdb/v2.0/reference/cli/influx/secret/delete/) to delete a secret key-value pair from your organization. Provide the secret key to delete with the `-k` or `--key` flag. @@ -31,8 +31,8 @@ to delete one or more secrets. **Include the following:** -- Your [organization ID](/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL -- Your [authentication token](/v2.0/security/tokens/view-tokens/) in the `Authorization` header +- Your [organization ID](/influxdb/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL +- Your [authentication token](/influxdb/v2.0/security/tokens/view-tokens/) in the `Authorization` header - An array of secret keys to delete in the request body diff --git a/content/influxdb/v2.0/security/secrets/manage-secrets/update.md b/content/influxdb/v2.0/security/secrets/manage-secrets/update.md index c0727bca0..48e38213e 100644 --- a/content/influxdb/v2.0/security/secrets/manage-secrets/update.md +++ b/content/influxdb/v2.0/security/secrets/manage-secrets/update.md @@ -13,7 +13,7 @@ aliases: Update secrets using the `influx` command line interface (CLI) or the InfluxDB API. ## Update a secret using the influx CLI -Use the [`influx secret update` command](/v2.0/reference/cli/influx/secret/update/) +Use the [`influx secret update` command](/influxdb/v2.0/reference/cli/influx/secret/update/) to update a secret in your organization. Provide the secret key to update with the `-k` or `--key` flag. You may also provide the secret value with the `-v` or `--value` flag. @@ -39,8 +39,8 @@ to update a secret in your organization. **Include the following:** -- Your [organization ID](/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL -- Your [authentication token](/v2.0/security/tokens/view-tokens/) in the `Authorization` header +- Your [organization ID](/influxdb/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL +- Your [authentication token](/influxdb/v2.0/security/tokens/view-tokens/) in the `Authorization` header - The updated secret key-value pair in the request body diff --git a/content/influxdb/v2.0/security/secrets/manage-secrets/view.md b/content/influxdb/v2.0/security/secrets/manage-secrets/view.md index 2010032f4..0248b5980 100644 --- a/content/influxdb/v2.0/security/secrets/manage-secrets/view.md +++ b/content/influxdb/v2.0/security/secrets/manage-secrets/view.md @@ -13,7 +13,7 @@ aliases: View secret keys using the `influx` command line interface (CLI) or the InfluxDB API. ## View secret keys using the influx CLI -Use the [`influx secret list` command](/v2.0/reference/cli/influx/secret/list/) +Use the [`influx secret list` command](/influxdb/v2.0/reference/cli/influx/secret/list/) to list your organization's secret keys. ```sh @@ -26,8 +26,8 @@ to view your organization's secrets keys. **Include the following:** -- Your [organization ID](/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL -- Your [authentication token](/v2.0/security/tokens/view-tokens/) in the `Authorization` header +- Your [organization ID](/influxdb/v2.0/organizations/view-orgs/#view-your-organization-id) in the request URL +- Your [authentication token](/influxdb/v2.0/security/tokens/view-tokens/) in the `Authorization` header ```sh diff --git a/content/influxdb/v2.0/security/secrets/use-vault.md b/content/influxdb/v2.0/security/secrets/use-vault.md index c663a34bd..d52f61f56 100644 --- a/content/influxdb/v2.0/security/secrets/use-vault.md +++ b/content/influxdb/v2.0/security/secrets/use-vault.md @@ -19,8 +19,8 @@ Store sensitive secrets in Vault using InfluxDB's built-in Vault integration. By default, all secrets added to **InfluxDB Cloud** are stored in the **InfluxDB Cloud Vault cluster**. -For more on adding and using secrets, see [Manage secrets](/v2.0/security/secrets/manage-secrets/). -Once added, use the [`secrets.get()`](/v2.0/reference/flux/stdlib/secrets/get/) function to retrieve secrets for use in Flux scripts. +For more on adding and using secrets, see [Manage secrets](/influxdb/v2.0/security/secrets/manage-secrets/). +Once added, use the [`secrets.get()`](/influxdb/v2.0/reference/flux/stdlib/secrets/get/) function to retrieve secrets for use in Flux scripts. ## Use Vault with InfluxDB OSS @@ -58,19 +58,19 @@ to provide connection credentials and other important Vault-related information ##### Vault address Provide the API address of your Vault server _(available in the Vault server output)_ -using the [`--vault-addr` flag](/v2.0/reference/config-options/#vault-addr) when +using the [`--vault-addr` flag](/influxdb/v2.0/reference/config-options/#vault-addr) when starting `influxd` or with the `VAULT_ADDR` environment variable. ##### Vault token Provide your [Vault token](https://learn.hashicorp.com/vault/getting-started/authentication) -(required to access your Vault server) using the [`--vault-token` flag](/v2.0/reference/config-options/#vault-token) +(required to access your Vault server) using the [`--vault-token` flag](/influxdb/v2.0/reference/config-options/#vault-token) when starting `influxd` or with the `VAULT_TOKEN` environment variable. _Your Vault server configuration may require other Vault settings._ ### Start InfluxDB -Start the [`influxd` service](/v2.0/reference/cli/influxd/) with the `--secret-store` +Start the [`influxd` service](/influxdb/v2.0/reference/cli/influxd/) with the `--secret-store` option set to `vault` any other necessary flags. ```bash @@ -93,8 +93,8 @@ If set, these flags override any [Vault environment variables](https://www.vault - `--vault-tls-server-name` - `--vault-token` -For more information, see [InfluxDB configuration options](/v2.0/reference/config-options/). +For more information, see [InfluxDB configuration options](/influxdb/v2.0/reference/config-options/). ### Manage secrets through the InfluxDB API Use the InfluxDB `/org/{orgID}/secrets` API endpoint to add tokens to Vault. -For details, see [Manage secrets](/v2.0/security/secrets/manage-secrets/). +For details, see [Manage secrets](/influxdb/v2.0/security/secrets/manage-secrets/). diff --git a/content/influxdb/v2.0/security/tokens/create-token.md b/content/influxdb/v2.0/security/tokens/create-token.md index b193b3d7b..53f420617 100644 --- a/content/influxdb/v2.0/security/tokens/create-token.md +++ b/content/influxdb/v2.0/security/tokens/create-token.md @@ -34,9 +34,9 @@ Tokens are visible only to the user who created them and stop working when the u ## Create a token using the influx CLI -Use the [`influx auth create` command](/v2.0/reference/cli/influx/auth/create) to create a token. +Use the [`influx auth create` command](/influxdb/v2.0/reference/cli/influx/auth/create) to create a token. Include flags with the command to grant specific permissions to the token. -See the [available flags](/v2.0/reference/cli/influx/auth/create#flags). +See the [available flags](/influxdb/v2.0/reference/cli/influx/auth/create#flags). ```sh # Syntax @@ -52,5 +52,5 @@ influx auth create -o my-org \ ``` Filtering options such as filtering by authorization ID, username, or user ID are available. -See the [`influx auth list` documentation](/v2.0/reference/cli/influx/auth/list) +See the [`influx auth list` documentation](/influxdb/v2.0/reference/cli/influx/auth/list) for information about other available flags. diff --git a/content/influxdb/v2.0/security/tokens/delete-token.md b/content/influxdb/v2.0/security/tokens/delete-token.md index 383037765..d2d463d4e 100644 --- a/content/influxdb/v2.0/security/tokens/delete-token.md +++ b/content/influxdb/v2.0/security/tokens/delete-token.md @@ -27,7 +27,7 @@ have access to your InfluxDB instance. ## Delete tokens using the influx CLI -Use the [`influx auth delete` command](/v2.0/reference/cli/influx/auth/delete) +Use the [`influx auth delete` command](/influxdb/v2.0/reference/cli/influx/auth/delete) to delete a token. _This command requires an auth ID, which is available in the output of `influx auth find`._ diff --git a/content/influxdb/v2.0/security/tokens/view-tokens.md b/content/influxdb/v2.0/security/tokens/view-tokens.md index c07aad9de..5b85ec624 100644 --- a/content/influxdb/v2.0/security/tokens/view-tokens.md +++ b/content/influxdb/v2.0/security/tokens/view-tokens.md @@ -30,7 +30,7 @@ Tokens are visible only to the user who created them and stop working when the u ## View tokens using the influx CLI -Use the [`influx auth list` command](/v2.0/reference/cli/influx/auth/list) +Use the [`influx auth list` command](/influxdb/v2.0/reference/cli/influx/auth/list) to view tokens. ```sh @@ -38,5 +38,5 @@ influx auth list ``` Filtering options such as filtering by authorization ID, username, or user ID are available. -See the [`influx auth list` documentation](/v2.0/reference/cli/influx/auth/list) +See the [`influx auth list` documentation](/influxdb/v2.0/reference/cli/influx/auth/list) for information about other available flags. diff --git a/content/influxdb/v2.0/telegraf-configs/_index.md b/content/influxdb/v2.0/telegraf-configs/_index.md index 557d02823..56edeaafc 100644 --- a/content/influxdb/v2.0/telegraf-configs/_index.md +++ b/content/influxdb/v2.0/telegraf-configs/_index.md @@ -29,7 +29,7 @@ the configuration from an InfluxDB HTTP(S) endpoint. ``` {{% note %}} -_[Setup instructions](/v2.0/telegraf-configs/view/#view-setup-instructions) for +_[Setup instructions](/influxdb/v2.0/telegraf-configs/view/#view-setup-instructions) for each Telegraf configuration are provided in the InfluxDB UI._ {{% /note %}} diff --git a/content/influxdb/v2.0/telegraf-configs/create.md b/content/influxdb/v2.0/telegraf-configs/create.md index 9387dcfba..d80687e37 100644 --- a/content/influxdb/v2.0/telegraf-configs/create.md +++ b/content/influxdb/v2.0/telegraf-configs/create.md @@ -1,7 +1,7 @@ --- title: Create a Telegraf configuration description: > - Use the InfluxDB UI or the [`influx` CLI](/v2.0/reference/cli/influx/) + Use the InfluxDB UI or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to create an Telegraf configuration. weight: 101 aliases: @@ -16,7 +16,7 @@ related: - /influxdb/v2.0/telegraf-configs/update/ --- -Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) +Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to create a Telegraf configuration. To create a Telegraf configuration, do one of the following: @@ -29,15 +29,15 @@ To create a Telegraf configuration, do one of the following: Use the InfluxDB UI to automatically generate and store new Telegraf configurations in InfluxDB. Creating the configuration in the UI lets you select from a list of available technologies and generates a Telegraf configuration to collect metrics from those technologies. -For more information, see [Automatically configure Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/). +For more information, see [Automatically configure Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/). Telegraf has an extensive list of plugins for many different technologies and use cases. Not all plugins are available through the InfluxDB UI, but you can [create and upload custom Telegraf configurations](#create-a-custom-telegraf-configuration) -that include any of the available [Telegraf plugins](/v2.0/reference/telegraf-plugins). +that include any of the available [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins). ## Use the influx CLI -Use the [`influx telegrafs create` command](/v2.0/reference/cli/influx/telegrafs/create/) +Use the [`influx telegrafs create` command](/influxdb/v2.0/reference/cli/influx/telegrafs/create/) to upload a Telegraf configuration file from your local machine and create a new Telegraf configuration in InfluxDB. @@ -69,8 +69,8 @@ influx telegrafs create \ ## Create a custom Telegraf configuration 1. Create a custom Telegraf configuration file that includes the `outputs.influxdb_v2` - output plugin. _See [Manually configure Telegraf](/v2.0/write-data/no-code/use-telegraf/manual-config/)_ + output plugin. _See [Manually configure Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config/)_ for more information. -2. Add and customize [Telegraf plugins](/v2.0/reference/telegraf-plugins) and save your changes. +2. Add and customize [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins) and save your changes. 3. [Use the `influx telegrafs create` command](#use-the-influx-cli) to upload your custom Telegraf configuration to InfluxDB. diff --git a/content/influxdb/v2.0/telegraf-configs/remove.md b/content/influxdb/v2.0/telegraf-configs/remove.md index bc5845f70..feb414698 100644 --- a/content/influxdb/v2.0/telegraf-configs/remove.md +++ b/content/influxdb/v2.0/telegraf-configs/remove.md @@ -1,7 +1,7 @@ --- title: Remove a Telegraf configuration description: > - Use the InfluxDB UI or the [`influx` CLI](/v2.0/reference/cli/influx/) + Use the InfluxDB UI or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to remove Telegraf configurations from InfluxDB. weight: 104 menu: @@ -14,7 +14,7 @@ aliases: - /v2.0/telegraf-configs/remove/ --- -Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) +Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to remove Telegraf configurations from InfluxDB. {{% note %}} @@ -38,7 +38,7 @@ To remove a Telegraf configuration, do one of the following: ## Use the influx CLI -Use the [`influx telegrafs rm` command](/v2.0/reference/cli/influx/telegrafs/rm/) +Use the [`influx telegrafs rm` command](/influxdb/v2.0/reference/cli/influx/telegrafs/rm/) to remove a Telegraf configuration from InfluxDB. Provide the following: diff --git a/content/influxdb/v2.0/telegraf-configs/update.md b/content/influxdb/v2.0/telegraf-configs/update.md index b8015065c..dad95cf0f 100644 --- a/content/influxdb/v2.0/telegraf-configs/update.md +++ b/content/influxdb/v2.0/telegraf-configs/update.md @@ -1,7 +1,7 @@ --- title: Update a Telegraf configuration description: > - Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) + Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to update InfluxDB Telegraf configurations. weight: 103 menu: @@ -14,7 +14,7 @@ aliases: - /v2.0/telegraf-configs/update/ --- -Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) +Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to update InfluxDB Telegraf configurations. To update a Telegraf configuration, do one of the following: @@ -42,7 +42,7 @@ To modify existing Telegraf configuration settings, 3. Press **Return** or click out of the editable field to save your changes. ## Use the influx CLI -Use the [`influx telegrafs update` command](/v2.0/reference/cli/influx/telegrafs/update/) +Use the [`influx telegrafs update` command](/influxdb/v2.0/reference/cli/influx/telegrafs/update/) to update an existing InfluxDB Telegraf configuration name, description, or settings from a Telegraf configuration file on your local machine. @@ -82,7 +82,7 @@ influx telegrafs update \ 2. Click the **name** of the Telegraf configuration to customize. 3. Click **Download Config** to download the Telegraf configuration file to your local machine. -4. Add or update [Telegraf plugin](/v2.0/reference/telegraf-plugins) settings and +4. Add or update [Telegraf plugin](/influxdb/v2.0/reference/telegraf-plugins) settings and save your changes. 5. [Use the `influx telegrafs update` command](#use-the-influx-cli) to upload your modified Telegraf configuration to InfluxDB and replace the existing configuration. diff --git a/content/influxdb/v2.0/telegraf-configs/view.md b/content/influxdb/v2.0/telegraf-configs/view.md index f892920ec..cc5d7e1ac 100644 --- a/content/influxdb/v2.0/telegraf-configs/view.md +++ b/content/influxdb/v2.0/telegraf-configs/view.md @@ -1,7 +1,7 @@ --- title: View Telegraf configurations description: > - Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) + Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to view and download InfluxDB Telegraf configurations. weight: 102 menu: @@ -14,7 +14,7 @@ aliases: - /v2.0/telegraf-configs/view/ --- -Use the InfluxDB user interface (UI) or the [`influx` CLI](/v2.0/reference/cli/influx/) +Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to view and download InfluxDB Telegraf configurations. To view Telegraf configurations, do one of the following: @@ -38,7 +38,7 @@ Setup instructions include commands for adding your InfluxDB authentication toke as an environment variable and starting Telegraf with the specific configuration. ## Use the influx CLI -Use the [`influx telegrafs` command](/v2.0/reference/cli/influx/telegrafs/) to +Use the [`influx telegrafs` command](/influxdb/v2.0/reference/cli/influx/telegrafs/) to list Telegraf configurations stored in InfluxDB. ```sh diff --git a/content/influxdb/v2.0/tools/repl.md b/content/influxdb/v2.0/tools/repl.md index 8754af934..3c40ff1c3 100644 --- a/content/influxdb/v2.0/tools/repl.md +++ b/content/influxdb/v2.0/tools/repl.md @@ -26,7 +26,7 @@ To open a new REPL session, run: ``` To query data from InfluxDB (local or remote), provide the host, organization, and token parameters -to the [`from()` function](/v2.0/reference/flux/stdlib/built-in/inputs/from/). +to the [`from()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/from/). ```js from(bucket: "example-bucket", diff --git a/content/influxdb/v2.0/users/_index.md b/content/influxdb/v2.0/users/_index.md index 9e64abc2d..103d6c30a 100644 --- a/content/influxdb/v2.0/users/_index.md +++ b/content/influxdb/v2.0/users/_index.md @@ -13,8 +13,8 @@ products: [oss] --- Users are those with access to InfluxDB. -To grant a user permission to access data, add them as a [member of an organization](/v2.0/organizations/members/) -and provide them with an [authentication token](/v2.0/security/tokens/). +To grant a user permission to access data, add them as a [member of an organization](/influxdb/v2.0/organizations/members/) +and provide them with an [authentication token](/influxdb/v2.0/security/tokens/). The following articles walk through managing users. diff --git a/content/influxdb/v2.0/users/change-password.md b/content/influxdb/v2.0/users/change-password.md index fecc76372..76e4e3191 100644 --- a/content/influxdb/v2.0/users/change-password.md +++ b/content/influxdb/v2.0/users/change-password.md @@ -19,7 +19,7 @@ User passwords cannot be updated in the InfluxDB UI. ## Change your password using the influx CLI -Use the [`influx user password` command](/v2.0/reference/cli/influx/user/password) +Use the [`influx user password` command](/influxdb/v2.0/reference/cli/influx/user/password) to update a password for a user. To update a password, you need the following: - Username or user ID _(provided in the output of `influx user list`)_ diff --git a/content/influxdb/v2.0/users/create-user.md b/content/influxdb/v2.0/users/create-user.md index 09c648aaf..0fa969c69 100644 --- a/content/influxdb/v2.0/users/create-user.md +++ b/content/influxdb/v2.0/users/create-user.md @@ -23,12 +23,12 @@ Additional users cannot be created in the InfluxDB UI. ## Create a user using the influx CLI -To create a new user, use the [`influx user create` command](/v2.0/reference/cli/influx/user/create) +To create a new user, use the [`influx user create` command](/influxdb/v2.0/reference/cli/influx/user/create) and include the following: - Username - Organization name or organization ID to add the user to _(provided in the output of - [`influx org list`](/v2.0/reference/cli/influx/org/list/))_ + [`influx org list`](/influxdb/v2.0/reference/cli/influx/org/list/))_ ```sh # Syntax @@ -44,7 +44,7 @@ include a password and organization ID with the `influx user create` command. - Username - Organization name or organization ID to add the user to _(provided in the output of - [`influx org list`](/v2.0/reference/cli/influx/org/list/))_ + [`influx org list`](/influxdb/v2.0/reference/cli/influx/org/list/))_ - Password ```sh diff --git a/content/influxdb/v2.0/users/delete-user.md b/content/influxdb/v2.0/users/delete-user.md index cc900c570..ace1138d5 100644 --- a/content/influxdb/v2.0/users/delete-user.md +++ b/content/influxdb/v2.0/users/delete-user.md @@ -18,7 +18,7 @@ to delete a user. {{% warn %}} Deleting a user removes them completely from InfluxDB. To remove a user from an organization without deleting the user entirely, see -[Remove a member from an organization](/v2.0/organizations/members/remove-member/). +[Remove a member from an organization](/influxdb/v2.0/organizations/members/remove-member/). {{% /warn %}} ## Delete a user from the InfluxDB UI @@ -29,7 +29,7 @@ Users cannot be deleted from the InfluxDB UI. ## Delete a user using the influx CLI -Use the [`influx user delete` command](/v2.0/reference/cli/influx/user/delete) +Use the [`influx user delete` command](/influxdb/v2.0/reference/cli/influx/user/delete) to delete a user. Deleting a user requires the following: - The user ID _(provided in the output of `influx user list`)_ diff --git a/content/influxdb/v2.0/users/update-user.md b/content/influxdb/v2.0/users/update-user.md index c02215756..50db994d2 100644 --- a/content/influxdb/v2.0/users/update-user.md +++ b/content/influxdb/v2.0/users/update-user.md @@ -23,7 +23,7 @@ User information cannot be updated in the InfluxDB UI. ## Update a user using the influx CLI -Use the [`influx user update` command](/v2.0/reference/cli/influx/user/update) +Use the [`influx user update` command](/influxdb/v2.0/reference/cli/influx/user/update) to update a user. Updating a user requires the following: - The user ID _(provided in the output of `influx user list`)_ diff --git a/content/influxdb/v2.0/users/view-users.md b/content/influxdb/v2.0/users/view-users.md index a2767eb2d..4ba469d81 100644 --- a/content/influxdb/v2.0/users/view-users.md +++ b/content/influxdb/v2.0/users/view-users.md @@ -23,7 +23,7 @@ There is no list of users in the InfluxDB UI. ## View users using the influx CLI -Use the [`influx user list` command](/v2.0/reference/cli/influx/user/list) +Use the [`influx user list` command](/influxdb/v2.0/reference/cli/influx/user/list) to view users. ```sh @@ -31,5 +31,5 @@ influx user list ``` Filtering options such as filtering by username or ID are available. -See the [`influx user list` documentation](/v2.0/reference/cli/influx/user/list) +See the [`influx user list` documentation](/influxdb/v2.0/reference/cli/influx/user/list) for information about other available flags. diff --git a/content/influxdb/v2.0/visualize-data/dashboards/_index.md b/content/influxdb/v2.0/visualize-data/dashboards/_index.md index a2d532694..dff0aa5db 100644 --- a/content/influxdb/v2.0/visualize-data/dashboards/_index.md +++ b/content/influxdb/v2.0/visualize-data/dashboards/_index.md @@ -29,7 +29,7 @@ http://localhost:9999/orgs/03a2bbf46249a000/dashboards/}} Add Cell** to open the Data Explorer and configure a new cell for your dashboard. -For details on using the Data Explorer, see [Explore metrics](/v2.0/visualize-data/explore-metrics/). +For details on using the Data Explorer, see [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics/). ### Add a note @@ -58,7 +58,7 @@ The default time range is 5 minutes. ### Add variables -Click **Variables** to display variables available for your dashboard. For details, see [Use and manage variables](/v2.0/visualize-data/variables/) +Click **Variables** to display variables available for your dashboard. For details, see [Use and manage variables](/influxdb/v2.0/visualize-data/variables/) ### Presentation mode diff --git a/content/influxdb/v2.0/visualize-data/dashboards/create-dashboard.md b/content/influxdb/v2.0/visualize-data/dashboards/create-dashboard.md index e3e5ccff7..5b6aadafc 100644 --- a/content/influxdb/v2.0/visualize-data/dashboards/create-dashboard.md +++ b/content/influxdb/v2.0/visualize-data/dashboards/create-dashboard.md @@ -75,10 +75,10 @@ aliases: #### Add data to your dashboard 1. From your dashboard, click **{{< icon "add-cell" >}} Add Cell**. -2. Create a query in the Data Explorer following the instructions in [Explore metrics](/v2.0/visualize-data/explore-metrics). +2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics). 3. Enter a name for your cell in the upper left. 4. Click the checkmark icon (**{{< icon "checkmark" >}}**) to save the cell to your dashboard. -You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/v2.0/visualize-data/explore-metrics). +You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics). #### Add a note to your dashboard 1. From your dashboard, click **{{< icon "note" >}} Add Note** in the upper left. diff --git a/content/influxdb/v2.0/visualize-data/explore-metrics.md b/content/influxdb/v2.0/visualize-data/explore-metrics.md index 075d4dab5..2fbd2ef2a 100644 --- a/content/influxdb/v2.0/visualize-data/explore-metrics.md +++ b/content/influxdb/v2.0/visualize-data/explore-metrics.md @@ -16,7 +16,7 @@ aliases: Explore and visualize your data in the **Data Explorer**. The InfluxDB user interface (UI) allows you to move seamlessly between using the Flux builder or templates and manually editing the query. -Choose between [visualization types](/v2.0/visualize-data/visualization-types/) for your query. +Choose between [visualization types](/influxdb/v2.0/visualize-data/visualization-types/) for your query. To open the **Data Explorer**, click the **Explore** (**Data Explorer**) icon in the left navigation menu: @@ -26,7 +26,7 @@ To open the **Data Explorer**, click the **Explore** (**Data Explorer**) icon in Flux is InfluxData's functional data scripting language designed for querying, analyzing, and acting on time series data. -See [Get started with Flux](/v2.0/query-data/get-started) to learn more about Flux. +See [Get started with Flux](/influxdb/v2.0/query-data/get-started) to learn more about Flux. 1. In the navigation menu on the left, select **Explore** (**Data Explorer**). @@ -36,7 +36,7 @@ See [Get started with Flux](/v2.0/query-data/get-started) to learn more about Fl - Select a bucket to define your data source or select `+ Create Bucket` to add a new bucket. - Edit your time range with the [time range option](#select-time-range) in the dropdown menu. - Add filters to narrow your data by selecting attributes or columns in the dropdown menu. - - Select **Group** from the **Filter** dropdown menu to group data into tables. For more about how grouping data in Flux works, see [Group data](/v2.0/query-data/flux/group-data/). + - Select **Group** from the **Filter** dropdown menu to group data into tables. For more about how grouping data in Flux works, see [Group data](/influxdb/v2.0/query-data/flux/group-data/). 3. Alternatively, click **Script Editor** to manually edit the query. To switch back to the query builder, click **Query Builder**. Note that your updates from the Script Editor will not be saved. 4. Use the **Functions** list to review the available Flux functions. @@ -49,7 +49,7 @@ See [Get started with Flux](/v2.0/query-data/get-started) to learn more about Fl ## Visualize your query -- Select an available [visualization types](/v2.0/visualize-data/visualization-types/) from the dropdown menu in the upper-left: +- Select an available [visualization types](/influxdb/v2.0/visualize-data/visualization-types/) from the dropdown menu in the upper-left: {{< img-hd src="/img/2-0-visualizations-dropdown.png" title="Visualization dropdown" />}} diff --git a/content/influxdb/v2.0/visualize-data/other-tools/grafana.md b/content/influxdb/v2.0/visualize-data/other-tools/grafana.md index 4e1760ab4..03a987090 100644 --- a/content/influxdb/v2.0/visualize-data/other-tools/grafana.md +++ b/content/influxdb/v2.0/visualize-data/other-tools/grafana.md @@ -23,8 +23,8 @@ to visualize data from **InfluxDB 2.0** and **{{< cloud-name "short" >}}**. The instructions in this guide require **Grafana Cloud** or **Grafana v7.1+**. {{% /note %}} -1. [Sign up for {{< cloud-name >}}](/v2.0/get-started/) or - [start InfluxDB 2.0 OSS](/v2.0/get-started/#start-with-influxdb-oss). +1. [Sign up for {{< cloud-name >}}](/influxdb/v2.0/get-started/) or + [start InfluxDB 2.0 OSS](/influxdb/v2.0/get-started/#start-with-influxdb-oss). 2. [Sign up for Grafana Cloud](https://grafana.com/products/cloud/) or [download and install Grafana](https://grafana.com/grafana/download). 3. Visit your **Grafana Cloud user interface** (UI) or, if running Grafana locally, @@ -50,15 +50,15 @@ configure your InfluxDB connection: 1. Under **Connection**, enter the following: - - **URL**: Your [InfluxDB URL](/v2.0/reference/urls/) **with the `/api/v2` path**. + - **URL**: Your [InfluxDB URL](/influxdb/v2.0/reference/urls/) **with the `/api/v2` path**. ```sh http://localhost:9999/api/v2 ``` - - **Organization**: Your InfluxDB [organization name **or** ID](/v2.0/organizations/view-orgs/). - - **Token**: Your InfluxDB [authentication token](/v2.0/security/tokens/). - - **Default Bucket**: The default [bucket](/v2.0/organizations/buckets/) to use in Flux queries. + - **Organization**: Your InfluxDB [organization name **or** ID](/influxdb/v2.0/organizations/view-orgs/). + - **Token**: Your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/). + - **Default Bucket**: The default [bucket](/influxdb/v2.0/organizations/buckets/) to use in Flux queries. - **Min time interval**: The [Grafana minimum time interval](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#min-time-interval). {{< img-hd src="/img/2-0-visualize-grafana.png" />}} @@ -80,7 +80,7 @@ configure your InfluxDB connection: 1. Under **HTTP**, enter the following: - - **URL**: Your [InfluxDB URL](/v2.0/reference/urls/). + - **URL**: Your [InfluxDB URL](/influxdb/v2.0/reference/urls/). ```sh https://cloud2.influxdata.com @@ -91,12 +91,12 @@ configure your InfluxDB connection: 3. Under **Basic Auth Details**, provide your InfluxDB authentication credentials: - **username**: InfluxDB username - - **password**: InfluxDB [authentication token](/v2.0/security/tokens/) + - **password**: InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) 4. Under **InfluxDB details**, set the following: - **Database**: The database to use when querying InfluxDB 2.0. - _See [Database and retention policy mapping](/v2.0/reference/api/influxdb-1x/dbrp/)._ + _See [Database and retention policy mapping](/influxdb/v2.0/reference/api/influxdb-1x/dbrp/)._ - **HTTP Method**: Select **GET**. - **Min time interval**: The [Grafana minimum time interval](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#min-time-interval). @@ -113,4 +113,4 @@ With your InfluxDB connection configured, use Grafana and Flux to query and visualize time series data stored in **InfluxDB 2.0** or **{{< cloud-name >}}**. For more information about using Grafana, see the [Grafana documentation](https://grafana.com/docs/). -If you're just learning Flux, see [Get started with Flux](/v2.0/query-data/get-started/). +If you're just learning Flux, see [Get started with Flux](/influxdb/v2.0/query-data/get-started/). diff --git a/content/influxdb/v2.0/visualize-data/templates/create-template.md b/content/influxdb/v2.0/visualize-data/templates/create-template.md index 484c0b729..16bdeee31 100644 --- a/content/influxdb/v2.0/visualize-data/templates/create-template.md +++ b/content/influxdb/v2.0/visualize-data/templates/create-template.md @@ -26,7 +26,7 @@ aliases: ## Clone a dashboard template {{% note %}} -Only [user templates](/v2.0/visualize-data/templates/#dashboard-template-types) can be cloned. +Only [user templates](/influxdb/v2.0/visualize-data/templates/#dashboard-template-types) can be cloned. {{% /note %}} 1. In the navigation menu on the left, select **Settings** > **Templates**. diff --git a/content/influxdb/v2.0/visualize-data/templates/use-template.md b/content/influxdb/v2.0/visualize-data/templates/use-template.md index d03f172a7..5910f474c 100644 --- a/content/influxdb/v2.0/visualize-data/templates/use-template.md +++ b/content/influxdb/v2.0/visualize-data/templates/use-template.md @@ -18,7 +18,7 @@ To create a new dashboard from an InfluxDB dashboard template: {{< nav-icon "settings" >}} -3. Select the [template type](/v2.0/visualize-data/templates/#dashboard-template-types). +3. Select the [template type](/influxdb/v2.0/visualize-data/templates/#dashboard-template-types). {{< img-hd src="/img/2-0-templates-type-select.png" alt="Select User Templates" />}} diff --git a/content/influxdb/v2.0/visualize-data/templates/view-template.md b/content/influxdb/v2.0/visualize-data/templates/view-template.md index d757959e3..d4fd310e0 100644 --- a/content/influxdb/v2.0/visualize-data/templates/view-template.md +++ b/content/influxdb/v2.0/visualize-data/templates/view-template.md @@ -60,14 +60,14 @@ It displays the following information: - Scoreboard #### Plugins -- [`apache` plugin](/v2.0/reference/telegraf-plugins/#apache) -- [`cpu` plugin](/v2.0/reference/telegraf-plugins/#cpu) -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) -- [`diskio` plugin](/v2.0/reference/telegraf-plugins/#diskio) -- [`mem` plugin](/v2.0/reference/telegraf-plugins/#mem) -- [`net` plugin](/v2.0/reference/telegraf-plugins/#net) -- [`netstat` plugin](/v2.0/reference/telegraf-plugins/#netstat) -- [`system` plugin](/v2.0/reference/telegraf-plugins/#system) +- [`apache` plugin](/influxdb/v2.0/reference/telegraf-plugins/#apache) +- [`cpu` plugin](/influxdb/v2.0/reference/telegraf-plugins/#cpu) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) +- [`diskio` plugin](/influxdb/v2.0/reference/telegraf-plugins/#diskio) +- [`mem` plugin](/influxdb/v2.0/reference/telegraf-plugins/#mem) +- [`net` plugin](/influxdb/v2.0/reference/telegraf-plugins/#net) +- [`netstat` plugin](/influxdb/v2.0/reference/telegraf-plugins/#netstat) +- [`system` plugin](/influxdb/v2.0/reference/telegraf-plugins/#system) ### Docker The Docker dashboard template contains an overview of Docker metrics. @@ -94,13 +94,13 @@ It displays the following information: #### Plugins -- [`cpu` plugin](/v2.0/reference/telegraf-plugins/#cpu) -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) -- [`diskio` plugin](/v2.0/reference/telegraf-plugins/#diskio) +- [`cpu` plugin](/influxdb/v2.0/reference/telegraf-plugins/#cpu) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) +- [`diskio` plugin](/influxdb/v2.0/reference/telegraf-plugins/#diskio) - [`docker` plugin](//v2.0/reference/telegraf-plugins/#docker) -- [`mem` plugin](/v2.0/reference/telegraf-plugins/#mem) -- [`swap` plugin](/v2.0/reference/telegraf-plugins/#swap) -- [`system` plugin](/v2.0/reference/telegraf-plugins/#system) +- [`mem` plugin](/influxdb/v2.0/reference/telegraf-plugins/#mem) +- [`swap` plugin](/influxdb/v2.0/reference/telegraf-plugins/#swap) +- [`system` plugin](/influxdb/v2.0/reference/telegraf-plugins/#system) ### Getting Started with Flux This dashboard is designed to get you started with the Flux language. @@ -115,8 +115,8 @@ It contains explanations and visualizations for a series of increasingly complex #### Plugins -- [`cpu` plugin](/v2.0/reference/telegraf-plugins/#cpu) -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) +- [`cpu` plugin](/influxdb/v2.0/reference/telegraf-plugins/#cpu) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) ### GitHub Data The GitHub Data dashboard template displays data related to GitHub repositories: @@ -132,7 +132,7 @@ The GitHub Data dashboard template displays data related to GitHub repositories: - Summary #### Plugins -- [`github` plugin](/v2.0/reference/telegraf-plugins/#github) +- [`github` plugin](/influxdb/v2.0/reference/telegraf-plugins/#github) ### InfluxDB 2.0 OSS Metrics @@ -192,7 +192,7 @@ It displays the following information: - Running Containers #### Plugins -- [`kubernetes` plugin](/v2.0/reference/telegraf-plugins/) +- [`kubernetes` plugin](/influxdb/v2.0/reference/telegraf-plugins/) ### Nginx The Nginx dashboard gives a visual overview of Nginx metrics. @@ -214,13 +214,13 @@ It displays the following information: #### Plugins -- [`cpu` plugin](/v2.0/reference/telegraf-plugins/#cpu) -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) -- [`diskio` plugin](/v2.0/reference/telegraf-plugins/#diskio) -- [`mem` plugin](/v2.0/reference/telegraf-plugins/#mem) -- [`nginx` plugin](/v2.0/reference/telegraf-plugins/#nginx) -- [`swap` plugin](/v2.0/reference/telegraf-plugins/#swap) -- [`system` plugin](/v2.0/reference/telegraf-plugins/#system) +- [`cpu` plugin](/influxdb/v2.0/reference/telegraf-plugins/#cpu) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) +- [`diskio` plugin](/influxdb/v2.0/reference/telegraf-plugins/#diskio) +- [`mem` plugin](/influxdb/v2.0/reference/telegraf-plugins/#mem) +- [`nginx` plugin](/influxdb/v2.0/reference/telegraf-plugins/#nginx) +- [`swap` plugin](/influxdb/v2.0/reference/telegraf-plugins/#swap) +- [`system` plugin](/influxdb/v2.0/reference/telegraf-plugins/#system) ### Redis The Redis dashboard gives a visual overview of Nginx metrics. @@ -246,12 +246,12 @@ It displays the following information: - Redis uptime #### Plugins -- [`cpu` plugin](/v2.0/reference/telegraf-plugins/#cpu) -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) -- [`mem` plugin](/v2.0/reference/telegraf-plugins/#mem) -- [`redis` plugin](/v2.0/reference/telegraf-plugins/#redis) -- [`swap` plugin](/v2.0/reference/telegraf-plugins/#swap) -- [`system` plugin](/v2.0/reference/telegraf-plugins/#system) +- [`cpu` plugin](/influxdb/v2.0/reference/telegraf-plugins/#cpu) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) +- [`mem` plugin](/influxdb/v2.0/reference/telegraf-plugins/#mem) +- [`redis` plugin](/influxdb/v2.0/reference/telegraf-plugins/#redis) +- [`swap` plugin](/influxdb/v2.0/reference/telegraf-plugins/#swap) +- [`system` plugin](/influxdb/v2.0/reference/telegraf-plugins/#system) ### System @@ -272,9 +272,9 @@ It displays the following information: - Swap #### Plugins -- [`disk` plugin](/v2.0/reference/telegraf-plugins/#disk) -- [`diskio` plugin](/v2.0/reference/telegraf-plugins/#diskio) -- [`mem` plugin](/v2.0/reference/telegraf-plugins/#mem) -- [`net` plugin](/v2.0/reference/telegraf-plugins/#net) -- [`swap` plugin](/v2.0/reference/telegraf-plugins/#swap) -- [`system` plugin](/v2.0/reference/telegraf-plugins/#system) +- [`disk` plugin](/influxdb/v2.0/reference/telegraf-plugins/#disk) +- [`diskio` plugin](/influxdb/v2.0/reference/telegraf-plugins/#diskio) +- [`mem` plugin](/influxdb/v2.0/reference/telegraf-plugins/#mem) +- [`net` plugin](/influxdb/v2.0/reference/telegraf-plugins/#net) +- [`swap` plugin](/influxdb/v2.0/reference/telegraf-plugins/#swap) +- [`system` plugin](/influxdb/v2.0/reference/telegraf-plugins/#system) diff --git a/content/influxdb/v2.0/visualize-data/variables/_index.md b/content/influxdb/v2.0/visualize-data/variables/_index.md index 2b646b877..7f37a0aae 100644 --- a/content/influxdb/v2.0/visualize-data/variables/_index.md +++ b/content/influxdb/v2.0/visualize-data/variables/_index.md @@ -46,14 +46,14 @@ The InfluxDB user interface (UI) provides the following predefined dashboard var #### v.timeRangeStart Specifies the beginning of the queried time range. -This variable is typically used to define the [`start` parameter](/v2.0/reference/flux/stdlib/built-in/transformations/range#start) +This variable is typically used to define the [`start` parameter](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range#start) of the `range()` function. The **Time Range** selector defines the value of this variable. #### v.timeRangeStop Specifies the end of the queried time range. -This variable is typically used to define the [`stop` parameter](/v2.0/reference/flux/stdlib/built-in/transformations/range#stop) +This variable is typically used to define the [`stop` parameter](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range#stop) of the `range()` function. The **Time Range** selector defines the value of this variable. @@ -62,7 +62,7 @@ It defaults to `now`. #### v.windowPeriod Specifies the period of windowed data. This variable is typically used to define the `every` or `period` parameters of the -[`window()` function](/v2.0/reference/flux/stdlib/built-in/transformations/window) +[`window()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/window) in data aggregation operations. The value of this variable is calculated by analyzing the duration of the Flux diff --git a/content/influxdb/v2.0/visualize-data/variables/common-variables.md b/content/influxdb/v2.0/visualize-data/variables/common-variables.md index df8b4d4f9..204a6fb71 100644 --- a/content/influxdb/v2.0/visualize-data/variables/common-variables.md +++ b/content/influxdb/v2.0/visualize-data/variables/common-variables.md @@ -15,9 +15,9 @@ influxdb/v2.0/tags: [variables] List all buckets in the current organization. _**Flux functions:** -[buckets()](/v2.0/reference/flux/stdlib/built-in/inputs/buckets/), -[rename()](/v2.0/reference/flux/stdlib/built-in/transformations/rename/), -[keep()](/v2.0/reference/flux/stdlib/built-in/transformations/keep/)_ +[buckets()](/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/buckets/), +[rename()](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/rename/), +[keep()](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keep/)_ ```js buckets() @@ -28,8 +28,8 @@ buckets() ## List measurements List all measurements in a specified bucket. -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/) -**Flux functions:** [v1.measurements()](/v2.0/reference/flux/stdlib/influxdb-v1/measurements/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/) +**Flux functions:** [v1.measurements()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurements/)_ ```js import "influxdata/influxdb/v1" @@ -39,8 +39,8 @@ v1.measurements(bucket: "bucket-name") ## List fields in a measurement List all fields in a specified bucket and measurement. -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/) -**Flux functions:** [v1.measurementTagValues()](/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/) +**Flux functions:** [v1.measurementTagValues()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ ```js import "influxdata/influxdb/v1" @@ -55,8 +55,8 @@ v1.measurementTagValues( List all unique tag values for a specific tag in a specified bucket. The example below lists all unique values of the `host` tag. -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/)_ -_**Flux functions:** [v1.tagValues()](/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/)_ +_**Flux functions:** [v1.tagValues()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues/)_ ```js import "influxdata/influxdb/v1" @@ -67,8 +67,8 @@ v1.tagValues(bucket: "bucket-name", tag: "host") List all Docker containers when using the Docker Telegraf plugin. _**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/inputs/#docker)_ -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/)_ -_**Flux functions:** [v1.tagValues()](/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/)_ +_**Flux functions:** [v1.tagValues()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues/)_ ```js import "influxdata/influxdb/v1" @@ -79,8 +79,8 @@ v1.tagValues(bucket: "bucket-name", tag: "container_name") List all Kubernetes pods when using the Kubernetes Telegraf plugin. _**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/inputs/#kubernetes)_ -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/)_ -_**Flux functions:** [v1.measurementTagValues()](/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/)_ +_**Flux functions:** [v1.measurementTagValues()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ ```js import "influxdata/influxdb/v1" @@ -95,8 +95,8 @@ v1.measurementTagValues( List all Kubernetes nodes when using the Kubernetes Telegraf plugin. _**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/inputs/#kubernetes)_ -_**Flux package:** [InfluxDB v1](/v2.0/reference/flux/stdlib/influxdb-v1/)_ -_**Flux functions:** [v1.measurementTagValues()](/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ +_**Flux package:** [InfluxDB v1](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/)_ +_**Flux functions:** [v1.measurementTagValues()](/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_ ```js import "influxdata/influxdb/v1" diff --git a/content/influxdb/v2.0/visualize-data/variables/create-variable.md b/content/influxdb/v2.0/visualize-data/variables/create-variable.md index 6d2d81653..29e7cda6f 100644 --- a/content/influxdb/v2.0/visualize-data/variables/create-variable.md +++ b/content/influxdb/v2.0/visualize-data/variables/create-variable.md @@ -15,7 +15,7 @@ Create dashboard variables in the Data Explorer, from the Settings section, or i **Variable names must be unique.** There are multiple variable types that provide different means of populating your list of variable values. -_For information about variable types, see [Variable types](/v2.0/visualize-data/variables/variable-types/)._ +_For information about variable types, see [Variable types](/influxdb/v2.0/visualize-data/variables/variable-types/)._ {{% note %}} ##### Variable name restrictions @@ -29,8 +29,8 @@ The following names cannot be used as dashboard variables because they are reser {{% note %}} InfluxData recommends using the Data Explorer to create -[Query dashboard variables](/v2.0/visualize-data/variables/variable-types/#query). -The [Table visualization type](/v2.0/visualize-data/visualization-types/table/) and +[Query dashboard variables](/influxdb/v2.0/visualize-data/variables/variable-types/#query). +The [Table visualization type](/influxdb/v2.0/visualize-data/visualization-types/table/) and **View Raw Data** option to provide human-readable query results. {{% /note %}} @@ -39,14 +39,14 @@ The [Table visualization type](/v2.0/visualize-data/visualization-types/table/) {{< nav-icon "data-explorer" >}} 2. Use the **Query Builder** or **Script Editor** to build a query. -3. Use the [Table visualization type](/v2.0/visualize-data/visualization-types/table/) +3. Use the [Table visualization type](/influxdb/v2.0/visualize-data/visualization-types/table/) or enable the **View Raw Data** option to view human-readable query results. 4. Click **Save As** in the upper right. 5. In the window that appears, select **Variable**. 6. Enter a name for your variable in the **Name** field. 7. Click **Create**. -_For information about common Query variables, see [Common variable queries](/v2.0/visualize-data/variables/common-variables/)._ +_For information about common Query variables, see [Common variable queries](/influxdb/v2.0/visualize-data/variables/common-variables/)._ ## Create a variable in the Settings section @@ -56,7 +56,7 @@ _For information about common Query variables, see [Common variable queries](/v2 2. Select the **Variables** tab. 3. Enter a name for your variable. -4. Select your variable type. For details on each type, see [Variable types](/v2.0/visualize-data/variables/variable-types/). +4. Select your variable type. For details on each type, see [Variable types](/influxdb/v2.0/visualize-data/variables/variable-types/). 5. Enter the appropriate variable information. 6. Click **Create**. diff --git a/content/influxdb/v2.0/visualize-data/variables/variable-types.md b/content/influxdb/v2.0/visualize-data/variables/variable-types.md index 9edfbb679..9d4950871 100644 --- a/content/influxdb/v2.0/visualize-data/variables/variable-types.md +++ b/content/influxdb/v2.0/visualize-data/variables/variable-types.md @@ -45,19 +45,19 @@ buckets() |> keep(columns: ["_value"]) ``` -_For examples of dashboard variable queries, see [Common variable queries](/v2.0/visualize-data/variables/common-variables)._ +_For examples of dashboard variable queries, see [Common variable queries](/influxdb/v2.0/visualize-data/variables/common-variables)._ {{% note %}} #### Important things to note about variable queries - The variable will only use values from the `_value` column. If the data you’re looking for is in a column other than `_value`, use the - [`rename()`](/v2.0/reference/flux/stdlib/built-in/transformations/rename/) or - [`map()`](/v2.0/reference/flux/stdlib/built-in/transformations/map/) functions + [`rename()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/rename/) or + [`map()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/map/) functions to change the name of that column to `_value`. - The variable will only use the first table in the output stream. - Use the [`group()` function](/v2.0/reference/flux/stdlib/built-in/transformations/group) + Use the [`group()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/group) to group everything into a single table. -- Do not use any [predefined dashboard variables](/v2.0/visualize-data/variables/#predefined-dashboard-variables) in variable queries. +- Do not use any [predefined dashboard variables](/influxdb/v2.0/visualize-data/variables/#predefined-dashboard-variables) in variable queries. {{% /note %}} ## CSV diff --git a/content/influxdb/v2.0/visualize-data/visualization-types/heatmap.md b/content/influxdb/v2.0/visualize-data/visualization-types/heatmap.md index 7606580d3..bd70db316 100644 --- a/content/influxdb/v2.0/visualize-data/visualization-types/heatmap.md +++ b/content/influxdb/v2.0/visualize-data/visualization-types/heatmap.md @@ -66,8 +66,8 @@ the visualization dropdown. ### Cross-measurement correlation The following example explores possible correlation between CPU and Memory usage. -It uses data collected with the Telegraf [Mem](/v2.0/reference/telegraf-plugins/#mem) -and [CPU](/v2.0/reference/telegraf-plugins/#cpu) input plugins. +It uses data collected with the Telegraf [Mem](/influxdb/v2.0/reference/telegraf-plugins/#mem) +and [CPU](/influxdb/v2.0/reference/telegraf-plugins/#cpu) input plugins. ###### Join CPU and memory usage The following query joins CPU and memory usage on `_time`. @@ -104,7 +104,7 @@ between column values. ## Important notes ### Differences between a heatmap and a scatter plot -Heatmaps and [Scatter plots](/v2.0/visualize-data/visualization-types/scatter/) +Heatmaps and [Scatter plots](/influxdb/v2.0/visualize-data/visualization-types/scatter/) both visualize the distribution of data points on X and Y axes. However, in certain cases, heatmaps provide better visibility into point density. diff --git a/content/influxdb/v2.0/visualize-data/visualization-types/histogram.md b/content/influxdb/v2.0/visualize-data/visualization-types/histogram.md index 56493428c..b8e077adc 100644 --- a/content/influxdb/v2.0/visualize-data/visualization-types/histogram.md +++ b/content/influxdb/v2.0/visualize-data/visualization-types/histogram.md @@ -63,7 +63,7 @@ the visualization dropdown. ### View error counts by severity over time The following example uses the Histogram visualization to show the number of errors "binned" by time and segmented by severity. -_It utilizes data from the [Telegraf Syslog plugin](/v2.0/reference/telegraf-plugins/#syslog)._ +_It utilizes data from the [Telegraf Syslog plugin](/influxdb/v2.0/reference/telegraf-plugins/#syslog)._ ##### Query for errors by severity code ```js diff --git a/content/influxdb/v2.0/visualize-data/visualization-types/scatter.md b/content/influxdb/v2.0/visualize-data/visualization-types/scatter.md index f1605db0f..f61829e63 100644 --- a/content/influxdb/v2.0/visualize-data/visualization-types/scatter.md +++ b/content/influxdb/v2.0/visualize-data/visualization-types/scatter.md @@ -58,8 +58,8 @@ the visualization dropdown. ### Cross-measurement correlation The following example explores possible correlation between CPU and Memory usage. -It uses data collected with the Telegraf [Mem](/v2.0/reference/telegraf-plugins/#mem) -and [CPU](/v2.0/reference/telegraf-plugins/#cpu) input plugins. +It uses data collected with the Telegraf [Mem](/influxdb/v2.0/reference/telegraf-plugins/#mem) +and [CPU](/influxdb/v2.0/reference/telegraf-plugins/#cpu) input plugins. ###### Query CPU and memory usage The following query creates a union of CPU and memory usage. @@ -98,7 +98,7 @@ In the Scatter visualization controls, points are differentiated based on their ## Important notes ### Differences between a scatter plot and a heatmap -Scatter plots and [Heatmaps](/v2.0/visualize-data/visualization-types/heatmap/) +Scatter plots and [Heatmaps](/influxdb/v2.0/visualize-data/visualization-types/heatmap/) both visualize the distribution of data points on X and Y axes. However, in certain cases, scatterplots can "hide" points if they share the same X and Y coordinates. diff --git a/content/influxdb/v2.0/visualize-data/visualization-types/table.md b/content/influxdb/v2.0/visualize-data/visualization-types/table.md index cb0151e83..2d0aa867a 100644 --- a/content/influxdb/v2.0/visualize-data/visualization-types/table.md +++ b/content/influxdb/v2.0/visualize-data/visualization-types/table.md @@ -26,7 +26,7 @@ The table visualization renders queried data in structured, easy-to-read tables. Columns and rows match those in the query output. If query results contain multiple tables, only one table is shown at a time. Select other output tables in the far left column of the table visualization. -Tables are identified by their [group key](/v2.0/query-data/get-started/#group-keys). +Tables are identified by their [group key](/influxdb/v2.0/query-data/get-started/#group-keys). ## Table Controls To view **Table** controls, click **{{< icon "gear" >}} Customize** next to diff --git a/content/influxdb/v2.0/write-data/_index.md b/content/influxdb/v2.0/write-data/_index.md index 967eff250..f1a373c61 100644 --- a/content/influxdb/v2.0/write-data/_index.md +++ b/content/influxdb/v2.0/write-data/_index.md @@ -34,21 +34,21 @@ Collect and write time series data to InfluxDB Cloud and InfluxDB OSS. Discover To write data into InfluxDB, you need the following: -- **organization** – _See [View organizations](/v2.0/organizations/view-orgs/#view-your-organization-id) +- **organization** – _See [View organizations](/influxdb/v2.0/organizations/view-orgs/#view-your-organization-id) for instructions on viewing your organization ID._ -- **bucket** – _See [View buckets](/v2.0/organizations/buckets/view-buckets/) for +- **bucket** – _See [View buckets](/influxdb/v2.0/organizations/buckets/view-buckets/) for instructions on viewing your bucket ID._ -- **authentication token** – _See [View tokens](/v2.0/security/tokens/view-tokens/) +- **authentication token** – _See [View tokens](/influxdb/v2.0/security/tokens/view-tokens/) for instructions on viewing your authentication token._ - **InfluxDB URL** – _See [InfluxDB URLs](/influxdb/v2.0/reference/urls/)_. -The [InfluxDB setup process](/v2.0/get-started/#set-up-influxdb) creates each of these. +The [InfluxDB setup process](/influxdb/v2.0/get-started/#set-up-influxdb) creates each of these. Use _line protocol_ format to write data into InfluxDB. Each line represents a data point. -Each point requires a [*measurement*](/v2.0/reference/syntax/line-protocol/#measurement) -and [*field set*](/v2.0/reference/syntax/line-protocol/#field-set) and may also include -a [*tag set*](/v2.0/reference/syntax/line-protocol/#tag-set) and a [*timestamp*](/v2.0/reference/syntax/line-protocol/#timestamp). +Each point requires a [*measurement*](/influxdb/v2.0/reference/syntax/line-protocol/#measurement) +and [*field set*](/influxdb/v2.0/reference/syntax/line-protocol/#field-set) and may also include +a [*tag set*](/influxdb/v2.0/reference/syntax/line-protocol/#tag-set) and a [*timestamp*](/influxdb/v2.0/reference/syntax/line-protocol/#timestamp). Line protocol data looks like this: @@ -60,7 +60,7 @@ mem,host=host1 used_percent=21.83599203 1556892777007291000 #### Timestamp precision -When writing data to InfluxDB, we [recommend including a timestamp](/v2.0/reference/syntax/line-protocol/#timestamp) with each point. +When writing data to InfluxDB, we [recommend including a timestamp](/influxdb/v2.0/reference/syntax/line-protocol/#timestamp) with each point. If a data point does not include a timestamp when it is received by the database, InfluxDB uses the current system time (UTC) of its host machine. @@ -74,8 +74,8 @@ InfluxDB accepts the following precisions: - `ms` - Milliseconds - `s` - Seconds -_For more details about line protocol, see the [Line protocol reference](/v2.0/reference/syntax/line-protocol) -and [Best practices for writing data](/v2.0/write-data/best-practices/)._ +_For more details about line protocol, see the [Line protocol reference](/influxdb/v2.0/reference/syntax/line-protocol) +and [Best practices for writing data](/influxdb/v2.0/write-data/best-practices/)._ ## Quickly start collecting data @@ -98,7 +98,7 @@ types of demo data that let you explore and familiarize yourself with InfluxDB C {{% note %}} #### Free to use and read-only - InfluxDB Cloud demo data buckets are **free to use** and are **_not_ subject to - [Free Plan](/v2.0/account-management/pricing-plans/#free-plan) rate limits**. + [Free Plan](/influxdb/v2.0/account-management/pricing-plans/#free-plan) rate limits**. - Demo data buckets are **read-only**. You cannot write data into demo data buckets. {{% /note %}} @@ -136,31 +136,31 @@ After adding a demo data bucket, view the pre-built dashboard specific to the de {{% note %}} #### Other sample data sets -See [Sample data](/v2.0/reference/sample-data) for more sample InfluxDB data sets. +See [Sample data](/influxdb/v2.0/reference/sample-data) for more sample InfluxDB data sets. {{% /note %}} ## Quick Start for InfluxDB OSS Select **Quick Start** in the last step of the InfluxDB user interface's (UI) -[setup process](/v2.0/get-started/#set-up-influxdb) to quickly start collecting data with InfluxDB. +[setup process](/influxdb/v2.0/get-started/#set-up-influxdb) to quickly start collecting data with InfluxDB. Quick Start creates a data scraper that collects metrics from the InfluxDB `/metrics` endpoint. The scraped data provides a robust dataset of internal InfluxDB metrics that you can query, visualize, and process. ### Use Quick Start to collect InfluxDB metrics -After [setting up InfluxDB v2.0](/v2.0/get-started/#set-up-influxdb), +After [setting up InfluxDB v2.0](/influxdb/v2.0/get-started/#set-up-influxdb), the "Let's start collecting data!" page displays options for collecting data. Click **Quick Start**. -InfluxDB creates and configures a new [scraper](/v2.0/write-data/no-code/scrape-data/). +InfluxDB creates and configures a new [scraper](/influxdb/v2.0/write-data/no-code/scrape-data/). The target URL points to the `/metrics` HTTP endpoint of your local InfluxDB instance (for example, `http://localhost:9999/metrics`), which outputs internal InfluxDB metrics in the [Prometheus data format](https://prometheus.io/docs/instrumenting/exposition_formats/). The scraper stores the scraped metrics in the bucket created during the -[initial setup process](/v2.0/get-started/#set-up-influxdb). +[initial setup process](/influxdb/v2.0/get-started/#set-up-influxdb). {{% note %}} Quick Start is only available in the last step of the setup process. -If you missed the Quick Start option, you can [manually create a scraper](/v2.0/write-data/scrape-data) +If you missed the Quick Start option, you can [manually create a scraper](/influxdb/v2.0/write-data/scrape-data) that scrapes data from the `/metrics` endpoint. {{% /note %}} @@ -171,8 +171,8 @@ that scrapes data from the `/metrics` endpoint. There are multiple options for writing data into InfluxDB, including both no-code and developer solutions. - - [No-code solutions](/v2.0/write-data/no-code) - - [Developer tools](/v2.0/write-data/developer-tools) + - [No-code solutions](/influxdb/v2.0/write-data/no-code) + - [Developer tools](/influxdb/v2.0/write-data/developer-tools) --- @@ -181,15 +181,15 @@ With your data in InfluxDB, you're ready to do one or more of the following: ### Query and explore your data Query data using Flux, the UI, and the `influx` command line interface. -See [Query data](/v2.0/query-data/). +See [Query data](/influxdb/v2.0/query-data/). ### Process your data -Use InfluxDB tasks to process and downsample data. See [Process data](/v2.0/process-data/). +Use InfluxDB tasks to process and downsample data. See [Process data](/influxdb/v2.0/process-data/). ### Visualize your data Build custom dashboards to visualize your data. -See [Visualize data](/v2.0/visualize-data/). +See [Visualize data](/influxdb/v2.0/visualize-data/). ### Monitor your data and send alerts Monitor your data and sends alerts based on specified logic. -See [Monitor and alert](/v2.0/monitor-alert/). +See [Monitor and alert](/influxdb/v2.0/monitor-alert/). diff --git a/content/influxdb/v2.0/write-data/best-practices/duplicate-points.md b/content/influxdb/v2.0/write-data/best-practices/duplicate-points.md index 5354df214..2be6508d1 100644 --- a/content/influxdb/v2.0/write-data/best-practices/duplicate-points.md +++ b/content/influxdb/v2.0/write-data/best-practices/duplicate-points.md @@ -16,7 +16,7 @@ influxdb/v2.0/tags: [best practices, write] --- InfluxDB identifies unique data points by their measurement, tag set, and timestamp -(each a part of [Line protocol](/v2.0/reference/syntax/line-protocol) used to write data to InfluxDB). +(each a part of [Line protocol](/influxdb/v2.0/reference/syntax/line-protocol) used to write data to InfluxDB). ```txt web,host=host2,region=us_west firstByte=15.0 1559260800000000000 diff --git a/content/influxdb/v2.0/write-data/best-practices/optimize-writes.md b/content/influxdb/v2.0/write-data/best-practices/optimize-writes.md index 64f97ae1e..05ea832b9 100644 --- a/content/influxdb/v2.0/write-data/best-practices/optimize-writes.md +++ b/content/influxdb/v2.0/write-data/best-practices/optimize-writes.md @@ -23,9 +23,9 @@ Use these tips to optimize performance and system overhead when writing data to {{% note %}} The following tools write to InfluxDB and employ _most_ write optimizations by default: -- [Telegraf](/v2.0/write-data/use-telegraf/) -- [InfluxDB client libraries](/v2.0/reference/api/client-libraries/) -- [InfluxDB scrapers](/v2.0/write-data/no-code/scrape-data/) +- [Telegraf](/influxdb/v2.0/write-data/use-telegraf/) +- [InfluxDB client libraries](/influxdb/v2.0/reference/api/client-libraries/) +- [InfluxDB scrapers](/influxdb/v2.0/write-data/no-code/scrape-data/) {{% /note %}} ## Batch writes @@ -55,7 +55,7 @@ By default, InfluxDB writes data in nanosecond precision. However if your data isn't collected in nanoseconds, there is no need to write at that precision. For better performance, use the coarsest precision possible for timestamps. -_Specify timestamp precision when [writing to InfluxDB](/v2.0/write-data/#timestamp-precision)._ +_Specify timestamp precision when [writing to InfluxDB](/influxdb/v2.0/write-data/#timestamp-precision)._ ## Use gzip compression @@ -84,10 +84,10 @@ In the `influxdb_v2` output plugin configuration in your `telegraf.conf`, set th {{% tab-content %}} ### Enable gzip compression in InfluxDB client libraries -Each [InfluxDB client library](/v2.0/reference/api/client-libraries/) provides +Each [InfluxDB client library](/influxdb/v2.0/reference/api/client-libraries/) provides options for compressing write requests or enforces compression by default. The method for enabling compression is different for each library. -For specific instructions, see the [InfluxDB client libraries documentation](/v2.0/reference/api/client-libraries/). +For specific instructions, see the [InfluxDB client libraries documentation](/influxdb/v2.0/reference/api/client-libraries/). {{% /tab-content %}} {{% tab-content %}} ### Use gzip compression with the InfluxDB API diff --git a/content/influxdb/v2.0/write-data/developer-tools/api.md b/content/influxdb/v2.0/write-data/developer-tools/api.md index c744b9a44..cb57a289e 100644 --- a/content/influxdb/v2.0/write-data/developer-tools/api.md +++ b/content/influxdb/v2.0/write-data/developer-tools/api.md @@ -26,7 +26,7 @@ Use the `POST` request method and include the following in your request: #### Example API write request Below is an example API write request using `curl`. -The URL depends on the version and location of your InfluxDB 2.0 instance _(see [InfluxDB URLs](/v2.0/reference/urls/))_. +The URL depends on the version and location of your InfluxDB 2.0 instance _(see [InfluxDB URLs](/influxdb/v2.0/reference/urls/))_. To compress data when writing to InfluxDB, set the `Content-Encoding` header to `gzip`. Compressing write requests reduces network bandwidth, but increases server-side load. @@ -64,4 +64,4 @@ mem,host=host2 used_percent=27.18294630 1556896336 {{< /code-tabs-wrapper >}} _For information about **InfluxDB API response codes**, see -[InfluxDB API Write documentation](/v2.0/api/#operation/PostWrite)._ +[InfluxDB API Write documentation](/influxdb/v2.0/api/#operation/PostWrite)._ diff --git a/content/influxdb/v2.0/write-data/developer-tools/client-libraries.md b/content/influxdb/v2.0/write-data/developer-tools/client-libraries.md index a1682b4a7..18e14df53 100644 --- a/content/influxdb/v2.0/write-data/developer-tools/client-libraries.md +++ b/content/influxdb/v2.0/write-data/developer-tools/client-libraries.md @@ -15,4 +15,4 @@ aliases: Use language-specific client libraries to integrate with the InfluxDB v2 API. -See [Client libraries reference](/v2.0/reference/api/client-libraries/) for more information. +See [Client libraries reference](/influxdb/v2.0/reference/api/client-libraries/) for more information. diff --git a/content/influxdb/v2.0/write-data/developer-tools/csv.md b/content/influxdb/v2.0/write-data/developer-tools/csv.md index c4eace3c4..b4672a549 100644 --- a/content/influxdb/v2.0/write-data/developer-tools/csv.md +++ b/content/influxdb/v2.0/write-data/developer-tools/csv.md @@ -1,9 +1,9 @@ --- title: Write CSV data to InfluxDB description: > - Use the [`influx write` command](/v2.0/reference/cli/influx/write/) to write CSV data + Use the [`influx write` command](/influxdb/v2.0/reference/cli/influx/write/) to write CSV data to InfluxDB. Include annotations with the CSV data to determine how the data translates - into [line protocol](/v2.0/reference/syntax/line-protocol/). + into [line protocol](/influxdb/v2.0/reference/syntax/line-protocol/). menu: influxdb_2_0: name: Write CSV data @@ -18,9 +18,9 @@ related: - /influxdb/v2.0/reference/cli/influx/write/ --- -Use the [`influx write` command](/v2.0/reference/cli/influx/write/) to write CSV data -to InfluxDB. Include [Extended annotated CSV](/v2.0/reference/syntax/annotated-csv/extended/) -annotations to specify how the data translates into [line protocol](/v2.0/reference/syntax/line-protocol/). +Use the [`influx write` command](/influxdb/v2.0/reference/cli/influx/write/) to write CSV data +to InfluxDB. Include [Extended annotated CSV](/influxdb/v2.0/reference/syntax/annotated-csv/extended/) +annotations to specify how the data translates into [line protocol](/influxdb/v2.0/reference/syntax/line-protocol/). Include annotations in the CSV file or inject them using the `--header` flag of the `influx write` command. @@ -70,21 +70,21 @@ Use **CSV annotations** to specify which element of line protocol each CSV colum represents and how to format the data. CSV annotations are rows at the beginning of a CSV file that describe column properties. -The `influx write` command supports [Extended annotated CSV](/v2.0/reference/syntax/annotated-csv/extended) +The `influx write` command supports [Extended annotated CSV](/influxdb/v2.0/reference/syntax/annotated-csv/extended) which provides options for specifying how CSV data should be converted into line protocol and how data is formatted. To write data to InfluxDB, data must include the following: -- [measurement](/v2.0/reference/syntax/line-protocol/#measurement) -- [field set](/v2.0/reference/syntax/line-protocol/#field-set) -- [timestamp](/v2.0/reference/syntax/line-protocol/#timestamp) _(Optional but recommended)_ -- [tag set](/v2.0/reference/syntax/line-protocol/#tag-set) _(Optional)_ +- [measurement](/influxdb/v2.0/reference/syntax/line-protocol/#measurement) +- [field set](/influxdb/v2.0/reference/syntax/line-protocol/#field-set) +- [timestamp](/influxdb/v2.0/reference/syntax/line-protocol/#timestamp) _(Optional but recommended)_ +- [tag set](/influxdb/v2.0/reference/syntax/line-protocol/#tag-set) _(Optional)_ Use CSV annotations to specify which of these elements each column represents. ## Write raw query results back to InfluxDB -Flux returns query results in [Annotated CSV](/v2.0/reference/syntax/annotated-csv/). +Flux returns query results in [Annotated CSV](/influxdb/v2.0/reference/syntax/annotated-csv/). These results include all annotations necessary to write the data back to InfluxDB. ## Inject annotation headers @@ -212,7 +212,7 @@ influx write -b example-bucket \ ## Skip rows with errors If a row in your CSV data is missing an -[element required to write to InfluxDB](/v2.0/reference/syntax/line-protocol/#elements-of-line-protocol) +[element required to write to InfluxDB](/influxdb/v2.0/reference/syntax/line-protocol/#elements-of-line-protocol) or data is incorrectly formatted, when processing the row, the `influx write` command returns an error and cancels the write request. To skip rows with errors, use the `--skipRowOnError` flag. @@ -239,7 +239,7 @@ Skipped rows are ignored and are not written to InfluxDB. --- ### Define constants -Use the Extended annotated CSV [`#constant` annotation](/v2.0/reference/syntax/annotated-csv/extended/#constant) +Use the Extended annotated CSV [`#constant` annotation](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#constant) to add a column and value to each row in the CSV data. {{< flex >}} @@ -270,7 +270,7 @@ example,source=csv count=18 1578096000000000000 --- ### Annotation shorthand -Extended annotated CSV supports [annotation shorthand](/v2.0/reference/syntax/annotated-csv/extended/#annotation-shorthand), +Extended annotated CSV supports [annotation shorthand](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#annotation-shorthand), which lets you define the **column label**, **datatype**, and **default value** in the column header. {{< flex >}} @@ -341,7 +341,7 @@ example count=18i 1578096000000000000 --- ### Ignore columns -Use the Extended annotated CSV [`#datatype ignored` annotation](/v2.0/reference/syntax/annotated-csv/extended/#ignored) +Use the Extended annotated CSV [`#datatype ignored` annotation](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#ignored) to ignore columns when writing CSV data to InfluxDB. {{< flex >}} @@ -371,7 +371,7 @@ m count=18i 1578096000000000000 ### Use alternate numeric formats If your CSV data contains numeric values that use a non-default fraction separator (`.`) -or contain group separators, [define your numeric format](/v2.0/reference/syntax/annotated-csv/extended/#double) +or contain group separators, [define your numeric format](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#double) in the `double`, `long`, and `unsignedLong` datatype annotations. {{% note %}} @@ -465,9 +465,9 @@ example lbs=2014u 1578096000000000000 --- ### Use alternate boolean format -Line protocol supports only [specific boolean values](/v2.0/reference/syntax/line-protocol/#boolean). +Line protocol supports only [specific boolean values](/influxdb/v2.0/reference/syntax/line-protocol/#boolean). If your CSV data contains boolean values that line protocol does not support, -[define your boolean format](/v2.0/reference/syntax/annotated-csv/extended/#boolean) +[define your boolean format](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#boolean) in the `boolean` datatype annotation. {{< flex >}} @@ -499,7 +499,7 @@ example verified=false 1578096000000000000 ### Use different timestamp formats The `influx write` command automatically detects **RFC3339** and **number** formatted timestamps when converting CSV to line protocol. -If using a different timestamp format, [define your timestamp format](/v2.0/reference/syntax/annotated-csv/extended/#datetime) +If using a different timestamp format, [define your timestamp format](/influxdb/v2.0/reference/syntax/annotated-csv/extended/#datetime) in the `dateTime` datatype annotation. {{< flex >}} diff --git a/content/influxdb/v2.0/write-data/developer-tools/influx-cli.md b/content/influxdb/v2.0/write-data/developer-tools/influx-cli.md index e65b51800..d5651960f 100644 --- a/content/influxdb/v2.0/write-data/developer-tools/influx-cli.md +++ b/content/influxdb/v2.0/write-data/developer-tools/influx-cli.md @@ -15,7 +15,7 @@ related: - /influxdb/v2.0/write-data/developer-tools/csv/ --- -To write data from the command line, use the [`influx write` command](/v2.0/reference/cli/influx/write/). +To write data from the command line, use the [`influx write` command](/influxdb/v2.0/reference/cli/influx/write/). Include the following in your command: | Requirement | Include by | @@ -26,7 +26,7 @@ Include the following in your command: | Authentication token | Set the `INFLUX_TOKEN` environment variable or use the `t`, `--token` flag. | | Data | Write data using **line protocol** or **annotated CSV**. Pass a file with the `-f`, `--file` flag. | -_See [Line protocol](/v2.0/reference/syntax/line-protocol/) and [Annotated CSV](/v2.0/reference/syntax/annotated-csv)_ +_See [Line protocol](/influxdb/v2.0/reference/syntax/line-protocol/) and [Annotated CSV](/influxdb/v2.0/reference/syntax/annotated-csv)_ #### Example influx write commands diff --git a/content/influxdb/v2.0/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md b/content/influxdb/v2.0/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md index 88215710f..05a80b280 100644 --- a/content/influxdb/v2.0/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md +++ b/content/influxdb/v2.0/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md @@ -17,7 +17,7 @@ Update a scraper in the InfluxDB user interface (UI). {{% note %}} Scraper **Target URLs** and **Buckets** cannot be updated. -To modify either, [create a new scraper](/v2.0/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper). +To modify either, [create a new scraper](/influxdb/v2.0/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper). {{% /note %}} ## Update a scraper in the InfluxDB UI diff --git a/content/influxdb/v2.0/write-data/no-code/use-telegraf/_index.md b/content/influxdb/v2.0/write-data/no-code/use-telegraf/_index.md index ae04ced58..07abf7f89 100644 --- a/content/influxdb/v2.0/write-data/no-code/use-telegraf/_index.md +++ b/content/influxdb/v2.0/write-data/no-code/use-telegraf/_index.md @@ -23,7 +23,7 @@ Its vast library of input plugins and "plug-and-play" architecture lets you quic and easily collect metrics from many different sources. This article describes how to use Telegraf to collect and store data in InfluxDB v2.0. -For a list of available plugins, see [Telegraf plugins](/v2.0/reference/telegraf-plugins/). +For a list of available plugins, see [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins/). #### Requirements - **Telegraf 1.9.2 or greater**. diff --git a/content/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config.md b/content/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config.md index ce80c910b..d5efd2f95 100644 --- a/content/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config.md +++ b/content/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config.md @@ -23,11 +23,11 @@ start Telegraf using the generated configuration file. {{% note %}} Only a subset of plugins are configurable using the InfluxDB UI. -To use plugins other than those listed, you must [manually configure Telegraf](/v2.0/write-data/no-code/use-telegraf/manual-config). +To use plugins other than those listed, you must [manually configure Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config). {{% /note %}} {{% note %}} -_View the [requirements](/v2.0/write-data/no-code/use-telegraf#requirements) +_View the [requirements](/influxdb/v2.0/write-data/no-code/use-telegraf#requirements) for using Telegraf with InfluxDB v2.0._ {{% /note %}} @@ -47,7 +47,7 @@ for using Telegraf with InfluxDB v2.0._ To configure a plugin or access plugin documentation, click the plugin name. {{% note %}} - Not all available plugins are listed on this screen. For more information on manually configuring additional plugins, see [Manually add Telegraf plugins](/v2.0/write-data/no-code/use-telegraf/manual-config/). + Not all available plugins are listed on this screen. For more information on manually configuring additional plugins, see [Manually add Telegraf plugins](/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config/). {{% /note %}} 8. Provide a **Telegraf Configuration Name** and an optional **Telegraf Configuration Description**. @@ -80,12 +80,12 @@ If you plan to monitor a Windows host using the System plugin, you must complete ## Start Telegraf -Requests to the [InfluxDB v2 API](/v2.0/reference/api/) must include an authentication token. +Requests to the [InfluxDB v2 API](/influxdb/v2.0/reference/api/) must include an authentication token. A token identifies specific permissions to the InfluxDB instance. ### Configure your token as an environment variable -1. Find your authentication token. _For information about viewing tokens, see [View tokens](/v2.0/security/tokens/view-tokens/)._ +1. Find your authentication token. _For information about viewing tokens, see [View tokens](/influxdb/v2.0/security/tokens/view-tokens/)._ 2. To configure your token as the `INFLUX_TOKEN` environment variable, run the command appropriate for your operating system and command-line tool: @@ -147,4 +147,4 @@ telegraf -config http://localhost:9999/api/v2/telegrafs/0xoX00oOx0xoX00o ## Manage Telegraf configurations For more information about managing Telegraf configurations in InfluxDB, see -[Telegraf configurations](/v2.0/telegraf-configs/). +[Telegraf configurations](/influxdb/v2.0/telegraf-configs/). diff --git a/content/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config.md b/content/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config.md index cd14f7660..e71ee4597 100644 --- a/content/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config.md +++ b/content/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config.md @@ -27,7 +27,7 @@ then start Telegraf using the custom configuration file. {{< youtube qFS2zANwIrc >}} {{% note %}} -_View the [requirements](/v2.0/write-data/no-code/use-telegraf#requirements) +_View the [requirements](/influxdb/v2.0/write-data/no-code/use-telegraf#requirements) for using Telegraf with InfluxDB v2.0._ {{% /note %}} @@ -36,13 +36,13 @@ Configure Telegraf input and output plugins in the Telegraf configuration file ( Input plugins collect metrics. Output plugins define destinations where metrics are sent. -_See [Telegraf plugins](/v2.0/reference/telegraf-plugins/) for a complete list of available plugins._ +_See [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins/) for a complete list of available plugins._ ### Manually add Telegraf plugins -To manually add any of the available [Telegraf plugins](/v2.0/reference/telegraf-plugins/), follow the steps below. +To manually add any of the available [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins/), follow the steps below. -1. Find the plugin you want to enable from the complete list of available [Telegraf plugins](/v2.0/reference/telegraf-plugins/). +1. Find the plugin you want to enable from the complete list of available [Telegraf plugins](/influxdb/v2.0/reference/telegraf-plugins/). 2. Click **View** to the right of the plugin name to open the plugin page on GitHub. For example, view the MQTT plugin GitHub page [here](https://github.com/influxdata/telegraf/blob/release-1.14/plugins/inputs/mqtt_consumer/README.md). 3. Copy and paste the example configuration into your Telegraf configuration file (typically named `telegraf.conf`). @@ -66,12 +66,12 @@ The InfluxDB output plugin configuration contains the following options: ##### urls An array of URLs for your InfluxDB v2.0 instances. -See [InfluxDB URLs](/v2.0/reference/urls/) for information about which URLs to use. +See [InfluxDB URLs](/influxdb/v2.0/reference/urls/) for information about which URLs to use. **{{< cloud-name "short">}} requires HTTPS**. ##### token Your InfluxDB v2.0 authorization token. -For information about viewing tokens, see [View tokens](/v2.0/security/tokens/view-tokens/). +For information about viewing tokens, see [View tokens](/influxdb/v2.0/security/tokens/view-tokens/). {{% note %}} ###### Avoid storing tokens in `telegraf.conf` @@ -146,12 +146,12 @@ enabling the InfluxDB v2 output plugin will write data to both v1.x and v2.0 ins ## Add a custom Telegraf configuration to InfluxDB To add a custom or manually configured Telegraf configuration to your collection -of Telegraf configurations in InfluxDB, use the [`influx telegrafs create`](/v2.0/reference/cli/influx/telegrafs/create/) -or [`influx telegrafs update`](/v2.0/reference/cli/influx/telegrafs/update/) commands. +of Telegraf configurations in InfluxDB, use the [`influx telegrafs create`](/influxdb/v2.0/reference/cli/influx/telegrafs/create/) +or [`influx telegrafs update`](/influxdb/v2.0/reference/cli/influx/telegrafs/update/) commands. For more information, see: -- [Create a Telegraf configuration](/v2.0/telegraf-configs/create/#use-the-influx-cli) -- [Update a Telegraf configuration](/v2.0/telegraf-configs/update/#use-the-influx-cli) +- [Create a Telegraf configuration](/influxdb/v2.0/telegraf-configs/create/#use-the-influx-cli) +- [Update a Telegraf configuration](/influxdb/v2.0/telegraf-configs/update/#use-the-influx-cli) ## Start Telegraf diff --git a/content/influxdb/v2.0/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md b/content/influxdb/v2.0/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md index f08ffb7a8..023653d00 100644 --- a/content/influxdb/v2.0/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md +++ b/content/influxdb/v2.0/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md @@ -16,7 +16,7 @@ weight: 202 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh). -Configure [`influxdb` output plugin](/v2.0/reference/telegraf-plugins/#influxdb) to write metrics to your InfluxDB 2.0 instance. +Configure [`influxdb` output plugin](/influxdb/v2.0/reference/telegraf-plugins/#influxdb) to write metrics to your InfluxDB 2.0 instance. ## Configure the HTTP Input plugin in your Telegraf configuration file diff --git a/content/kapacitor/v1.4/about_the_project/releasenotes-changelog.md b/content/kapacitor/v1.4/about_the_project/releasenotes-changelog.md index ddd94236e..d84d77274 100644 --- a/content/kapacitor/v1.4/about_the_project/releasenotes-changelog.md +++ b/content/kapacitor/v1.4/about_the_project/releasenotes-changelog.md @@ -302,7 +302,7 @@ stream ``` The API exposes endpoints to query the state of each alert and endpoints for configuring alert handlers. -See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. +See the [API docs](/kapacitor/v1.4/api/api/) for more details. The kapacitor CLI has been updated with commands for defining alert handlers. This release introduces a new feature where you can window based off the number of points instead of their time. @@ -389,7 +389,7 @@ stream New API endpoints have been added to be able to configure InfluxDB clusters and alert handlers dynamically without needing to restart the Kapacitor daemon. Along with the ability to dynamically configure a service, API endpoints have been added to test the configurable services. -See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. +See the [API docs](/kapacitor/v1.4/api/api/) for more details. >NOTE: The `connect_errors` stat from the query node was removed since the client changed, all errors are now counted in the `query_errors` stat. diff --git a/content/kapacitor/v1.4/guides/continuous_queries.md b/content/kapacitor/v1.4/guides/continuous_queries.md index ed4aba7eb..4de2ac803 100644 --- a/content/kapacitor/v1.4/guides/continuous_queries.md +++ b/content/kapacitor/v1.4/guides/continuous_queries.md @@ -155,5 +155,5 @@ batch Kapacitor is a powerful tool, if you need more power use it. If not keep using CQs until you do. -For more information and help writing TICKscripts from InfluxQL queries take a looks at these [docs](/{{< latest "kapacitor" >}}/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. +For more information and help writing TICKscripts from InfluxQL queries take a looks at these [docs](/kapacitor/v1.4/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. Every function available in the InfluxDB query language is available in Kapacitor, so you can convert any query into a Kapacitor TICKscript. diff --git a/content/kapacitor/v1.4/guides/event-handler-setup.md b/content/kapacitor/v1.4/guides/event-handler-setup.md index b665af775..3b91d4c78 100644 --- a/content/kapacitor/v1.4/guides/event-handler-setup.md +++ b/content/kapacitor/v1.4/guides/event-handler-setup.md @@ -8,12 +8,12 @@ menu: parent: Guides --- -Integrate Kapacitor into your monitoring system by sending [alert messages](/{{< latest "kapacitor" >}}/nodes/alert_node/#message) to supported event handlers. +Integrate Kapacitor into your monitoring system by sending [alert messages](/kapacitor/v1.4/nodes/alert_node/#message) to supported event handlers. Currently, Kapacitor can send alert messages to specific log files and specific URLs, as well as to applications like [Slack](https://slack.com/) and [HipChat](https://www.hipchat.com/). -This document offers step-by-step instructions for setting up event handlers with Kapacitor, including the relevant configuration options and [TICKscript](/{{< latest "kapacitor" >}}/tick/) syntax. +This document offers step-by-step instructions for setting up event handlers with Kapacitor, including the relevant configuration options and [TICKscript](/kapacitor/v1.4/tick/) syntax. Currently, this document doesn't cover every supported event handler, but we will continue to add content to this page over time. -For a complete list of the supported event handlers and for additional information, please see the [event handler reference documentation](/{{< latest "kapacitor" >}}/nodes/alert_node/). +For a complete list of the supported event handlers and for additional information, please see the [event handler reference documentation](/kapacitor/v1.4/nodes/alert_node/). diff --git a/content/kapacitor/v1.4/introduction/getting-started.md b/content/kapacitor/v1.4/introduction/getting-started.md index 2e9f51bf1..3d8eebc59 100644 --- a/content/kapacitor/v1.4/introduction/getting-started.md +++ b/content/kapacitor/v1.4/introduction/getting-started.md @@ -23,7 +23,7 @@ The following applications will be required: * [InfluxDB](/{{< latest "influxdb" "v1" >}}/) - While Kapacitor does not require InfluxDB, it is the easiest integration to setup and so it will be used in this guide. InfluxDB >= 1.3.x will be needed. * [Telegraf](/{{< latest "telegraf" >}}/) - Telegraf >= 1.4.x will be required. -* [Kapacitor](/{{< latest "kapacitor" >}}/) - The latest Kapacitor binary and installation packages can be found at the [downloads](https://portal.influxdata.com/downloads) page. +* [Kapacitor](/kapacitor/v1.4/) - The latest Kapacitor binary and installation packages can be found at the [downloads](https://portal.influxdata.com/downloads) page. * Terminal - The Kapacitor client application works using the CLI and so a basic terminal will be needed to issue commands. The use case diff --git a/content/kapacitor/v1.4/nodes/alert_node.md b/content/kapacitor/v1.4/nodes/alert_node.md index ab898b064..0d86d6afb 100644 --- a/content/kapacitor/v1.4/nodes/alert_node.md +++ b/content/kapacitor/v1.4/nodes/alert_node.md @@ -28,7 +28,7 @@ menu: | **[email](#email) ( `to` `...string`)** | Email the alert data. | | **[exec](#exec) ( `executable` `string`, `args` `...string`)** | Execute a command whenever an alert is triggered and pass the alert data over STDIN in JSON format. | | **[flapping](#flapping) ( `low` `float64`, `high` `float64`)** | Perform flap detection on the alerts. The method used is similar method to Nagios: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/flapping.html | -| **[hipChat](#hipchat) ( )** | Send the alert to HipChat. For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. | +| **[hipChat](#hipchat) ( )** | Send the alert to HipChat. For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//kapacitor/v1.4/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. | | **[history](#history) ( `value` `int64`)** | Number of previous states to remember when computing flapping levels and checking for state changes. Minimum value is 2 in order to keep track of current and previous states. | | **[id](#id) ( `value` `string`)** | Template for constructing a unique ID for a given alert. | | **[idField](#idfield) ( `value` `string`)** | Optional field key to add to the data, containing the alert ID as a string. | @@ -52,7 +52,7 @@ menu: | **[stateChangesOnly](#statechangesonly) ( `maxInterval` `...time.Duration`)** | Only sends events where the state changed. Each different alert level OK, INFO, WARNING, and CRITICAL are considered different states. | | **[talk](#talk) ( )** | Send the alert to Talk. To use Talk alerting you must first follow the steps to create a new incoming webhook. | | **[tcp](#tcp) ( `address` `string`)** | Send JSON alert data to a specified address over TCP. | -| **[telegram](#telegram) ( )** | Send the alert to Telegram. For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, | +| **[telegram](#telegram) ( )** | Send the alert to Telegram. For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//kapacitor/v1.4/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, | | **[topic](#topic) ( `value` `string`)** | Topic specifies the name of an alert topic to which, alerts will be published. Alert handlers can be configured per topic, see the API documentation. | | **[victorOps](#victorops) ( )** | Send alert to VictorOps. To use VictorOps alerting you must first enable the 'Alert Ingestion API' in the 'Integrations' section of VictorOps. Then place the API key from the URL into the 'victorops' section of the Kapacitor configuration. | | **[warn](#warn) ( `value` `ast.LambdaNode`)** | Filter expression for the WARNING alert level. An empty value indicates the level is invalid and is skipped. | @@ -67,7 +67,7 @@ menu: ### Description An [AlertNode](/kapacitor/v1.4/nodes/alert_node/) can trigger an event of varying severity levels and pass the event to alert handlers. -The criteria for triggering an alert is specified using a [lambda expression](/{{< latest "kapacitor" >}}/tick/expr/). +The criteria for triggering an alert is specified using a [lambda expression](/kapacitor/v1.4/tick/expr/). See [AlertNode.Info,](/kapacitor/v1.4/nodes/alert_node/#info) [AlertNode.Warn,](/kapacitor/v1.4/nodes/alert_node/#warn) and [AlertNode.Crit](/kapacitor/v1.4/nodes/alert_node/#crit) below. Different event handlers can be configured for each [AlertNode.](/kapacitor/v1.4/nodes/alert_node/) @@ -608,7 +608,7 @@ alert.flapping(low float64, high float64) ### HipChat Send the alert to HipChat. -For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#hipchat-setup). +For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//kapacitor/v1.4/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. @@ -1925,7 +1925,7 @@ alert.tcp(address string) ### Telegram Send the alert to Telegram. -For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#telegram-setup). +For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//kapacitor/v1.4/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, Example: diff --git a/content/kapacitor/v1.4/nodes/from_node.md b/content/kapacitor/v1.4/nodes/from_node.md index e7f7cdd14..ed03498c8 100644 --- a/content/kapacitor/v1.4/nodes/from_node.md +++ b/content/kapacitor/v1.4/nodes/from_node.md @@ -27,7 +27,7 @@ menu: | **[retentionPolicy](#retentionpolicy) ( `value` `string`)** | The retention policy name If empty any retention policy will be used. | | **[round](#round) ( `value` `time.Duration`)** | Optional duration for rounding timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .round(1s) | | **[truncate](#truncate) ( `value` `time.Duration`)** | Optional duration for truncating timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .truncate(1s) | -| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. | +| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/kapacitor/v1.4/tick/expr/) docs for more information. | @@ -211,7 +211,7 @@ from.truncate(value time.Duration) Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. -See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. +See the [expression](/kapacitor/v1.4/tick/expr/) docs for more information. Multiple calls to the Where method will `AND` together each expression. diff --git a/content/kapacitor/v1.4/working/api.md b/content/kapacitor/v1.4/working/api.md index 9da886f59..847eac676 100644 --- a/content/kapacitor/v1.4/working/api.md +++ b/content/kapacitor/v1.4/working/api.md @@ -497,7 +497,7 @@ GET /kapacitor/v1/tasks?fields=status&fields=executing&fields=error ### Custom task HTTP endpoints -In TICKscript it is possible to expose a cache of recent data using the [HTTPOut](/{{< latest "kapacitor" >}}/nodes/http_out_node/) node. +In TICKscript it is possible to expose a cache of recent data using the [HTTPOut](/kapacitor/v1.4/nodes/http_out_node/) node. The data is available at the path `/kapacitor/v1/tasks/TASK_ID/ENDPOINT_NAME`. ### Example diff --git a/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md b/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md index 0ac62f6a9..df4c4a793 100644 --- a/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md +++ b/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md @@ -439,7 +439,7 @@ stream ``` The API exposes endpoints to query the state of each alert and endpoints for configuring alert handlers. -See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. +See the [API docs](/kapacitor/v1.5/api/api/) for more details. The kapacitor CLI has been updated with commands for defining alert handlers. This release introduces a new feature where you can window based off the number of points instead of their time. @@ -526,7 +526,7 @@ stream New API endpoints have been added to be able to configure InfluxDB clusters and alert handlers dynamically without needing to restart the Kapacitor daemon. Along with the ability to dynamically configure a service, API endpoints have been added to test the configurable services. -See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. +See the [API docs](/kapacitor/v1.5/api/api/) for more details. >NOTE: The `connect_errors` stat from the query node was removed since the client changed, all errors are now counted in the `query_errors` stat. diff --git a/content/kapacitor/v1.5/guides/continuous_queries.md b/content/kapacitor/v1.5/guides/continuous_queries.md index 056a996b9..3867e0d07 100644 --- a/content/kapacitor/v1.5/guides/continuous_queries.md +++ b/content/kapacitor/v1.5/guides/continuous_queries.md @@ -156,7 +156,7 @@ batch Kapacitor is a powerful tool. If you need more flexibility than CQs offer, use it. -For more information and help writing TICKscripts from InfluxQL queries take a look at these [docs](/{{< latest "kapacitor" >}}/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. +For more information and help writing TICKscripts from InfluxQL queries take a look at these [docs](/kapacitor/v1.5/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. Every function available in the InfluxDB query language is available in Kapacitor, so you can convert any query into a Kapacitor TICKscript. ## Important to Know diff --git a/content/kapacitor/v1.5/guides/event-handler-setup.md b/content/kapacitor/v1.5/guides/event-handler-setup.md index 230b36e37..3de128a04 100644 --- a/content/kapacitor/v1.5/guides/event-handler-setup.md +++ b/content/kapacitor/v1.5/guides/event-handler-setup.md @@ -8,17 +8,17 @@ menu: parent: guides --- -Integrate Kapacitor into your monitoring system by sending [alert messages](/{{< latest "kapacitor" >}}/nodes/alert_node/#message) +Integrate Kapacitor into your monitoring system by sending [alert messages](/kapacitor/v1.5/nodes/alert_node/#message) to supported event handlers. Currently, Kapacitor can send alert messages to specific log files and specific URLs, as well as to applications such as [Slack](https://slack.com/) and [HipChat](https://www.hipchat.com/). This document offers step-by-step instructions for setting up event handlers with Kapacitor, -including relevant configuration options and [TICKscript](/{{< latest "kapacitor" >}}/tick/) syntax. +including relevant configuration options and [TICKscript](/kapacitor/v1.5/tick/) syntax. Currently, this document doesn't cover every supported event handler, but we will continue to add content to this page over time. For a complete list of the supported event handlers and for additional information, -please see the [event handler reference documentation](/{{< latest "kapacitor" >}}/nodes/alert_node/). +please see the [event handler reference documentation](/kapacitor/v1.5/nodes/alert_node/). [HipChat Setup](#hipchat-setup) [Telegram Setup](#telegram-setup") diff --git a/content/kapacitor/v1.5/guides/two-measurement-alert.md b/content/kapacitor/v1.5/guides/two-measurement-alert.md index 3209e389e..df37391f1 100644 --- a/content/kapacitor/v1.5/guides/two-measurement-alert.md +++ b/content/kapacitor/v1.5/guides/two-measurement-alert.md @@ -17,7 +17,7 @@ As an added bonus, we'll also include a query that can be used to graph the perc difference between the two measurements. ## Comparing measurements and creating an alert -The following [TICKscript](/{{< latest "kapacitor" >}}/tick/) streams the `m1` and `m2` measurements, +The following [TICKscript](/kapacitor/v1.5/tick/) streams the `m1` and `m2` measurements, joins them, compares them, and triggers an alert if the two measurements are different. ```js diff --git a/content/kapacitor/v1.5/nodes/alert_node.md b/content/kapacitor/v1.5/nodes/alert_node.md index 4dbe621df..c835c4980 100644 --- a/content/kapacitor/v1.5/nodes/alert_node.md +++ b/content/kapacitor/v1.5/nodes/alert_node.md @@ -14,7 +14,7 @@ menu: The `alert` node triggers an event of varying severity levels and passes the event to [event handlers](/kapacitor/v1.5/event_handlers/). The criteria for -triggering an alert is specified via a [lambda expression](/{{< latest "kapacitor" >}}/tick/expr/). +triggering an alert is specified via a [lambda expression](/kapacitor/v1.5/tick/expr/). See [AlertNode.Info](/kapacitor/v1.5/nodes/alert_node/#info), [AlertNode.Warn](/kapacitor/v1.5/nodes/alert_node/#warn), and [AlertNode.Crit](/kapacitor/v1.5/nodes/alert_node/#crit) below. diff --git a/content/kapacitor/v1.5/nodes/from_node.md b/content/kapacitor/v1.5/nodes/from_node.md index 122a169c8..7b868f695 100644 --- a/content/kapacitor/v1.5/nodes/from_node.md +++ b/content/kapacitor/v1.5/nodes/from_node.md @@ -52,7 +52,7 @@ the tag `host` matches the regex `logger\d+`. | **[retentionPolicy](#retentionpolicy) ( `value` `string`)** | The retention policy name If empty any retention policy will be used. | | **[round](#round) ( `value` `time.Duration`)** | Optional duration for rounding timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .round(1s) | | **[truncate](#truncate) ( `value` `time.Duration`)** | Optional duration for truncating timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .truncate(1s) | -| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. | +| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/kapacitor/v1.5/tick/expr/) docs for more information. | @@ -271,7 +271,7 @@ from.truncate(value time.Duration) Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. -See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. +See the [expression](/kapacitor/v1.5/tick/expr/) docs for more information. Multiple calls to the Where method will `AND` together each expression. diff --git a/content/kapacitor/v1.5/nodes/join_node.md b/content/kapacitor/v1.5/nodes/join_node.md index ba06b66cd..f921e46bb 100644 --- a/content/kapacitor/v1.5/nodes/join_node.md +++ b/content/kapacitor/v1.5/nodes/join_node.md @@ -266,7 +266,7 @@ Example: #### Handling null fill values in outer joins When using Kapacitor to perform an outer join, it's important to set default values for `null` fields resulting from the join and fill operations. -This is done using the [DefaultNode](/{{< latest "kapacitor" >}}/nodes/default_node/), +This is done using the [DefaultNode](/kapacitor/v1.5/nodes/default_node/), which replaces null values for a specific field key with a specified default value. Not doing so may result in invalid line protocol (as `null` isn't an appropriate value for all field types) causing the join to fail. diff --git a/content/kapacitor/v1.5/working/api.md b/content/kapacitor/v1.5/working/api.md index 8532183c3..78b7cf43e 100644 --- a/content/kapacitor/v1.5/working/api.md +++ b/content/kapacitor/v1.5/working/api.md @@ -501,7 +501,7 @@ GET /kapacitor/v1/tasks?fields=status&fields=executing&fields=error ### Custom task HTTP endpoints -In TICKscript, it is possible to expose a cache of recent data via the [HTTPOut](/{{< latest "kapacitor" >}}/nodes/http_out_node/) node. +In TICKscript, it is possible to expose a cache of recent data via the [HTTPOut](/kapacitor/v1.5/nodes/http_out_node/) node. The data is available at the path `/kapacitor/v1/tasks/TASK_ID/ENDPOINT_NAME`. ### Example