Ask the Community
Groups
Tip: Creating tests to monitor the time since last results from a DGEX - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION</strong></p> <p>How to determine if the DGEX is publishing results to the upstream DGE?</p> <p><strong>RESOLUTION</strong></p> <p>After configuring a DGEX in Traverse, and after the DGE has published the first results to the upstream DGE, set up the "Time Since Result From DGE Extension (DGEX-NAME)" test on the upstream DGE.</p> <p> </p> <p><strong>Locate the upstream DGE</strong></p> <p>To do so, navigate and find the Traverse upstream DGE Server (referred to as 'Traverse Server' in this article). Click on Status --> Devices and find the server</p> <p><img src="/attachments/token/dT14g2u7BvxHJXobPdfLD3Gas/?name=traverse_server.png" alt="traverse_server.png" width="866" height="156" class="embedImage-img importedEmbed-img"></img><br><br></p> <p><strong>Determine if the test is configured on the upstream DGE</strong></p> <p>Click on the device name and determine if the test is already configured on the system. Use time in the filter: <img src="/attachments/token/axo9679ibgyCXvJyX1BhIrH7Z/?name=time_since.png" alt="time_since.png" width="867" height="211" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p> </p> <p><strong>Discover the test on the upstream DGE</strong></p> <p>In your instance, it is possible that the test does not show up for the DGEX. For this example, we will go ahead and delete the 'Time Since Result From DGE Extension (sjo-dgex)' and discover it.</p> <p>click on the pencil icon to edit the device <img src="/attachments/token/9ynECSxfoIy5xHUbn0v0REPmW/?name=edit_device.png" alt="edit_device.png" width="877" height="179" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p>Click on 'Create New Standard Tests'</p> <p>Select 'Create new tests by selecting specific monitors' and check jmx</p> <p><img src="/attachments/token/9UaxxVvFLxJuQSzAlGtgaeJvZ/?name=check_jmx.png" alt="check_jmx.png" width="868" height="283" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p>Click 'Add Test'</p> <p>In the following page, from the drop down, select the entry with jmxport 7692. If an entry does not exist, please see the next step </p> <p> <img src="/attachments/token/gsnVhrWBZFqLpwaahxjPJBqzo/?name=jmx_7692.png" alt="jmx_7692.png" width="723" height="179" class="embedImage-img importedEmbed-img"></img></p> <p>If the jmx monitor with port 7692 does not exist, create one by selecting 'Create New' . Set the port to 7692, and leave all other fields as default</p> <p>Click 'Continue'</p> <p> </p> <p><strong>Provision the Test</strong></p> <p>In the following page, the discovered tests are displayed. Provision the test(s). It is recommended that an appropriate Action Profile be set for the test<img src="/attachments/token/ywPi3ba74NYwoKQfnJmCJZuLX/?name=provision_test.png" alt="provision_test.png" width="868" height="348" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p><strong>Reviewing the test</strong></p> <p>The test will go Critical if the DGEX stops publishing results to the upstream DGEX. It is recommended that you set an action profile and be notified on this status</p> <p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse</p> <p><strong>REFERENCE </strong></p> <p>None.</p> <div> </div> </article> </main>