Very cool and awesome stuff! Keeping track of cloud sprawl/spend can get super stressful, esp if you are mutli-cloud! Excited to see what you all continue to ship!!
Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
51–56 of 56 posts
Re: Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
#52Earlier quoted context omitted.
we are actually trying something similar but possible kinesis + clickhouse or kafka + clickhouse. Currently kinesis seems easier to deal with but not a good intergration or sink connector available to process records at scale for kinesis to put into clickhouse. Were you ever felt into similar problems where you had to process records at huge scale to be able to insert into clickhouse without much delay. One more thin…
I'm not familiar with Kinesis's sink APIs, but yes I'd imagine you'll have to write your own connector from scratch. To answer your question, though, no: in the Kafka connector, the frequency of inserts into ClickHouse is configurable relatively independent of the batch size, so you don't need massive scale for real-time CH inserts. To save you a couple hours, here's an example config for the connector: # Snippet fro…
[deleted]
Re: Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
#53Earlier quoted context omitted.
we are actually trying something similar but possible kinesis + clickhouse or kafka + clickhouse. Currently kinesis seems easier to deal with but not a good intergration or sink connector available to process records at scale for kinesis to put into clickhouse. Were you ever felt into similar problems where you had to process records at huge scale to be able to insert into clickhouse without much delay. One more thin…
I'm not familiar with Kinesis's sink APIs, but yes I'd imagine you'll have to write your own connector from scratch. To answer your question, though, no: in the Kafka connector, the frequency of inserts into ClickHouse is configurable relatively independent of the batch size, so you don't need massive scale for real-time CH inserts. To save you a couple hours, here's an example config for the connector: # Snippet fro…
Thanks these config are helpful
Re: Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
#54Very cool! Feature request: I have really struggled with turning the thing costing me money off in AWS. If, with the right master credentials, I could consistently and easily do that somehow, that'd be a 10x feature. If you made that use-case free, you'd get tons of installations from people who desperately need this in the top of your sales funnel. edit: This used to say "in your app" and that wasn't quite what I wa…
It's very easy to do with Cloudchipr (https://app.cloudchipr.com). It allows to sort and filter and by product family (Compute, DataTransfer, Storage, etc..), then go down by tree and identify the most expensive resources under the category.
The nice part here is that when you see an instance burning $3000 a month, you can click on it and see cost break down based on traffic, compute, etc...
Re: Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
#55Very cool! Feature request: I have really struggled with turning the thing costing me money off in AWS. If, with the right master credentials, I could consistently and easily do that somehow, that'd be a 10x feature. If you made that use-case free, you'd get tons of installations from people who desperately need this in the top of your sales funnel. edit: This used to say "in your app" and that wasn't quite what I wa…
It's very easy to do with Cloudchipr ( https://app.cloudchipr.com ). It allows to sort and filter and by product family (Compute, DataTransfer, Storage, etc..), then go down by tree and identify the most expensive resources under the category. The nice part here is that when you see an instance burning $3000 a month, you can click on it and see cost break down based on traffic, compute, etc...
But is there a way to stop that instance, though?
Re: Launch HN: Dashdive (YC W23) – Track your cloud costs precisely
#56Earlier quoted context omitted.
It's very easy to do with Cloudchipr ( https://app.cloudchipr.com ). It allows to sort and filter and by product family (Compute, DataTransfer, Storage, etc..), then go down by tree and identify the most expensive resources under the category. The nice part here is that when you see an instance burning $3000 a month, you can click on it and see cost break down based on traffic, compute, etc...
But is there a way to stop that instance, though?
Sure thing! You can stop, delete, backup and delete. It supports all the actions that cloud provider supports.