New Mapping Entities

%3CLINGO-SUB%20id%3D%22lingo-sub-1217986%22%20slang%3D%22en-US%22%3ENew%20Mapping%20Entities%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1217986%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20a%20road%20map%20for%20when%20new%20map%20entities%20will%20be%20added%20to%20alerts%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20few%20playbooks%20set%20up%20for%20New%20Accounts%20created%2C%20and%20currently%20we're%20just%20using%20the%20Hosts%20entity%20as%20a%20placeholder%20for%20the%20%22InitiatedBy%22%20entity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20playbooks%20generate%20tickets%20for%20our%20company%2C%20however%20we've%20been%20having%20some%20issues%20with%20the%20Initiated%20not%20being%20associated%20with%20the%20correct%20TargetResource.%20I've%20tried%20a%20few%20workarounds%20and%20I%20get%20one%20of%20the%20following%3A%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EOne%20InitiatedBy%20is%20associated%20with%20all%20TargetResources%2C%20when%20in%20reality%20there's%20multiple%20Initiators.%3C%2FLI%3E%3CLI%3EEach%20InitiatedBy%20is%20associated%20with%20every%20TargetResource%2C%20which%20creates%20numerous%20duplicate%20tickets%20with%20incorrect%20information.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI've%20also%20tried%20the%20new%20Alert%20Aggregation%20tool%20to%20group%20by%20the%20%22Host%22%20placeholder%20mapped%20entity%2C%20but%20results%20in%20the%20same%20issue%20as%20above.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1224571%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Mapping%20Entities%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1224571%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F418279%22%20target%3D%22_blank%22%3E%40leoszalkowski%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi.%3C%2FP%3E%0A%3CP%3EWe%20are%20working%20very%20hard%20on%20this.%26nbsp%3B%20We%20should%20have%20something%20in%20the%20new%20few%20months.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Is there a road map for when new map entities will be added to alerts?

 

We have a few playbooks set up for New Accounts created, and currently we're just using the Hosts entity as a placeholder for the "InitiatedBy" entity.

 

These playbooks generate tickets for our company, however we've been having some issues with the Initiated not being associated with the correct TargetResource. I've tried a few workarounds and I get one of the following: 

  • One InitiatedBy is associated with all TargetResources, when in reality there's multiple Initiators.
  • Each InitiatedBy is associated with every TargetResource, which creates numerous duplicate tickets with incorrect information.

I've also tried the new Alert Aggregation tool to group by the "Host" placeholder mapped entity, but results in the same issue as above.

1 Reply
Highlighted

@leoszalkowski 

Hi.

We are working very hard on this.  We should have something in the new few months.