Skip to content

🎰 Welcome to the Vegas Casino Observability Hackathon!

🏆 Hackathon Challenges
View all hackathon challenges organized by track (GitHub Copilot and Dynatrace). Start your journey here!

💻 Development Workflow
Understand how to make changes, build images, and deploy updates. Learn about the GitHub Actions workflow and Helm deployments.

☁️ Environment Setup
Learn about the DevContainer environment and deployment architecture. Understand kind, OpenFeature, cert-manager, and more.

🎯 What is This Hackathon?

Hackathon Kickoff: What You’ll Build & What to Expect

The Vegas Casino Observability Hackathon is a hands-on learning experience where you'll:

  • Learn GitHub Copilot: Master AI-assisted development with GitHub Copilot
  • Improve Observability: Enhance OpenTelemetry instrumentation using Copilot
  • Work with Dynatrace: Query data, create dashboards, and build custom apps
  • Practice Real-World Skills: Work with microservices, Kubernetes, and feature flags

🚀 Quick Start

Prerequisites

Before you begin, ensure you have:

  • ✅ A GitHub account
  • ✅ Access to GitHub Copilot (included with GitHub subscription)
  • ✅ Ability to fork this repository
  • ✅ An email address for Dynatrace tenant access

Getting Started

  1. Fork the Repository

  2. Fork this repository to your GitHub account

  3. Start the Hackathon

  4. Visit the Hackathon Challenges page
  5. Begin with GitHub Copilot Challenge 01
  6. Complete challenges in order, then move to Dynatrace challenges

📋 Challenge Overview

See the Hackathon Challenges page for a complete overview of all challenges organized by track.

🏗️ The Vegas Casino Application

The hackathon uses a microservices-based casino application with:

  • 4 Game Services: Slots (Node.js), Roulette (Python), Dice (Go), Blackjack (Node.js)
  • Frontend Service: Web UI for players
  • Scoring Service: Leaderboards and statistics (Java/Spring Boot)
  • Dashboard Service: Analytics and reporting
  • Supporting Infrastructure: Redis, PostgreSQL, OpenTelemetry Collector

All services are pre-instrumented with OpenTelemetry and deployed in a Kubernetes cluster running in your DevContainer.

🔄 Development Workflow

Important: Building Images

You don't build images locally! All Docker images are built automatically via GitHub Actions when you:

  1. Make code changes in your forked repository
  2. Commit and push your changes
  3. GitHub Actions automatically builds new Docker images
  4. Update your Helm deployment to use the new images

See the Development Guide for details on: - Where source code is located - How GitHub Actions builds images - How to update your deployment with Helm

🎓 Learning Path

graph LR
    A[Fork Repository] --> B[GitHub Copilot<br/>Challenge 01]
    B --> C[Challenge 02]
    C --> D[Challenge 03]
    D --> F[Dynatrace<br/>Challenge 00]
    F --> G[Challenge 01]
    G --> H[Challenge 02]
    H --> I[Challenge 03]
    I --> J[Bonus Challenges]
    J --> K[Challenge 04<br/>Copilot]
    J --> M[Challenge 05<br/>B-MAD Agent]
    J --> L[Challenge 04<br/>Dynatrace]

    style A fill:#9333ea
    style F fill:#06b6d4
    style J fill:#f59e0b
    style K fill:#10b981
    style M fill:#10b981
    style L fill:#10b981

📚 Additional Resources

🆘 Need Help?

  • Check the individual challenge pages for detailed instructions
  • Review the Environment Setup guide for troubleshooting
  • Consult the Development Guide for workflow questions

Ready to start? Visit the Hackathon Challenges page to begin!