Track your R cron jobs

Instantly connect LogSnag to your R project to track your cron jobs and other important events - LogSnag makes event tracking easy.

When setting up cron jobs in R, it is usually crucial to keep track of their execution and whether they have been executed successfully or not. Sometimes, a minor failure in a cronjob can cause your R application to stop working correctly. LogSnag makes it easy to track your cron jobs and their execution status all in real-time, and it works seamlessly with your R code.

Setting up your account

Setting up LogSnag with R is very simple!

  1. Create a free LogSnag account.
  2. Create a new project on your dashboard.
  3. Copy your API token from the settings page.

R code snippets

Once your LogSnag account is set up, you can use the following code snippets to track your cron jobs. Just replace the YOUR_API_TOKEN with your LogSnag API token and update your project name.

Using R with httr

headers = c(
  'Content-Type' = 'application/json',
  'Authorization' = 'Bearer YOUR_API_TOKEN'

body = '{
  "project": "my-saas",
  "channel": "cronjobs",
  "event": "Cronjob Started",
  "description": "job: email-notifications",
  "icon": "⏰",
  "notify": true

res <- VERB("POST", url = "", body = body, add_headers(headers))

cat(content(res, 'text'))
Using R with RCurl
headers = c(
  "Content-Type" = "application/json",
  "Authorization" = "Bearer YOUR_API_TOKEN"
params = "{
  \"project\": \"my-saas\",
  \"channel\": \"cronjobs\",
  \"event\": \"Cronjob Started\",
  \"description\": \"job: email-notifications\",
  \"icon\": \"⏰\",
  \"notify\": true
res <- postForm("", .opts=list(postfields = params, httpheader = headers, followlocation = TRUE), style = "httppost")

R integration details

LogSnag is an easy-to-use event tracking tool that allows you to track any event within your R application. One of the most common use cases for LogSnag is tracking cron jobs as they are being executed. With LogSnag, you can receive real-time push notifications on your desktop and mobile devices whenever a new cronjob is executed. In addition, you can create simple charts and filter through your data to help you better understand how your R application is performing.

Other use-cases for LogSnag

  1. Track payment events via R

  2. Track user signup events via R

  3. Track waitlist signup events via R

  4. Track user sign in events in R

  5. Get a notification when your R code is done executing

  6. Monitor when a user exceeds the usage limit for your R service

  7. Monitor when a new feature is used in your R application

  8. Monitor suspicious activity in your R application

  9. Monitor when a user is being rate limited in your R application

  10. Monitor when database goes down in your R application

  11. Monitor your CPU usage in your R application

  12. Monitor memory usage in your R application

  13. Monitor high disk usage in your R application

  14. Track when a file is uploaded to your R application

  15. Track when a form is submitted to your R application

  16. Track canceled subscriptions in your R application

  17. Monitor failed payments for your R application

  18. Monitor your CI/CD build status for your R application

  19. Monitor when a user changes their email address in your R application

  20. Monitor Redis downtime in your R application

  21. Monitor your Postgres downtime in your R application

  22. Monitor MySQL downtime in your R application

  23. Monitor failed logins in your R application

    View all common use-cases with R