Dynatrace
Dynatrace is an AI-powered observability and application performance monitoring platform serving developers, operations teams, and enterprises.
About this data
Updated June 29, 2026
Overall Pulse Score
-1 over this period
A 0-100 index summarizing the tone of 46 relevant public mentions gathered from public online communities across 8 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Discussion around Dynatrace over the recent period skewed heavily negative, with bug reports dominating the conversation and accounting for the majority of mentions. Commenters frequently raised reliability concerns, including issues with HTTP errors during certificate uploads, broken dashboard examples, and failures triggering autonomous investigations. A handful of praise surfaced around integrations and AI quality features, with at least one commenter sharing a positive walkthrough of sending telemetry via OTLP. Several mentions also focused on missing functionality and feature requests for broader API and sampler coverage.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How Dynatrace compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 46 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 46 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“Using --http (spawn an http server) leads to "Already connected to a transport. Call close() before connecting to a new transport, or use a separate Protocol instance per connection". **Describe the bug** When starting @dynatrace-oss/dynatrace-mcp-server version 1.4.0 or 1.5.0 wi...”
“chat_with_davis_copilot: Remove repeating LLM question. **Is your feature request related to a problem? Please describe.** Refer to: https://github.com/dynatrace-oss/dynatrace-mcp/blob/main/src/index.ts#L1001 Waste of context space? (feedback from customers testing MCP) **Describ...”
“[Bug]: Error Http 400 when uploading certificat to tenant. ### Description Having problems setting up workspaces and uploading the certificat to Tenant, get a http 400. Tried several schema versions and all give the same issue, tried from work installation and home no proxies etc...”
“How to send Claude Code telemetry to Dynatrace (OTLP) — 3 steps. # Send Claude Code telemetry to Dynatrace (OTLP) — 3 steps Claude Code already speaks OTLP. To get its metrics + logs/events into Dynatrace, you just point an OpenTelemetry Collector at Dynatrace's native OTLP endpo...”
“creating context with environment url without protocol, leads to broken context. ### What happened? DQL queries failed with Steps to reproduce I created a context using dtctl auth login --context dev --environment .apps.dynatrace.com. The login succeeded, but when I tried to exec...”
216+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bug reports and reliability complaints dominated discussion by a wide margin over the four-week window.
- Sentiment showed a brief spike in late May but retreated sharply once discussion volume increased in June.
- Opinion was divided on integration depth, with some commenters praising existing support while others pushed for expanded coverage.
- Positive mentions around AI features and OTLP connectivity existed but were outnumbered and did not shift the overall tone.
| Praise theme | Mentions |
|---|---|
| Strong features | 4 |
| Good integrations | 2 |
| AI quality | 2 |
| Reliability | 1 |
| Performance | 1 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 25 |
| Reliability | 10 |
| Missing features | 7 |
| Easy to use | 4 |
| Lacking integrations | 4 |
Public discussion around Dynatrace over the recent four-week window was heavily weighted toward frustration, with bug reports and reliability concerns accounting for the vast majority of negative mentions. Commenters raised issues spanning HTTP errors during certificate uploads, broken dashboard JSON examples, and failures to trigger autonomous investigation workflows, giving the complaint side of the conversation a distinctly operational flavor. The sheer volume of bug-related mentions dwarfed praise by a wide margin, and several mentions pointed to reliability problems that suggested persistent rather than one-off issues.
The score trajectory over this period tells a turbulent story. Discussion started at a low point in late February and sank further through April, with scores bottoming out around the mid-20s at one point. A sharp rebound appeared in late May, pushing sentiment into clearly positive territory, but that recovery proved short-lived. The heaviest weeks of discussion in early June saw scores fall back into the low-to-mid 30s and 40s, suggesting the spike may have been an outlier tied to limited mentions rather than a genuine mood shift. By the final week of the window, sentiment had settled into a narrow, modestly negative range.
Praise did surface, though it remained a minority voice. Commenters expressed positive sentiment around specific integrations and AI-related capabilities, with a few mentions highlighting performance positives. The OpenTelemetry and OTLP connectivity angle drew constructive, how-to style discussion, which carried a more neutral-to-positive tone compared to the bug threads.
Opinion was most divided around integration and extensibility. Some commenters celebrated what Dynatrace already supports in that space, while others filed feature requests for broader sampler support and missing API coverage, indicating a gap between expectations and current implementation. Ease-of-use complaints added a quieter but consistent undercurrent of dissatisfaction that ran alongside the louder bug conversation.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
-1 over this period
A 0-100 index summarizing the tone of 46 relevant public mentions gathered from public online communities across 8 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
Dynatrace
40
Trainual
88
Score-level preview from live weekly tracking.
Are you Dynatrace?
Get a private enterprise dashboard for your product - full history, every source, theme deep-dives, and weekly alerts. You can also respond to the data shown here.
Explore the enterprise dashboardAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Is Dynatrace your product?
See everything behind this page - full history, every source, theme deep-dives, and weekly alerts - in a private enterprise dashboard.
Request early accessCompare with similar tools
Safari MCP Server
A Model Context Protocol server that gives AI assistants programmatic access to Safari browser automation for developers.
Free
View DetailsRevenueCat
A platform that manages in-app purchases, subscriptions, and revenue analytics for iOS and Android app developers.
Free tier; paid plans available
View Details