influxdata / influxdata/docs-v2
clarify auth wrt checks and tasks
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Our docs on checks and notifications don't discuss who the chck runs as, which I think would be helpful for people in understanding what buckets, influx APIs, etc the query has access to. I'm not sure the best place for this since this applies to both monitor-alert/checks/ and monitor-alert/custom-checks/, so I'm going to suggest adjusting the toplevel page's Overview point '1' to change from:
"A check in InfluxDB queries data and assigns a status with a _level based on specific conditions."
to:
"A check in InfluxDB queries data and assigns a status with a _level based on specific conditions. Checks are run under the authorization of the user that created the check."
Likewise, we should do the same for tasks. Eg, update the getting started section of tasks to change this (though maybe there is a better place on the same page with some rewording):
"An InfluxDB task is a scheduled Flux script that takes a stream of input data, modifies or analyzes it in some way, then stores the modified data in a new bucket or performs other actions."
to:
"An InfluxDB task is a scheduled Flux script that takes a stream of input data, modifies or analyzes it in some way, then stores the modified data in a new bucket or performs other actions. Tasks are run under the authorization of the user that created the task."
##### Relevant URLs
- https://docs.influxdata.com/influxdb/cloud/monitor-alert/
- https://docs.influxdata.com/influxdb/v2.0/monitor-alert/
- https://docs.influxdata.com/influxdb/cloud/process-data/get-started/
- https://docs.influxdata.com/influxdb/v2.0/process-data/get-started/
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.