GSoC 2022 Ideas - SigNoz

[pranay01]

Idea 1 - One Click deployments for SigNoz

Making it easier to deploy SigNoz in different environments. e.g. One click deploy in Digital Ocean, One Click deploy in GCP, AWS, Azure, or any other PaaS like Heroku.

a. Providing a single click Heroku deploy option may be a good idea to make it easy to test SigNoz for developers.
Check if current SigNoz docker can run in Heroku free tier and the compute requirements are served in the free tier of Heroku. Goal is not to test with high load but to get the application up and running with sample Hot ROD application

Relevant Issue for more idea

b. We want to make it very simple for users to install and get started with SigNoz. Digital Ocean is one of the popular platform devs use to run their infra.
We should be able to provide a simple single click install experience for SigNoz similar to what PostHog does.

Relevant Issue for more idea

Skills required/preferred - Familiarity with cloud platform AWS, GCP
Possible mentors - Prashant Shahi

Expected Size of Project - 175 hrs

Idea 2 - Integrations with alerting tools

Build integrations with other tools. e.g. Ability to send alerts in emails or integrations with other alert management tools like OpsGenie, PagerDuty. Sample issues

a. Currently SigNoz only supports sending alerts on Slack channels. Pagerduty is one of the most popular incidence management platform. Support form sending alerts from SigNoz to PagerDuty would enable such users to manage their alerts more effectively.

This would require

• Ability to create PagerDuty as a new notification channel - Should be relatively simple to do as Alertmanager already supports pagerduty
• Ability to configure which alerts is sent to which channels. This would require creating a mapper between alert types and the notification channels

Relevant Issue for more idea

b. The only alert channels available is through slack. Users would like to be able to at least send a notification to multiple parties about the alert through email.

Relevant Issue for more idea

Skills required/preferred - Golang, Backend engineering
Possible mentors - Vishal Sharma

Expected Size of Project - 175 hrs

Idea 3 - User onboarding flow for Demo environment

SigNoz sandbox environment with step by step guidance to show users different features of SigNoz. This would enable users to not need to install SigNoz if they just want to understand its capabilities. We can use a sample app to show case SigNoz's capability for this

Expected Size of Project - 175 hrs

Skills required/preferred - Frontend, ReactJS
Possible mentors - Palash Gupta

Idea 4 - Sample app with microservices for demo environment

Create a sample app with services in different languages and using differen databases which we can use in SigNoz demo environments. Instrument these apps with opentelemetry libraries so that corresponding metrics and trace data is available for users to go through.

Expected Size of Project - 175 hrs
Skills required/preferred - Fullstack engineer, NodeJS, Go
Possible mentors - Pranshu Chittora

Idea 5 - Test different Opentelemetry receivers with SigNoz and publish docs

Create sample apps for different receivers supported by OpenTelemetry and add them in SigNoz docs with detailed instructions on how to use them. This will provide a clear guide for users to follow when they are trying any of the receivers with SigNoz

Some good receivers to write guides for -

• Kafka metrics receiver
• Dockerstats Receiver
• Jaeger Receiver
• JMX Receiver

Expected Size of Project - 350 hrs
Skills required/preferred - Fullstack engineer, receiver specific technologies like Kafka, Jaeger, JMX
Possible mentors - Prashant Shahi

Idea 6 - New features

Couldn't find any ideas that piqued your interest? Well, the next option would be to make a new feature request (or any other kind of issue type) yourself! Try using SigNoz and if you find anything you felt like it was missing, then well open an issue as your submission to work on the project!

Expected Size of Project - Based on proposal