Repository navigation
feat(landing): Dynatrace pricing guide - #1572
Conversation
Maple review🟢 Confidence 8/10 · likely safe to merge Adds a static Dynatrace pricing guide page, registers it in the guides index and llms.txt. Content and arithmetic check out; one internal link points at a page that does not exist.
Findings🟠 Warning · F1 · Link to
|
| File | Calls/day | Busiest operations |
|---|---|---|
apps/landing/src/pages/guides/dynatrace-pricing.astro |
131k | maple 131k/day, 92.9% err |
What was checked
- Worked-example arithmetic recomputed: $1,325.80/month, $15,910/year, $173.70 retention break-even
tocslugs all match section ids;FAQ,TableOfContents,SeoHead,Layoutprops match the sibling guidesllms-full.txtis docs-only, so guides need no entry there
4921036 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.
![maple-review-bot[bot]](https://avatars.githubusercontent.com/in/4108169?s=60&v=4){kind=small}
| <p class="guide-eyebrow">10 · Comparison</p> | ||
| <h2>Dynatrace vs New Relic pricing</h2> | ||
| <p> | ||
| The two vendors meter different things. Dynatrace bills infrastructure by the hour and data by volume, with no seat fees. New Relic bills data by volume and users by seat. New Relic figures below are from <a href="https://newrelic.com/pricing" target="_blank" rel="noopener noreferrer">newrelic.com/pricing</a>, last verified {verified}; the <a href="/guides/new-relic-pricing">New Relic pricing guide</a> covers its model in detail. |
There was a problem hiding this comment.
Warning
Link to /guides/new-relic-pricing points at a page that does not exist
F1 · Warning · correctness
No new-relic-pricing file exists under apps/landing/src/pages/guides/ and the repo has no redirect for it, so this link 404s. The New Relic comparison that does exist is /compare/new-relic. Link there, or land the New Relic guide first.
Point at `/compare/new-relic`, or merge after the `/guides/new-relic-pricing` page ships.
🤖 Prompt to fix with an AI agent
In `apps/landing/src/pages/guides/dynatrace-pricing.astro:420`: Link to `/guides/new-relic-pricing` points at a page that does not exist.
No `new-relic-pricing` file exists under `apps/landing/src/pages/guides/` and the repo has no redirect for it, so this link 404s. The New Relic comparison that does exist is `/compare/new-relic`. Link there, or land the New Relic guide first.
Suggested fix: Point at `/compare/new-relic`, or merge after the `/guides/new-relic-pricing` page ships.
Verify the problem exists at that location before changing it, and keep the fix to those lines.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
Devin Review found 1 potential issue.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
| <p class="guide-eyebrow">10 · Comparison</p> | ||
| <h2>Dynatrace vs New Relic pricing</h2> | ||
| <p> | ||
| The two vendors meter different things. Dynatrace bills infrastructure by the hour and data by volume, with no seat fees. New Relic bills data by volume and users by seat. New Relic figures below are from <a href="https://newrelic.com/pricing" target="_blank" rel="noopener noreferrer">newrelic.com/pricing</a>, last verified {verified}; the <a href="/guides/new-relic-pricing">New Relic pricing guide</a> covers its model in detail. |
There was a problem hiding this comment.
🟡 New Relic guide link returns 404
Clicking the New Relic pricing guide link returns 404. No route exists for that guide, so readers cannot open the promised comparison.
Learn more
The new pricing guide links to a separate New Relic pricing guide, but the landing application's guide routes do not include that page. The internal link therefore leads to the site's not-found response.
Example: A reader clicks “New Relic pricing guide” in the comparison section and reaches 404 rather than the detailed guide described by the link.
Recommended fix: Add the linked guide route before publishing this link, or replace the link with an existing destination such as the cited New Relic pricing page.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 2 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: 🔵 Low · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely identifies the main change: adding a Dynatrace pricing guide to the landing site. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Covers the DPS model, the public rate card, cost per host by monitoring mode, Kubernetes, log/trace/metric billing, commitments and trial, a worked monthly bill, spend controls, a comparison with New Relic's model, and Maple's pricing. Vendor prices last verified 2026-10-19.
Regroup into six sections, re-verify every price on the rate card and licensing docs, add a cost-per-host chart, a stacked bill for the worked example, a trace-billing diagram for OpenTelemetry sources, and a tested Collector config that drops debug logs before export. YAML keys with a slash (otlp_http/dynatrace) now highlight.
4921036 to
6d76cb4
Compare
Maple review🟢 Confidence 7/10 · likely safe to merge Adds a Dynatrace pricing guide page, registers it on
Findings🟠 Warning · F2 · Billing screenshot referenced by the guide is not in the repocorrectness ·
🟠 Warning · F3 · Collector snippet uses component ids
|
| File | Calls/day | Busiest operations |
|---|---|---|
apps/landing/src/pages/guides/dynatrace-pricing.astro |
105k | maple 105k/day, 91.1% err |
What was checked
- Bill arithmetic re-checked: 6×16 GiB Full-Stack $700.80, retain $180, $1325.80 total; retention break-even $173.70 / $0.0035 = 49,600 GiB
- All in-page
tocslugs matchidattributes, and/pricing,/docs/reference/ingest,/docs/infrastructure/hostsroutes exist - New
[\w./-]+regex is valid inside a character class and only affects theyamltokenizer
6d76cb4 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.
| logs: | ||
| log_record: | ||
| - severity_number < SEVERITY_NUMBER_INFO | ||
| cumulative_to_delta: |
There was a problem hiding this comment.
Warning
Collector snippet uses component ids cumulative_to_delta and otlp_http
F3 · Warning · correctness
The Collector's component ids carry no underscore: the contrib processor is cumulativetodelta and the exporter is otlphttp (the repo's own configs use cumulativetodelta/fargate in deploy/k8s-infra/templates/cluster-configmap.yaml:143 and otlphttp/maple in deploy/docker-agent/collector-config.yaml:123). Both snippets therefore fail to start with "unknown type", and the same misspelling is quoted in prose at line 517; rename them here at lines 112, 116, 132, 136 and 144-148.
Use `cumulativetodelta` and `otlphttp/dynatrace` / `otlphttp/maple` in both config blocks, and the same names in the sentence at line 517.
🤖 Prompt to fix with an AI agent
In `apps/landing/src/pages/guides/dynatrace-pricing.astro:112-133`: Collector snippet uses component ids `cumulative_to_delta` and `otlp_http`.
The Collector's component ids carry no underscore: the contrib processor is `cumulativetodelta` and the exporter is `otlphttp` (the repo's own configs use `cumulativetodelta/fargate` in `deploy/k8s-infra/templates/cluster-configmap.yaml:143` and `otlphttp/maple` in `deploy/docker-agent/collector-config.yaml:123`). Both snippets therefore fail to start with "unknown type", and the same misspelling is quoted in prose at line 517; rename them here at lines 112, 116, 132, 136 and 144-148.
Suggested fix: Use `cumulativetodelta` and `otlphttp/dynatrace` / `otlphttp/maple` in both config blocks, and the same names in the sentence at line 517.
Verify the problem exists at that location before changing it, and keep the fix to those lines.
Maple review🟢 Confidence 7/10 · likely safe to merge Adds a static Dynatrace pricing guide with a rate card, a worked monthly bill and Collector configs, plus its index and llms.txt entries. The arithmetic and Maple pricing figures check out; two earlier warnings (dead New Relic link, missing screenshot) remain unfixed at this head.
Before merge
Still open from earlier reviews
Production impactProduction traffic of the changed files (last 7 days)
What was checked
|
Maple review🟢 Confidence 8/10 · likely safe to merge This commit only removes the missing billing screenshot and states the monthly equivalent of each list price in the rate-card table. The arithmetic checks out; two previously raised defects are still present at this head.
Before merge
Still open from earlier reviews
Fixed since the last review
Production impactProduction traffic of the changed files (last 7 days)
What was checked
|
|
Merged with 2 steps from "Before merge" still open. If they are done, tick them on the review comment; if not, now is the time.
|
1 participant
Adds
/guides/dynatrace-pricing: a pricing explainer for people working out what Dynatrace will cost them before they talk to sales.What the page covers
Search intent: someone asking what Dynatrace costs (per host, per GiB, per year) and how DPS works, often comparing it with New Relic.
No client code, so no language tabs.
guide-highlight.ts: YAML keys containing/(otlp_http/dynatrace) now highlight. Every other key highlights exactly as before.Verification
otel/opentelemetry-collector-contrib:0.163.1(validate, alone and merged). In a live run, a DEBUG log record was dropped and an INFO record kept, a span reached both exporters, and the Maple exporter (with theMAPLE_TESTkey) exported without errors.bun run --cwd apps/landing buildpasses. Page reviewed at 1280 px and 390 px with Playwright./screenshots/guides/dynatrace-pricing-01-billing-usage.webp(Settings → Billing usage).Maple docs linked
/docs/reference/ingest/docs/infrastructure/hosts/pricingSources (verified 2026-10-20)
Summary by CodeRabbit
/in mapping keys.