Digest

​

What is a Digest?

• Trend analysis: Tracks infrastructure health over time and highlights notable changes.
• Issue summaries: Consolidates patterns discovered from alerts and incidents.
• Actionable insights: Recommends optimizations and proactive fixes based on discovered trends.
• Scheduled delivery: Runs via cron and can post results to Slack.

​

Use Cases

​

Detect Emerging Risks Earlier

• Challenge: Slow drift and multi‑week trends (e.g., rising 95th percentile latency) are easy to miss.
• How it works: Digests compare recent periods against baselines and flag material degradation.
• Outcome: Early warnings with clear evidence so teams can act before issues escalate.

​

Operational Hygiene

• Challenge: Recurring issues and noisy alerts persist because insights are fragmented and hygiene work is deprioritized.
• How it works: Digest sections track repeating patterns (flaky tests, noisy alerts, SLO misses), highlight cleanup actions, and link to investigations or tickets. Posting to Slack keeps hygiene tasks visible.
• Outcome: Continuous improvement loop that reduces toil and alert noise while improving reliability over time.

​

Stakeholder Alignment

• Challenge: Leaders and partner teams need consistent, comparable updates; ad‑hoc reporting creates misalignment and delays decisions.
• How it works: Scheduled digests present week‑over‑week trends (e.g., error rates, latency, cost), summarize incidents and mitigations, and outline next‑week priorities. Deliver to stakeholder Slack channels for broad visibility.
• Outcome: Shared source of truth that speeds decision‑making and reduces status meetings.

​

How to Set Up Digests

​

Create the Digest

• Go to Digests and click “Create Digest”.
• Name your digest (e.g., “Weekly Platform Health”).

​

Configure the Schedule

• Enter a cron expression (e.g., 0 9 * * 1 for 9am every Monday).
• Recommended: Select a Slack Channel to post results for notifications.

​

Define Content Sections

• Add one or more sections to provide instructions on what to report on.
• Note the sections are separate from each other and do not share contexts.

​

Run and Notify

• From the job page, click “Run Now” to generate a report immediately.
• Choose whether to send Slack notifications for that run; scheduled runs follow your channel settings.

​

Review Results

• See your digest runs listed with timestamps and status.
• Open a run to review the compiled report.

​

Best Practices

• Group context‑dependent instructions into one section: Sections are independent and do not share context; if multiple instructions rely on the same telemetry data or intermediate results, keep them together in a single section for higher efficiency.
• Be specific about outputs and steps: Define the desired report format and the exact “how” (e.g., data sources to use, metrics to compare, thresholds/SLAs) so reports are consistent, comparable, and high quality across runs.
• Leverage Prompt Studio to iterate on digest prompts: Use Prompt Studio to test section prompts against recent data, compare versions side‑by‑side, tighten wording for clarity and consistency, then save improvements back to the digest job.

​

Example Reports