How can you tell if your Atom is running if you can't get to the Boomi Platform?

Document created by mike_aronson Employee on May 19, 2016Last modified by Adam Arrowsmith on Aug 2, 2016
Version 2Show Document
  • View in full screen mode

The Dell Boomi Platform is a very reliable and accessible platform. There are occasions when down time may occur and although we are doing everything to prevent downtime, planned maintenance or unexpected outages may occur. Dell Boomi is always looking at ways to minimize downtime and ensure the platform is up and running to meet our SLAs for our customers.


The Dell Boomi atoms, especially those installed and hosted locally are subject to the availability of the environment on which it is hosted. If there is an occasion where the platform is down, or perhaps your local network or situation is preventing you from accessing the platform, here are some things you can do if you need to check if your atom is running or is down outside of the Boomi Platform:


  1. Log onto the atom server and check the atom service (or daemon if Linux) to see if it is up and running or down. Take a quick look at the atom/execution/ folder to see when the last execution was logged at the latest time expected per schedules, inbound requests, etc.
  2. Check your application endpoints and validate if data is reaching the endpoints.  In some cases, this is very helpful or easy to do if you have access to the endpoints and if the behavior of your process integrations and data are easy to track.
  3. Implement a simple heartbeat process or set of heartbeat processes that run on a frequent schedule and send a message to an email account, or you can even add a send email step within your processes to verify that it ran. You can check the email account to see if messages have shown up to determine if the processes are still running. This often works, as it is unlikely that the Dell Boomi platform, your atom, and the email server are ever all unavailable at the same time. Email server can go down too or can be slow, so it would be wise to pick a very reliable email account and also set the sync settings to a frequent setting. (note some out there are notably slow to sync). You may wish to set up a specific email account for this (just don't lose the password ) or use your regular reliable email account and setup an inbox filter to route these messages to a designated folder with an archive or purge settings after a few days.


There is likely more that you can do to find out the status of your atom and processes outside of the platform. For additional runtime monitoring strategies, see Operational Monitoring Best Practices for Atom, Molecule, and Atom Cloud Runtimes.


What other strategies have you implemented?