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) 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)
Please let me know if you're interested or have any feedback.
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.
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.
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?
I added public IP to the page where you connect MongoDB, you can try again.
However our MongoDB environment is very secluded inside a VPC, K8S... If makes sense in the future pls consider a Docker version with some sort of registration key.
You might want to consider adding an on-premise plan? I think most DBs are not publicly exposed on the internet?
If you run MongoDB on server (example AWS or DigitalOcean) you can easily connect to it with MongoDB connection string.
It's advised to run on separate server as MongoDB takes up a considerable amount of RAM and it's never a good idea to run your database service on the same server instance as your production services. I run mine on AWS lightsail for $3,5/month for now.
Will look into adding on-premise, if this gets any traction.
As developers can use Robo3T and write queries, the ideal customer in my mind is a smaller team/startup where developers setup metrics for marketing/product team as they need them but can't use MongoDB.
I'm not sure how to market this as developers need to do the setup, but product or marketing actually needs it.
Any advice on how to market?
good luck with callstop, the landing page looks neat.
OSS combined with cloud offerings seem to be an established approach