influxdata / influxdata/influxdb

InfluxDB Cloud: reports

Open
#18,309 1 comment 0 reactions 0 assignees View on GitHub
kind/feature-request team/ui
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Proposal:__
Reports that can be sent via different endpoints on specified schedule automatically. Reports can be in different formats and contain different data. Examples:

* screenshot of dashboard cells within specified time range can be sent to specified email address
* result of Flux query can be sent to HTTP endpoint in JSON format

It's different than alerts. Alerts are sent on some conditional. But reports are supposed to be sent without conditions, by schedule.

New feature can be placed in renamed Alerts section like this:

![image](https://user-images.githubusercontent.com/26361185/83329490-86e06800-a292-11ea-807e-fcd0f4e1d36b.png)

__Use case:__
Examples of use cases:
* report containing image of sales amounts of a company which is sent every Friday to specified email addresses
* JSON containing bucket data is sent to existing REST API as body of a request

Contributor guide

Open the contributing guide

Research direction

No implementation files or tests are named. Start by reviewing the existing Alerts section and its scheduling, endpoint, dashboard, and email capabilities, then clarify the supported report formats, data sources, destinations, and schedule behavior. Done means the report feature's scope and acceptance criteria are defined.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, backend-api-design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.