💡 Help Us Help You: What Troubleshooting Topics Should We Cover Next?

[Adam-Piotrowicz]

At Dynatrace, we’re constantly working to make your experience smoother and more efficient. Our Troubleshooting Knowledge Base is designed to help you quickly resolve common issues and discover best practices, but we know there’s always room to improve!

That’s where you come in. 🫵

We’d love to hear from you:
👉 What topics would you like to see covered in future troubleshooting articles?
👉 Are there specific challenges you’ve faced that could use a deeper dive or step-by-step guidance?

Whether it’s about OneAgent deployment, log ingestion, Kubernetes monitoring, or something else entirely - your feedback helps us create content that truly matters.

Here you can see examples of our last year's most popular articles, which have already helped hundreds of Dynatrace users to make their software work perfectly and understand their business like never before:

📖 Troubleshooting automatic RUM injection failures

📖 Troubleshooting RUM correlation issues for web applications

📖 Synthetic Troubleshooting Map

📖 Synthetic Browser Monitor Error Codes

📖 Troubleshooting Kubernetes CPU Throttling Problems in Dynatrace

📖 Why my logs are not visible in Dynatrace?

So, if you have anything you would like to learn from us on your mind, 📬 drop your suggestions in the comments below. 👇

Thank you for being an active member of our Community! 🧑‍💻

[sujit_k_singh]

Hi @Adam-Piotrowicz 

One topic I think would be really useful is advanced troubleshooting for API-based ActiveGate extensions. In many enterprise environments, SNMP is blocked for security reasons, so we rely on REST API integrations for devices like F5 BIG-IP, Palo Alto, Cisco APIC, and Citrix NetScaler. These API-based setups often run into issues with authentication, SSL/TLS certificates, rate limits, and schema changes after firmware upgrades. A guide that walks through diagnosing these problems and validating API calls would help a lot of teams.

Another area worth covering is OpenPipeline ingestion delays and timestamp limitations. When connectivity issues occur, BizEvents can hit the 24-hour cutoff, which creates challenges for data accuracy. It would be great to see best practices for designing resilient pipelines—like buffering, retry logic, and how to handle original timestamps for reporting—so users can avoid losing critical business events.

[AntonPineiro]

Hi,

I would like some dummy article for about custom extensions framework 2.0, from scratch.

Best regards

[m3tomlins]

I would generally like to ask for more troubleshooting around Dynatrace Configuration and Administration:
 - how to detect and mitigate unexpected entity id changes
 - how to maintain a consistent configuration across multiple tenants
 - adapting/migrating IAM permissions
 - maintaining custom service detection rules/detecting code or entry-point changes
 - managing bizevent configurations across divergent implementations of the same service/process

Thank you for all that you do to help us do more with Dynatrace!

[NicoleMT]

Hello, it would be very helpful to have a more detailed guide for creating SQL extensions. Currently, for example, the Custom Extensions Creator app does not provide a step-by-step guide or a tutorial that clearly explains the complete process of creating an extension from scratch, so having clearer and more structured documentation would be a significant improvement.

[dannemca]

I would suggest troubleshooting the Dynatrace Operator, specially the dynakube yaml.

There are so many config options to be included in the dynakube, and the default one we get from deployment page is way too simple.

What others options we have to enhance our deployment when instrumenting a cluster?

What/where to look for when a pod is not instrumented?

Thanks.

[Julius_Loman]

Event many of the cases are already documented at https://docs.dynatrace.com/docs/shortlink/monitoring-troubleshooting , there are still gaps, especially when it comes to fine-tuning the operator deployment itself and most importantly the CSI driver.