-
Bug
-
Resolution: Fixed
-
Medium
-
4.20.0
-
None
-
15
-
Severity 3 - Minor
-
17
-
Issue Summary
Currently - missing objects are flagged per import configuration.
So, if the same object type is being updated by two different Import configuration - both with "Missing Objects" set to update a Status Attribute, with any threshold. After the threshold is reached on either import - the Status Attribute across all objects will fluctuate, depending on which Import was running last.
Steps to Reproduce
- Configure 2 Import configurations (A, B) both updating the same Object Type for example: Importing from 2 Azure Subscriptions into the same Structure, with the Predefined mapping
- Let each import run on schedule to accede the Threshold
- Missing Objects Update on some object types is set to Update the Status Attribute to "Not found", Assume threshold is 2 syncs - for the explanation below
- Notice Object A (included in Import A) and Object B (included in Import B) both belong to the same object type X
Expected Results
Requested:
If an objects in the same object type is updated by any import, the Missing Object's Counter is reset:
Following the Imports along a timeline:
Import A is running creating Object A
Import B is running creating Object B, flagging Object A as a Missing Object
Import A is running - Identifying Object A, Resetting Object A Flag, flagging Object B as a Missing Object
Import B is running - identifying Object B, Resetting Object B Flag, flagging Object A as a Missing Object
and so on - the end result: Status is not updated, unless an object is missing in BOTH the Imports for the given threshold
Actual Results
Following the Imports along a timeline:
Import A is running creating Object A
Import B is running creating Object B, flagging Object A as a Missing Object
Import A is running - Identifying Object A, flagging Object B as a Missing Object
Import B is running - identifying Object B, updating Status of Object A to "Not Found"(Threshold was reached)
Import A is running - identifying Object A, Updating Status of Object A to "Running", updating Status of Object B to "Not Found" (Threshold was reached)
Import B is running - identifying Object B, Updating Status of Object B to "Running", updating Status of Object A to "Not Found" (Threshold was reached)
and so on.
...
Workaround
Either create a Root Object Type per subscription, so that each Import configuration will actually update its own Object Types,(Pros - Missing Objects will act as expected, Cons - hard to maintain, troubleshoot and requires more administration)
or;
Set Missing Objects to Ignore and configure an Automation rule to run on Schedule, and update Status to not found, if the object was not updated for a set period (Updated < now(-2d) - assuming that each Import will actually update the Objects (Pros - disregard the Missing Objects causing the Status to fluctuate. Cons - requires and Object update as a condition, and may add to performance when running)
- causes
-
JSDSERVER-15258 Running Asset Imports can lead to OutOfMemoryException (OOME) as every object's history is added to the cache
-
- Closed
-
-
JSDSERVER-8676 improve import configuration options when the Azure integration is used with multiple subscriptions
- Gathering Interest
- is related to
-
JSDSERVER-8706 Create a cleanup mechanism to Assets Object History
- Gathering Interest
- was cloned as
-
JSDCLOUD-11981 Insight Missing Objects across all import configurations
- Closed
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
Hi everyone,
Thank you for your feedback, we’re excited to let you know that we’re starting work on this bug on Assets import configuration.
This improvement will ensure that objects are only flagged as missing from an import when the object was created or updated via the import being executed. This will help avoid clashes between multiple import configurations for the same object type.
An example scenario would be:
When an import from system A runs, it should never mark users which were imported or updated from system B or C as being missing. It should also not mark the manually created users as being missing.
The current behaviour does not consider where the object came from when marking them as missed.
Please continue to follow this ticket for further updates as we progress this improvement.
Kind regards,
Craig Shannon
Jira Service Management Data Center