Monitor your Postgres downtime in your Ruby application

LogSnag makes it easy to track your Ruby application and monitor when Postgres goes down.

Postgres is a robust, relational database commonly used in Ruby applications to persist and query data. It is a great tool with many features, making it an excellent choice for small and large applications.

However, just like any other database, Postgres is susceptible to downtime caused by various reasons. For example, your database instance might go down due to hardware failure, network issues, misconfiguration, or several other reasons. When this happens, chances are that your application will not be able to continue working as expected, causing significant issues such as failing requests and slow performance. In severe cases, it can cause data loss.

Therefore, it is crucial to monitor the status of your database and take immediate action when something is not functioning as expected. Fortunately, LogSnag makes it trivial to track such events as database downtimes and failures. LogSnag is a simple and powerful event tracking tool that allows us to log whenever we encounter an unexpected behavior in our applications.

For example, in the case of Postgres, we usually set up periodic checks to ensure that our database is up and running and monitor its performance, disk, and memory usage. If we encounter any issues, such as increased disk usage, slow performance, or downtime, we log the event using LogSnag. It then notifies our team immediately and allows us to take immediate action.

In addition, LogSnag provides a powerful insights dashboard that allows us to monitor the status of our database, its performance, uptime, memory usage, and any other metric that we want to track, making it easy to monitor the health of our database.


Setting up LogSnag

  1. Sign up for a free LogSnag account.
  2. Create your first project from the dashboard.
  3. Head to settings and copy your API token.

Ruby code snippets

To track your Postgres downtime, you can use the following code snippet Please don't forget to replace the YOUR_API_TOKEN with your API token and update the project and channel names.

Using Ruby with Net::HTTP
require "uri"
require "json"
require "net/http"

url = URI("https://api.logsnag.com/v1/log")

https = Net::HTTP.new(url.host, url.port)
https.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Content-Type"] = "application/json"
request["Authorization"] = "Bearer YOUR_API_TOKEN"
request.body = JSON.dump({
  "project": "my-saas",
  "channel": "status",
  "event": "Postgres is down",
  "description": "Postgres has been down for the last 5 minutes",
  "icon": "🚨",
  "notify": true
})

response = https.request(request)
puts response.read_body

Ruby integration details

In addition, LogSnag provides several powerful features, such as real-time event tracking, push notifications, charts, funnels, and user journey tracking. Furthermore, it works seamlessly with Ruby and is an excellent tool for monitoring each application part.

LogSnag provides a generous free plan to get you started with event tracking. You can also check out our pricing page to see our paid plans. So please give us a try and let us know what you think!

Other use-cases for LogSnag

  1. Track payment events via Ruby

  2. Track user signup events via Ruby

  3. Track your Ruby cron jobs

  4. Track waitlist signup events via Ruby

  5. Track user sign in events in Ruby

  6. Get a notification when your Ruby code is done executing

  7. Monitor when a user exceeds the usage limit for your Ruby service

  8. Monitor when a new feature is used in your Ruby application

  9. Monitor suspicious activity in your Ruby application

  10. Monitor when a user is being rate limited in your Ruby application

  11. Monitor when database goes down in your Ruby application

  12. Monitor your CPU usage in your Ruby application

  13. Monitor memory usage in your Ruby application

  14. Monitor high disk usage in your Ruby application

  15. Track when a file is uploaded to your Ruby application

  16. Track when a form is submitted to your Ruby application

  17. Track canceled subscriptions in your Ruby application

  18. Monitor failed payments for your Ruby application

  19. Monitor your CI/CD build status for your Ruby application

  20. Monitor when a user changes their email address in your Ruby application

  21. Monitor Redis downtime in your Ruby application

  22. Monitor MySQL downtime in your Ruby application

  23. Monitor failed logins in your Ruby application

    View all common use-cases with Ruby