Code Insights monitoring/alerting/recurring reports

Created by: jyavorska

Problem to solve

You have to check code insights manually – no alerts if values change. This is not how IC developers prefer to use tools – they don't want to manually come back to check, but instead want to set automated reports or alerts that only surface when they need to care about a metric.

Right now, IC devs have poor visibility into insights – bringing reports into slack or other channels they use more regularly will improve adoption for IC dev users.

We will expand the concept of "triggers" in monitors to include thresholds or date-recurring (like weekly) reports, and "actions" to include sending code insights values/chart captures.

Measure of success

Primary: # of monitors/reports set up and sent; overall increase in unique and total WAU pageviews

Solution summary

https://sourcegraph.productboard.com/feature-board/1793095-code-insights/features/6506613/insights

Artifacts:

TO DO

What specific customers are we iterating on the problem and solution with?

Impact on use cases

Code health, fixing vulnerabilities, onboarding & velocity, incident response

Delivery plan

https://sourcegraph.productboard.com/feature-board/1793095-code-insights/features/6506613/detail

TO DO