Skip to content

Codespaces#

dt-badge

This Codespace leverages the Dynatrace Enablement Framework, providing a robust and flexible development environment. Key features include:

  • Seamless operation within GitHub Codespaces, as a remote container, or locally via Docker.
  • Cross-compilation support for both AMD and ARM architectures, ensuring broad compatibility.
  • Adherence to industry standards and best practices to optimize the developer experience.
  • Real-time observability of Kubernetes clusters using Dynatrace Full-Stack monitoring.
  • Integrated Dynatrace MCP Server to deliver deep, actionable insights across distributed systems.

To learn more about the Dynatrace Enablement Framework and how it can enhance your development workflow, please refer to the official documentation

1. Launch Codespace#

Open in GitHub Codespaces

1.1 Codespaces configuration#

Branch, Machine sizing & secrets

  • Branch
    • select the main branch
  • Machine sizing
    • As a machine type select 4-core
  • Secrets (enter your credentials within the following variables)
    • DT_ENVIRONMENT
    • DT_OPERATOR_TOKEN
    • DT_INGEST_TOKEN
    • DT_APP_OAUTH_CLIENT_ID
    • DT_APP_OAUTH_CLIENT_SECRET

2. Explore what has been deployed#

Your Codespace has now deployed the following resources:

  • A local Kubernetes (kind) cluster monitored by Dynatrace, with some pre-deployed apps that will be used later in the demo.

  • The Todo Java App and the Bugzapper Node.js app which will be used in our debugging quiz

  • The Dynatrace Quiz App which will be available at https://yourTenantID.apps.dynatrace.com/ui/apps/my.bug.busters/

3. Tips & Tricks#

The client kubectl is configured for you automatically.

Exposing the apps to the public#

The app TODO app and Bugzapper apps are being exposed from the devcontainer to your localhost or the github dns domain. If you want to make the endpoints publicly accesible, just go to the ports section in VsCode, right click on them and change the visibility to public.

4. Troubleshooting#

If there is an issue with the application, we recommend you verify the health of the Kind cluster. 

kubectl cluster-info

Validate the pods are running successfully: 

kubectl get pods -n bugzapper

kubectl get pods -n todoapp

kubectl get pods -n dynatrace

Now let's get started with the bug hunting. Click below to start.