• 6
    • 21
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We occasionally are having issues with the insight import that causes the import to no longer work (i.e. Corrupt file, empty file). 

      It would be interesting to have some sort of notification when there are errors with the import (i.e Email notification, automation rule)

            [JSDSERVER-11031] Create a way to send notifications when an Insight import fails

            ca46b9fffad1 - thought about your comment and here is a solution:
            Map your DB Results Import to an Object Type "Heartbeat", where result's timestamp (e.g. Import's START_TIME) is mapped to the Name / Label).

            The Heartbeat object will only have its four default Attributes, and the Import will recycle these with Missing Objects Remove, after 1 sync - so new objects will be created whenever the Monitoring Import runs successfully (including its own last run), and older objects will be deleted.

            Configure an Automation rule:
            WHEN: Scheduled event - every n min / hours / days etc (adjustable, depending on the checkup resolution you wish to have, and other params like imports frequency etc.).

            IF: objectType = Heartbeat AND Created < now(-n <d/h/m>) //again, depending on the checkup resolution you wish to have...

            THEN: possible Actions: Email - send Monitoring Email
                                     Create Jira Ticket - if needed
                                     HTTP Request: you can create an Object or trigger any other system...
                                     Attribute Value - set a Status or any Attribute in a corresponding object - if needed...

             

            So - if the Monitoring Import did not run, no Heartbeat object will be created / deleted... If there are heartbeat objects which were Created before the set threshold (in the Automation rule) - this means that the Monitoring Import did not run within the set period, and an action will be triggered...

            Yinon Negev added a comment - ca46b9fffad1 - thought about your comment and here is a solution: Map your DB Results Import to an Object Type "Heartbeat", where result's timestamp (e.g. Import's START_TIME) is mapped to the Name / Label). The Heartbeat object will only have its four default Attributes, and the Import will recycle these with Missing Objects Remove, after 1 sync - so new objects will be created whenever the Monitoring Import runs successfully (including its own last run), and older objects will be deleted. Configure an Automation rule: WHEN: Scheduled event - every n min / hours / days etc (adjustable, depending on the checkup resolution you wish to have, and other params like imports frequency etc.). IF: objectType = Heartbeat AND Created < now(-n <d/h/m>) //again, depending on the checkup resolution you wish to have... THEN: possible Actions: Email - send Monitoring Email                          Create Jira Ticket - if needed                          HTTP Request: you can create an Object or trigger any other system...                          Attribute Value - set a Status or any Attribute in a corresponding object - if needed...   So - if the Monitoring Import did not run, no Heartbeat object will be created / deleted... If there are heartbeat objects which were Created before the set threshold (in the Automation rule) - this means that the Monitoring Import did not run within the set period, and an action will be triggered...

            Nice solution, using Insight to solve Insight!  But if the database import fails, then you have a real conundrum.  

            David Sumlin added a comment - Nice solution, using Insight to solve Insight!  But if the database import fails, then you have a real conundrum.  

            Here is an outline for a solution:
            The Import Process results are all saved into the AO_8542F1_IFJ_PRG_RES database table.

            You may create an Object Type to contain process results, and configure an Insight Database Import, importing from this table to Insight periodically. (RESULT column = 0 when Result is OK, also indicated in the JSON within the "RESULT_DATA" column)

            Configure an Automation rule to trigger on Results Object created, and Result is not OK - Trigger an Action (e.g. send an Email, fire an HTTP request, update a Status and/or Create a Jira Ticket...)

            Yinon Negev added a comment - Here is an outline for a solution: The Import Process results are all saved into the AO_8542F1_IFJ_PRG_RES database table. You may create an Object Type to contain process results, and configure an Insight Database Import, importing from this table to Insight periodically. (RESULT column = 0 when Result is OK, also indicated in the JSON within the "RESULT_DATA" column) Configure an Automation rule to trigger on Results Object created, and Result is not OK - Trigger an Action (e.g. send an Email, fire an HTTP request, update a Status and/or Create a Jira Ticket...)

              Unassigned Unassigned
              7d74d3b1a350 Rodrigo Jose Zaparoli
              Votes:
              19 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: