API/Python/Open-Source Solutions

Expand all | Collapse all

status of dSource

Jump to Best Answer
  • 1.  status of dSource

    Posted 02-28-2018 08:35:00 PM
    Recently we had an issue where our delphix engine hung and as a result, our dSources were a little behind in the logs with our production database. Is there a way to proactively monitor the delphix engine and dsource so we can get notified sooner rather than when we find out manually ?

  • 2.  RE: status of dSource
    Best Answer

    Posted 02-28-2018 08:56:00 PM
    Yes. You can setup a alert profile and start receiving an email about the warning/critical faults. So that you will be notified as and when log file is missing.

  • 3.  RE: status of dSource

    Posted 02-28-2018 08:58:00 PM
    Thank you. Is the alert profile setup done from the GUI ? I haven't done it before. so just checking

  • 4.  RE: status of dSource

  • 5.  RE: status of dSource

    Posted 02-28-2018 11:13:00 PM
    Thank you very much. Does this also monitor the status of the delphix engine or rather report if there is a connection failure to the engine ?

  • 6.  RE: status of dSource

    Posted 03-01-2018 05:20:00 AM
    Hi Srividya, You have several methods for monitoring the engine. Using standard SNMP SMTP for sending emails Syslog to send Delphix logs to a syslog server Custom scripts using our CLI or API, dxtoolkit Mission control (Delphix reporting) - Managing multiple Delphix Engines Regards, Mouhssine

  • 7.  RE: status of dSource

    Posted 03-01-2018 03:07:00 PM
    All good points above, but only works if the Delphix Management component is working.  What if it's down?  It cannot send alerts.

     In addition to configuring alerts and notifications, you should use a simple HTTP/HTTPS probe from your monitoring solution of choice.  They all have such a probe, and your company is almost certainly already using one to monitor other important web based software, you just need to find the right people. 

    The probe typically just hits a web page every minute and looks for a 200 response from a web server, and as long as they get one everything is judged to be OK.  It's very simple, and about 99% effective.

    The reason only 99% effective is false positives and negatives.  False Positive:  the Management component might just be slow, not down.  (Personally...I'd like to get alerted for that).  False Negative:  hypothetically the Management component might be up but the engine is still "unhealthy".  (But you should get an Alert for that!)

    Just remember, you need BOTH the HTTP/HTTPS probe AND the Delphix alert system to successfully monitor your engine health.