Skip to content

GSoC 2025 Project Ideas

Devdutt Shenoi edited this page Feb 11, 2025 · 4 revisions

A list of ideas for Google Summer of Code projects with Parseable


Hi there, we at Parseable are building a database for logs, helping users store and analyze logs generated by their software infrastructure, in a quick and cost-effective way. We would love to have you on-board as a contributor for GSoC 2025. Please find below a list of ideas that you might find interesting enough to spend the summer working on with us!

1: Distributed Tracing Dashboard

Build an intuitive UI to visualize distributed traces (e.g., OpenTelemetry), allowing users to explore spans, correlate logs/metrics, and diagnose performance bottlenecks.

Objectives

  • Design a trace timeline viewer (Gantt chart or flame graph) using libraries like D3.js, VisX, or Grafana.
  • Enable click-through navigation to linked logs/events (e.g., errors, latency spikes).
  • Integrate with metrics (CPU, memory) to highlight resource constraints during trace spans.
  • Add filters (service name, duration) and search for spans.
  • Use React for frontend and integrate with Parseable’s query APIs.

Deliverables

  • Interactive trace visualization UI.
  • Metrics correlation panel.
  • Documentation for developers and end-users.

Tech Stack: React/JS(X), HTML+CSS

Repo: https://github.com/parseablehq/console

Expected Time commitment: ~350 hours

Mentor-designate: Praveen KB [email protected] (@praveen5959)

Related issue: https://github.com/parseablehq/console/issues/439

2: End-to-End Test Suite for Feature Validation

Currently the parseable server is tested with the help of quest, a not-so-comprehensive test suite to validate Parseable’s core features (ingestion, querying, retention). With this project you can implement even more checks to enable fast and fearless development, without impacting any feature expectations from Parseable.

Objectives

  • Design test cases for log ingestion, query APIs, and storage lifecycle (compaction, retention).
  • Simulate edge cases (high throughput, malformed logs).
  • Integrate with GitHub Actions/GitLab CI for automated regression testing.

Deliverables

  • Automated test suite with CI/CD integration.
  • Performance benchmarking reports.
  • Test coverage dashboard.

Tech Stack: Rust/Python/Go, Docker

Repo: https://github.com/parseablehq/quest

Expected Time commitment: ~100 hours

Mentor-designate: Devdutt Shenoi [email protected] (@de-sh)

Related issue: https://github.com/parseablehq/quest/issues/95

3: Log Collector Sink for Vector, Vault and others

Develop a Parseable sink for popular log collectors (Vector, Vault) to streamline log ingestion.

Objectives

  • Implement a Vector sink in Rust (using Vector’s SDK).
  • Create Fluentd/Logstash plugins (Ruby/Java) to forward logs to Parseable.
  • Support batch processing, retries, and auth (TLS, OAuth2).
  • Validate with formats like JSON, Syslog, and OpenTelemetry.

Deliverables:

  • Production-ready sinks/plugins.
  • Configuration examples and performance benchmarks.
  • Contributor guide for extending to other collectors.

Tech Stack: Rust (Vector), Ruby (Fluentd), Go (Vault), etc.

Expected Time commitment: ~150 hours

Mentor-designate: Nitish Tiwari [email protected] (@nitisht)

TODO: Your Own Idea

NOTE: If you have an idea to build something that would improve the lives of developers using parseable in any which way, feel free to hop on over to our slack and start a discussion with us now!

Let's discuss...

  1. Slack: http://logg.ing/community
  2. GitHub Discussions: https://github.com/orgs/parseablehq/discussions

The maintainers of the projects are listed along with the ideas as mentor designates, please discuss your GSoC project proposals by either emailing them to the relevant mentors or through the mentioned channels before submitting them.