Splunk Build-a-thon!

334 Registered Разрешённый размер команды: 1 - 2
334 Registered Разрешённый размер команды: 1 - 2
этап подачи идей
Онлайн
starts on:
Apr 28, 2025, 04:00 PM UTC (UTC)
ends on:
May 26, 2025, 12:00 AM UTC (UTC)
Prototype Phase
Онлайн
starts on:
May 26, 2025, 04:00 PM UTC (UTC)
ends on:
Jun 23, 2025, 12:00 AM UTC (UTC)

Track 1 - Resources

Track 1: Splunk App Development

Tech Stack / Tools

  • Local Splunk Enterprise for Development / Testing

  • SCDE for cloud testing

  • Usage of Splunk’s app development frameworks is recommended but not required

App Requirements

  • The app must be a fully functional Splunk App that provides tangible value to Splunk users. It will be evaluated based on its impact and usefulness.

  • Apps should follow general best practices for security, performance, and usability as outlined in the Splunk Cloud Ready App Guidelines and align with AppInspect standards.

  • The app should address real customer challenges or improve the efficiency of Splunk administrators by streamlining workflows, enhancing data insights, or optimizing Splunk operations.

App Functionality

  • The app should include interactive dashboards, reports, or visualizations that help users analyze and interpret data effectively.

  • The app should offer an intuitive and well-structured interface, making it easy for users to interact with and extract value from the data.

Deployment / Compatibility

  • App must be installable on SCDE

  • Follow Splunk AppInspect guidelines

  • Should work across different Splunk environments (Splunk Cloud / Splunk Enterprise)

Code Submission

  • The app’s source code must be submitted via a GitHub, GitLab, or similar source repository. It can be public or private, but private repositories must grant access to judges for evaluation.

  • The submission must include a README file with the following:

    • Setup instructions

    • Usage details

    • Any dependencies / prerequisites required to run the app (Optional)

  • Participants must provide clear instructions on how to test the app, including:

    • Steps to connect the app to a product/service API (if applicable)

    • Screenshots or logs demonstrating the app’s functionality when properly configured

    • Example configurations or test data (Optional)

  • Code should be well-structured, commented, and easy to understand, ensuring maintainability and ease of review by judges.

Documentation

  • Participants must submit a brief (1-page maximum) document or a maximum of 5-minute demo video covering the following:

    • A clear explanation of the problem the app solves and how it benefits users.

    • Define the primary users of the app (e.g., Splunk admins, security analysts, IT operations teams, etc.).

    • Describe how the app interacts with Splunk, including data ingestion, processing, visualization, or automation features.

    • A short demo video showcasing the app’s functionality, key features, and how users can interact with it. (Optional)

    • Provide a brief technical overview in written form or as a diagram, outlining key components, workflows, and integrations. (Optional)

Поделиться в социальных сетях

?