Get more out of Dynatrace with community-built, ready-to-use solutions

A community-driven library of reusable Dynatrace artifacts: dashboards, apps, agents, and configurations. Built to solve real-world customer scenarios.

Save time by using one of the solutions before rebuilding them from scratch.

Get more out of Dynatrace with community-built, ready-to-use solutions

A community-driven library of reusable Dynatrace artifacts: dashboards, apps, agents, and configurations. Built to solve real-world customer scenarios.

Fresh out of the kitchen

All solutions

Results

Built something that works? Share it.

Someone else has the same problem you just solved. Add your dashboard, notebook, workflow, app or configuration to the community library and it shows up here as soon as it is merged.

Contribution guideline

Community examples and solutions are not officially maintained or supported by Dynatrace. They are shared as-is by the community. Use them as inspiration and starting points, and review them before using them in production.

Contribute a solution

If you built something in Dynatrace that solved a real problem, someone else has the same problem. Everything on this site comes straight from the community-examples repository — merge it there and it appears here.

1

Export from your environment

Export the dashboard, notebook, workflow or configuration. Strip anything environment-specific — entity IDs, management zones, host names, credentials.

2

Add a README with metadata

Copy the README template into <category>/<solution-name>/. Its metadata header (title, type, tags) controls how your solution is listed and filtered here. Add at least one screenshot.

3

Open a pull request

A maintainer reviews it against the quality criteria below. Once merged, the page picks it up on the next sync — within the hour.

Open the repository Contribution guide README template

Quality criteria

Deliberately minimal — they are what makes a solution usable by someone who isn't you.

✓
Clear customer valueIt solves a real-world problem. The README says which one, in one sentence.
✓
Production-readyUsable as-is or with minimal adjustment — not a half-finished experiment.
✓
Reusable by designNo hard-coded entity IDs, management zones or environment-specific assumptions.
✓
Properly documentedREADME with intent, prerequisites, setup steps and at least one screenshot.
✓
Meaningful layout & actionable insightFor dashboards: a layout that answers a question, not a wall of every metric.

Maintainer overview

Read-only. The repository is the single source of truth — to add, change or remove a solution, open a pull request there. This view flags what needs attention.