From bbe21c43c1e59b29d9b5b77c75ef409edb7c5681 Mon Sep 17 00:00:00 2001 From: Sunbrye Ly Date: Fri, 23 Sep 2022 08:40:14 -1000 Subject: [PATCH 1/2] feat: dar-331 --- content/influxdb/v2.4/process-data/get-started.md | 5 +++++ .../v2.4/process-data/manage-tasks/task-run-history.md | 7 +++++++ 2 files changed, 12 insertions(+) diff --git a/content/influxdb/v2.4/process-data/get-started.md b/content/influxdb/v2.4/process-data/get-started.md index e3d8af1f7..5a0677176 100644 --- a/content/influxdb/v2.4/process-data/get-started.md +++ b/content/influxdb/v2.4/process-data/get-started.md @@ -49,10 +49,15 @@ option task = {name: "downsample_5m_precision", every: 1h, offset: 0m} _See [Task configuration options](/influxdb/v2.4/process-data/task-options) for detailed information about each option._ +_Note that InfluxDB doesn't guarantee that a task will run at the scheduled time. +See [View task run logs for a task](/influxdb/v2.4/process-data/manage-tasks/task-run-history/#view-task-run-logs-with-the-influxdb-api) +for detailed information on task service-level agreements (SLAs)._ + {{% note %}} The InfluxDB UI provides a form for defining task options. {{% /note %}} + {{% cloud-only %}} ### Task options for invokable scripts diff --git a/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md b/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md index 796249785..9ebc5495c 100644 --- a/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md +++ b/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md @@ -74,3 +74,10 @@ endpoint](/influxdb/v2.4/api/#operation/GetTasksIDRunsIDLogs). {{< api-endpoint method="GET" endpoint="http://localhost:8086/api/v2/tasks/TASK_ID/runs/RUN_ID/logs" >}} To retry failed task runs, see how to [run tasks](/influxdb/v2.4/process-data/manage-tasks/run-task/). + +{{% warn %}} +InfluxDB doesn’t guarantee that a task will run at the scheduled time. During busy +periods, tasks are added to the run queue and processed in order of submission. +The scheduled start time and actual start time can be viewed in the logs under +`scheduledFor` and `startedAt`. +{{% /warn %}} \ No newline at end of file From 57166a59e9e8ce1ab8694615e651e5557665a197 Mon Sep 17 00:00:00 2001 From: Sunbrye Ly Date: Mon, 26 Sep 2022 08:45:27 -1000 Subject: [PATCH 2/2] fix: pr requested changes --- .../influxdb/v2.4/process-data/get-started.md | 2 +- .../manage-tasks/task-run-history.md | 17 ++++++++++------- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/content/influxdb/v2.4/process-data/get-started.md b/content/influxdb/v2.4/process-data/get-started.md index 5a0677176..f40fee628 100644 --- a/content/influxdb/v2.4/process-data/get-started.md +++ b/content/influxdb/v2.4/process-data/get-started.md @@ -50,7 +50,7 @@ _See [Task configuration options](/influxdb/v2.4/process-data/task-options) for about each option._ _Note that InfluxDB doesn't guarantee that a task will run at the scheduled time. -See [View task run logs for a task](/influxdb/v2.4/process-data/manage-tasks/task-run-history/#view-task-run-logs-with-the-influxdb-api) +See [View task run logs for a task](/influxdb/v2.4/process-data/manage-tasks/task-run-history) for detailed information on task service-level agreements (SLAs)._ {{% note %}} diff --git a/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md b/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md index 9ebc5495c..306e37640 100644 --- a/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md +++ b/content/influxdb/v2.4/process-data/manage-tasks/task-run-history.md @@ -20,6 +20,16 @@ and the exit status of the run attempt. Use the InfluxDB user interface (UI), the `influx` command line interface (CLI), or the InfluxDB `/api/v2` API to view task run histories and associated logs. +{{% warn %}} +InfluxDB doesn’t guarantee that a task will run at the scheduled time. During busy +periods, tasks are added to the run queue and processed in order of submission. +The scheduled start time and actual start time can be viewed in the logs under +`scheduledFor` and `startedAt`. + +Task execution time doesn't affect the time range queried. Tasks will query +over the set time range as if executed on schedule regardless of delay. +{{% /warn %}} + ## View a task's run history in the InfluxDB UI 1. In the navigation menu on the left, select **Tasks**. @@ -74,10 +84,3 @@ endpoint](/influxdb/v2.4/api/#operation/GetTasksIDRunsIDLogs). {{< api-endpoint method="GET" endpoint="http://localhost:8086/api/v2/tasks/TASK_ID/runs/RUN_ID/logs" >}} To retry failed task runs, see how to [run tasks](/influxdb/v2.4/process-data/manage-tasks/run-task/). - -{{% warn %}} -InfluxDB doesn’t guarantee that a task will run at the scheduled time. During busy -periods, tasks are added to the run queue and processed in order of submission. -The scheduled start time and actual start time can be viewed in the logs under -`scheduledFor` and `startedAt`. -{{% /warn %}} \ No newline at end of file