3 ms·
Maker here. I created DatabaseLog as an internal tool to provide our marketing team with a simple way to track monthly performance (Registered users, Posted job
by rosaldo 6y ago
Maker here. I created DatabaseLog as an internal tool to provide our marketing team with a simple way to track monthly performance (Registered users, Posted jobs etc.) and compare to past performance on our MongoDB data and decided to release it to the world in case it's useful for other makers/teams.
Here's how it works:
1. Connect to remote MongoDB database
2.Define metrics once, simply as creating a {query} or an [aggregation] on your data
3.Analyze changes in your site's performance over various lengths of time and compare to past performance
There is a Free account to track up to 3 metrics and unlimited to track unlimited metrics for $29/month, but payments aren't connected so it's free for unlimited metrics now.
I'm aware there is MongoDB Charts, but I personally wanted something easier to use just for analytics and not only for databases hosted on Mongo Atlas.
I'm transparent about what it stores (https://databaselog.com/doc/we-do-not-store-your-data https://databaselog.com/doc/we-do-not-store-your-data) and recommend using it with read-only user to be 100% safe nothing changes.
If you're interested in how I built Databaselog, I shared my progress publicly (https://twitter.com/MattHlavacka/status/1264172956130869248 https://twitter.com/MattHlavacka/status/1264172956130869248)
Please let me know if you're interested or have any feedback.
- guzik 6y agoGetting: Oops! <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Internal Server Error</pre> </body> </html> during the registration. Hug of death?
- rosaldo 6y agoFixed. Lesson learned - don't post on HN Show, when your app runs on $10/month container and db on $3.5 one
- vngzs 6y agoIt took me an embarrassing amount of time to realize this wasn't an official MongoDB product. But that's a compliment! The landing page is great. Really interested in behind-the-firewall options. Nobody should punch a hole in their network exposing their DB to the Internet. IMO you should offer VPC peering for AWS & GCP so this can work entirely on private networks.
- rosaldo 6y agoThanks for compliment vngzs! As you and more commenters pointed out, current connection to db isn't very optimal. I added a note "Allow remote connection to MongoDB port (27017) from 165.22.32.162" while I try to come up with a better solution. If you can share some advice/article on how VPC peering for AWS & GCP works, I'll be grateful.