Home

OMS Alerts Foreword OnPremise

%3CLINGO-SUB%20id%3D%22lingo-sub-202130%22%20slang%3D%22en-US%22%3EOMS%20Alerts%20Foreword%20OnPremise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-202130%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENeed%20your%20recommendations%20forwarding%20alerts%20from%20OMS%20to%20On-Prem%20Instance%20which%20is%20my%20alert%26nbsp%3Baggrigator%20and%20has%20integration%20with%20my%20ticketing%20tool.%3C%2FP%3E%3CP%3EBecause%20Webhook%20is%20a%20public%20service%20and%20can't%20be%20integrated%20without%20exposing%20another%20public%20facing%20end%20interface.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20there%20is%20a%20way%20by%20peering%20ER%20with%20public%20interface.%3C%2FP%3E%3CP%3ELet%20me%20know%20if%20you%20are%20aware%20of%20any%20other%20solution.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-202130%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAgents%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-202208%22%20slang%3D%22en-US%22%3ERe%3A%20OMS%20Alerts%20Foreword%20OnPremise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-202208%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EYou%20can%20trigger%20a%20runbook.%20That%20runbook%20can%20run%20on%20Hybrid%20Worker%20which%20could%20be%20on-premises%20server.%20The%20runbook%20will%20run%20on%20that%20environment%20and%20log%20the%20alert%20in%20your%20on-premises%20alert%20tool.%3C%2FP%3E%0A%3CP%3EOther%20option%3A%3C%2FP%3E%0A%3CP%3EAs%20Log%20Analytics%20alerts%20are%20logged%20as%20data%20in%20Log%20Analytics%20you%20can%20query%20that%20information%20on%20certain%20intervals%20from%20your%20on-premises%20server%20via%20PowerShell%2FC%23%20or%20other%20methods.%20The%20data%20is%20logged%20in%20Alert%20table.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20recommend%20the%20first%20approach%20as%20it%20is%20more%20flexible%20and%20you%20run%20runbooks%20only%20when%20there%20are%20alerts.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20me%20know%20if%20I%20understood%20the%20scenario%20and%20the%20proposals%20are%20what%20you%20are%20looking%20for.%3C%2FP%3E%3C%2FLINGO-BODY%3E
sac tr
Occasional Visitor

Hi All,

 

Need your recommendations forwarding alerts from OMS to On-Prem Instance which is my alert aggrigator and has integration with my ticketing tool.

Because Webhook is a public service and can't be integrated without exposing another public facing end interface. 

I know there is a way by peering ER with public interface.

Let me know if you are aware of any other solution. 

 

Thanks

1 Reply

Hi,

You can trigger a runbook. That runbook can run on Hybrid Worker which could be on-premises server. The runbook will run on that environment and log the alert in your on-premises alert tool.

Other option:

As Log Analytics alerts are logged as data in Log Analytics you can query that information on certain intervals from your on-premises server via PowerShell/C# or other methods. The data is logged in Alert table.

 

I would recommend the first approach as it is more flexible and you run runbooks only when there are alerts.

 

Let me know if I understood the scenario and the proposals are what you are looking for.

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
202 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies