The best Hacker News stories from Show from the past day
Latest posts:
Launch HN: SigNoz (YC W21) – Open-source alternative to DataDog
Hi HN,<p>Pranay and Ankit here. We’re founders of SigNoz ( <a href="https://signoz.io" rel="nofollow">https://signoz.io</a> ), an open source observability platform. We are building an open-core alternative to DataDog for companies that are security and privacy conscious, and are concerned about huge bills they need to pay to SaaS observability vendors.<p>Observability means being able to monitor your application components - from mobile and web front-ends to infrastructure, and being able to ask questions about their states. Things like latency, error rates, RPS, etc. Better observability helps developers find the cause of issues in their deployed software and solve them quickly.<p>Ankit was leading an engineering team, where we became aware of the importance of observability in a microservices system where each service depended on the health of multiple other services. And we saw that this problem was getting more and more important, esp. in today’s world of distributed systems.<p>The journey of SigNoz started with our own pain point. I was working in a startup in India. We didn’t use application monitoring (APM) tools like DataDog/NewRelic as it was very costly, though we badly needed it. We had many customers complaining about broken APIs or a payment not processing - and we had to get into war room mode to solve it. Having a good observability system would have allowed us to solve these issues much more quickly.<p>Not having any solution which met our needs, we set out to do something about this.<p>In our initial exploration, we tried setting up RED (Rate, Error and Duration) and infra metrics using Prometheus. But we soon realized that metrics can only give you an aggregate overview of systems. You need to debug why these metrics went haywire. This led us to explore Jaeger, an open source distributed tracing system.<p>Key issues with Jaeger were that there was no concept of metrics in Jaegers, and datastores supported by Jaeger lacked aggregation capabilities. For example, if you had tags of “customer_type: premium” for your premium customers, you couldn’t find p99 latency experienced by them through Jaeger.<p>We found that though there are many backend products - an open source product with UI custom-built for observability, which integrates metrics & traces, was missing.<p>Also, some folks we talked to expressed concern about sending data outside of boundaries - and we felt that with increasing privacy regulations, this would become more critical. We thought there was scope for an open source solution that addresses these points.<p>We think that currently there is a huge gap between the state of SaaS APM products and OSS products. There is a scope for open core products which is open source but also supports enterprise scale and comes with support and advanced features.<p>Some of our key features - (1) Seamless UI to track metrics and traces (2) Ability to get metrics for business-relevant queries, e.g. latency faced by premium customers (3) Aggregates on filtered traces, etc.<p>We plan to focus next on building native alert managers, support for custom metrics and then logs ( waiting for open telemetry logs to mature more in this). More details about our roadmap here ( <a href="https://signoz.io/docs/roadmap" rel="nofollow">https://signoz.io/docs/roadmap</a> )<p>We are based on Golang & React. The design of SigNoz is inspired by streaming data architecture. Data is ingested to Kafka and relevant info & meta-data is extracted by stream processing. Any number of processors can be built as per business needs. Processed data is ingested to real-time analytics datastore, Apache Druid, which powers aggregates on slicing and dicing of high dimensional data. In the initial benchmarks we did for self-hosting SigNoz, we found that it would be 10x more cost-effective than SaaS vendors ( <a href="https://signoz.io/blog/signoz-benchmarks/" rel="nofollow">https://signoz.io/blog/signoz-benchmarks/</a> )<p>We’ve launched this repo under MIT license so any developer can use the tool. The goal is to not charge individual developers & small teams. We eventually plan on making a licensed version where we charge for features that large companies care about like advanced security, single sign-on, advanced integrations and support.<p>You can check out our repo at <a href="https://github.com/SigNoz/signoz" rel="nofollow">https://github.com/SigNoz/signoz</a> We have a ton of features in mind and would love you to try it and let us know your feedback!
Launch HN: SigNoz (YC W21) – Open-source alternative to DataDog
Hi HN,<p>Pranay and Ankit here. We’re founders of SigNoz ( <a href="https://signoz.io" rel="nofollow">https://signoz.io</a> ), an open source observability platform. We are building an open-core alternative to DataDog for companies that are security and privacy conscious, and are concerned about huge bills they need to pay to SaaS observability vendors.<p>Observability means being able to monitor your application components - from mobile and web front-ends to infrastructure, and being able to ask questions about their states. Things like latency, error rates, RPS, etc. Better observability helps developers find the cause of issues in their deployed software and solve them quickly.<p>Ankit was leading an engineering team, where we became aware of the importance of observability in a microservices system where each service depended on the health of multiple other services. And we saw that this problem was getting more and more important, esp. in today’s world of distributed systems.<p>The journey of SigNoz started with our own pain point. I was working in a startup in India. We didn’t use application monitoring (APM) tools like DataDog/NewRelic as it was very costly, though we badly needed it. We had many customers complaining about broken APIs or a payment not processing - and we had to get into war room mode to solve it. Having a good observability system would have allowed us to solve these issues much more quickly.<p>Not having any solution which met our needs, we set out to do something about this.<p>In our initial exploration, we tried setting up RED (Rate, Error and Duration) and infra metrics using Prometheus. But we soon realized that metrics can only give you an aggregate overview of systems. You need to debug why these metrics went haywire. This led us to explore Jaeger, an open source distributed tracing system.<p>Key issues with Jaeger were that there was no concept of metrics in Jaegers, and datastores supported by Jaeger lacked aggregation capabilities. For example, if you had tags of “customer_type: premium” for your premium customers, you couldn’t find p99 latency experienced by them through Jaeger.<p>We found that though there are many backend products - an open source product with UI custom-built for observability, which integrates metrics & traces, was missing.<p>Also, some folks we talked to expressed concern about sending data outside of boundaries - and we felt that with increasing privacy regulations, this would become more critical. We thought there was scope for an open source solution that addresses these points.<p>We think that currently there is a huge gap between the state of SaaS APM products and OSS products. There is a scope for open core products which is open source but also supports enterprise scale and comes with support and advanced features.<p>Some of our key features - (1) Seamless UI to track metrics and traces (2) Ability to get metrics for business-relevant queries, e.g. latency faced by premium customers (3) Aggregates on filtered traces, etc.<p>We plan to focus next on building native alert managers, support for custom metrics and then logs ( waiting for open telemetry logs to mature more in this). More details about our roadmap here ( <a href="https://signoz.io/docs/roadmap" rel="nofollow">https://signoz.io/docs/roadmap</a> )<p>We are based on Golang & React. The design of SigNoz is inspired by streaming data architecture. Data is ingested to Kafka and relevant info & meta-data is extracted by stream processing. Any number of processors can be built as per business needs. Processed data is ingested to real-time analytics datastore, Apache Druid, which powers aggregates on slicing and dicing of high dimensional data. In the initial benchmarks we did for self-hosting SigNoz, we found that it would be 10x more cost-effective than SaaS vendors ( <a href="https://signoz.io/blog/signoz-benchmarks/" rel="nofollow">https://signoz.io/blog/signoz-benchmarks/</a> )<p>We’ve launched this repo under MIT license so any developer can use the tool. The goal is to not charge individual developers & small teams. We eventually plan on making a licensed version where we charge for features that large companies care about like advanced security, single sign-on, advanced integrations and support.<p>You can check out our repo at <a href="https://github.com/SigNoz/signoz" rel="nofollow">https://github.com/SigNoz/signoz</a> We have a ton of features in mind and would love you to try it and let us know your feedback!
Show HN: Weekend project, shows when the next season of your TV show premieres
I treated myself to a solo hackathon this weekend and built
<a href="https://next-season-of.com" rel="nofollow">https://next-season-of.com</a>. The data is scrapped from IMDB and the website is generated using the hugo template engine. There's still a lot of optimization to be done but I'm planning to use this as a learning ground to try and get my pages to rank in Google. It would be really cool to search "next season of Ozark" and see a link to next-season-of.com.
Show HN: Weekend project, shows when the next season of your TV show premieres
I treated myself to a solo hackathon this weekend and built
<a href="https://next-season-of.com" rel="nofollow">https://next-season-of.com</a>. The data is scrapped from IMDB and the website is generated using the hugo template engine. There's still a lot of optimization to be done but I'm planning to use this as a learning ground to try and get my pages to rank in Google. It would be really cool to search "next season of Ozark" and see a link to next-season-of.com.
Launch HN: Infracost (YC W21) – open-source cloud cost estimator
Hi, we’re Ali, Hassan and Alistair and we co-founded Infracost (<a href="https://www.infracost.io" rel="nofollow">https://www.infracost.io</a>). Infracost is an open-source cloud cost estimator for your pull requests. When you change your infrastructure code (Terraform), Infracost posts a comment in the pull request, which tells you the impact of this change to your cloud bill, e.g. “this will increase your bill by 25% next month”.<p>Existing cloud cost management products focus on post-bill analysis and target finance and management teams via charting dashboards. We built one of these back in 2013. They are all missing an important piece - the people who are responsible for purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them. We want to make cloud costs simpler to understand for developers and DevOps so they can make better decisions, which we believe will lead to more cost-efficient systems.<p>In 2011 Ali and Hassan started a cloud cost forecasting company based on Ali’s PhD research. They applied to YC and got through to the interview round. RightScale acquired them in 2012. I read about their YC interview experience on HN, reached out and ended up joining them. We went on to form the team that built RightScale’s cloud cost management product (now called Flexera Optima).<p>In our most recent startup (which failed) we were launching cloud stacks for users on-demand and we wanted a way to work out the cost of each. We hacked together something by building a GraphQL-based cloud pricing API and a CLI that parsed our Terraform code and output a cost breakdown.<p>We released the code on GitHub as Infracost and discovered that others had similar problems. We got requests to support more cloud services and integrate it into pull requests. At the moment, Infracost supports Terraform for AWS and Google Cloud (we’re adding new resources every week). It can be integrated into GitHub, GitLab, CircleCI, Bitbucket and Atlantis, or can be used anywhere through the CLI. In the future we plan to add support for more cloud vendors and infrastructure-as-code tools (Azure, CloudFormation, Pulumi, etc).<p>We now spend a lot of our days trawling through the cloud pricing pages working out how pricing works for different cloud services. We’re grateful for the contributors who have helped us with this. AWS currently has over 2 million price points and this is constantly increasing. Users are requesting better support for usage-based services like data transfer, S3 and Lambda. Currently we allow for usage estimates to be passed into the tool, and are looking at other methods, i.e. based on last month’s actual usage. We’ve also learned, the hard way, the importance of UX in CLI and workflow tools.<p>So far we are seeing a few use-cases for Infracost. Some enterprise users have integrated it into their “self-service” cloud catalog to set cost expectations before provisioning. Other users have integrated it into their CI pipeline as a safety net to catch unexpected costs. And some users are running it at design time to compare options and model usage.<p>We’ve talked to Sid Sijbrandij (CEO of GitLab), and Ian Tien (CEO of Mattermost) about when and how to monetize. Currently we are thinking about a buyer-based open core approach, in which the individual contributor edition will always be free, and enterprise paid features will include multi-team support, management reports and private cloud support.<p>We’d really appreciate it if you try it out and give us feedback. You can check out the repo at <a href="https://github.com/infracost/infracost" rel="nofollow">https://github.com/infracost/infracost</a>. We’d love your thoughts on our approach, and anything that has worked, or hasn’t worked for you when it comes to managing cloud costs.
Launch HN: Infracost (YC W21) – open-source cloud cost estimator
Hi, we’re Ali, Hassan and Alistair and we co-founded Infracost (<a href="https://www.infracost.io" rel="nofollow">https://www.infracost.io</a>). Infracost is an open-source cloud cost estimator for your pull requests. When you change your infrastructure code (Terraform), Infracost posts a comment in the pull request, which tells you the impact of this change to your cloud bill, e.g. “this will increase your bill by 25% next month”.<p>Existing cloud cost management products focus on post-bill analysis and target finance and management teams via charting dashboards. We built one of these back in 2013. They are all missing an important piece - the people who are responsible for purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them. We want to make cloud costs simpler to understand for developers and DevOps so they can make better decisions, which we believe will lead to more cost-efficient systems.<p>In 2011 Ali and Hassan started a cloud cost forecasting company based on Ali’s PhD research. They applied to YC and got through to the interview round. RightScale acquired them in 2012. I read about their YC interview experience on HN, reached out and ended up joining them. We went on to form the team that built RightScale’s cloud cost management product (now called Flexera Optima).<p>In our most recent startup (which failed) we were launching cloud stacks for users on-demand and we wanted a way to work out the cost of each. We hacked together something by building a GraphQL-based cloud pricing API and a CLI that parsed our Terraform code and output a cost breakdown.<p>We released the code on GitHub as Infracost and discovered that others had similar problems. We got requests to support more cloud services and integrate it into pull requests. At the moment, Infracost supports Terraform for AWS and Google Cloud (we’re adding new resources every week). It can be integrated into GitHub, GitLab, CircleCI, Bitbucket and Atlantis, or can be used anywhere through the CLI. In the future we plan to add support for more cloud vendors and infrastructure-as-code tools (Azure, CloudFormation, Pulumi, etc).<p>We now spend a lot of our days trawling through the cloud pricing pages working out how pricing works for different cloud services. We’re grateful for the contributors who have helped us with this. AWS currently has over 2 million price points and this is constantly increasing. Users are requesting better support for usage-based services like data transfer, S3 and Lambda. Currently we allow for usage estimates to be passed into the tool, and are looking at other methods, i.e. based on last month’s actual usage. We’ve also learned, the hard way, the importance of UX in CLI and workflow tools.<p>So far we are seeing a few use-cases for Infracost. Some enterprise users have integrated it into their “self-service” cloud catalog to set cost expectations before provisioning. Other users have integrated it into their CI pipeline as a safety net to catch unexpected costs. And some users are running it at design time to compare options and model usage.<p>We’ve talked to Sid Sijbrandij (CEO of GitLab), and Ian Tien (CEO of Mattermost) about when and how to monetize. Currently we are thinking about a buyer-based open core approach, in which the individual contributor edition will always be free, and enterprise paid features will include multi-team support, management reports and private cloud support.<p>We’d really appreciate it if you try it out and give us feedback. You can check out the repo at <a href="https://github.com/infracost/infracost" rel="nofollow">https://github.com/infracost/infracost</a>. We’d love your thoughts on our approach, and anything that has worked, or hasn’t worked for you when it comes to managing cloud costs.
Show HN: "Programming Algorithms in Lisp” Book
Show HN: "Programming Algorithms in Lisp” Book
Show HN: Clerk – all of user management as-a-service, not just authentication
Show HN: Clerk – all of user management as-a-service, not just authentication
Show HN: Clerk – all of user management as-a-service, not just authentication
Show HN: One thousand in – I've built an IPO “FOMO” web app
Show HN: Stamp turns a folder into a plain text file and a file into a folder
Show HN: Stamp turns a folder into a plain text file and a file into a folder
Show HN: Stamp turns a folder into a plain text file and a file into a folder
Show HN: SVG Shape Generator – Create organic-looking shapes for your designs
Show HN: You-tldr – easy-to-read transcripts of Youtube videos
Show HN: You-tldr – easy-to-read transcripts of Youtube videos
Show HN: You-tldr – easy-to-read transcripts of Youtube videos
Show HN: You-tldr – easy-to-read transcripts of Youtube videos