Take the Open Source Treasure Challenge, the last challenge like this! ‌‌‌‌‌‌‌‌‌‌🔑‌

[Michal_Gebacki]

Dear Dynatrace Community, a big changes are along the way!

Before we'll shed some light on the planned changes in the Community Challenges formula, let us introduce you to this month's Community Challenge. Spare some time to take part in it, as in the future this format will look way different! Theme of June: open source features, about which you can read a lot on the Dynatrace Community!

How to take this Community Challenge?

1. Go to the Open Source Tool tag

2. Explore all of features that Dynatrace Experts have briefly introduced to you in a respective four blog posts.

3. Choose which of Open Source Tools would you learn better and test in your work environment.

4. Take some notes from your tests and share with us benefits or gains you see in the particular open source feature.

5. Let's see which open source features address some crucial business needs!

Can't wait for your use cases! 👀

Benefits of taking this Community Challenge:

👉 Every participant receives a "Open Source Advocate" badge

👉 You will also get +100 bonus points for extra activity

👉 Engage with others and have fun!

Community Challenge evolution: what and when is going to change?

Alright, now it's time to introduce you to the planned Community Challenge overhaul. Starting from the middle of next month, July 2026, we're kicking off a new format of OpenSource Community Challenges. It will be designed differently, including more interactive chapters, and a whole focus on the open source aspect. More details will be shared with you in two weeks when the next Community Newsletter will be published.

And for now... Let's celebrate the end of a beautiful era and take the very last Community Challenge in its current form! It was a great journey, but it's not a farewell. It's just a complex evolution and manifesto of the wise words, that the only constant - is change. 

[Michal_Gebacki]

Can't wait to see the very first answer! 👀

[MaximilianoML]

Hello @Michal_Gebacki,

I’m not sure if this is the right place, but the links you shared brought me here:

[Michal_Gebacki]

Hello, @MaximilianoML and @SachinJindal & @SachinJindal!

We are deeply sorry for this inconvenience, the link has changed in the meantime due to the Forum Navigation's changes, it has been fixed now.

Hope it won't discourage you from taking the challenge eventually, fingers crossed! 😄

[AntonPineiro]

Hi,

Looks like it is working now.

Best regards

[SachinJindal]

same its just redirect to blank page .. 

[t_pawlak]

I have the same.

[MaximilianoML]

Hi team!

For this challenge, I would choose dtctl as the open-source tool I explored and applied in a real Dynatrace use case.

In my case, I used dtctl while building a custom Dynatrace App called Audit Lens. The goal of the app is to improve the way we investigate Dynatrace Audit Logs, especially when the user does not already know exactly which DQL query to write or which fields to search for.

Audit logs can be extremely valuable, but they are not always easy to explore. Sometimes you know the question you want to answer, for example:

Who removed permissions from another user?

But you may not immediately know which fields, providers, actions, or event types are relevant. Audit Lens tries to reduce that friction by providing a more guided investigation experience, with quick searches, contextual insights, and drilldown capabilities on top of audit data.

Where dtctl brought value was in the development workflow around the app. I used it together with an Agentic Development approach based on Spec-Driven Development. Instead of treating the app as a one-off manual build, I used specifications to describe the expected behavior, investigation flows, app structure, and Dynatrace-specific requirements.

Then, with an AI engineering agent and dtctl, I could iterate faster and keep the work more aligned with Dynatrace App development practices.

In this use case, dtctl helped by supporting a more structured development lifecycle for the Dynatrace App, especially around:

• Bootstrapping and managing the Dynatrace App project
• Keeping the app workflow closer to a repeatable engineering process
• Validating and running the app locally during development
• Supporting faster iteration between specification, implementation, and testing
• Making the development process more suitable for AI-assisted engineering

The current version of Audit Lens still has improvements to be made, but the picture today already works very well. It shows how a Dynatrace App can turn raw audit log data into a more accessible investigation experience, and how dtctl can help developers move faster while still keeping structure and control in the development process.

For me, the main business value is clear: dtctl helps make Dynatrace custom app development more scalable, repeatable, and easier to integrate into modern engineering workflows.

It is especially powerful when combined with AI-assisted development, because the agent can work against a clear specification while dtctl keeps the Dynatrace App lifecycle practical and executable.

[Malaik]

Hi,

Snowflake is the one interesting me as we want to introduce this part in our ENV,

will try to test it further and share if possible,

Regards,