We worked on this during the offsite, but there are a couple of things that are still needed to productionize it:
1. move it to ee & release for all paid customers
2. product design: currently we just prepend the dashboardItem we came from, but dashboards can have layouts, which would get messed up if we did it this way. It would be great to be able to see where we came from (e.g. to know when the spike in the graph happened exactly that made me click on the dive link, but I don't know how to design it)
3. Code changes based on ^
4. Blog post (including a diving hedgehog @lottiecoxon) - I propose with the different user stories we used in our demo

cc @samwinslow @jamesefhawkins anything else I'm missing?

posthog/api/insight.py
import json
from typing import Any, Dict, Type
from django.db.models import QuerySet
from django.db.models.query_utils import Q
from django.utils.timezone import now
from django_filters.rest_framework import DjangoFilterBackend
from drf_spectacular.utils import OpenApiResponse
from rest_framework import request, serializers, viewsets
from rest_framework.decorators import action
from rest_framework.permissions import IsAuthenticated
from rest_framework.response import Response
from sentry_sdk import capture_exception
from ee.clickhouse.queries.funnels import ClickhouseFunnelTimeToConvert, ClickhouseFunnelTrends
from ee.clickhouse.queries.funnels.utils import get_funnel_order_class
from ee.clickhouse.queries.paths.paths import ClickhousePaths
from ee.clickhouse.queries.retention.clickhouse_retention import ClickhouseRetention
from ee.clickhouse.queries.stickiness.clickhouse_stickiness import ClickhouseStickiness
from ee.clickhouse.queries.trends.clickhouse_trends import ClickhouseTrends
from ee.clickhouse.queries.util import get_earliest_timestamp
from posthog.api.documentation import extend_schema
from posthog.api.insight_serializers import (
    FunnelSerializer,