Incidents into ServiceNow, automatically
If ServiceNow is your system of record, infrastructure alerts belong there as incidents, not as emails someone forwards. LynxTrac posts alert events to ServiceNow over webhooks so threshold breaches and grouped exceptions arrive as incidents in your existing flow.
Your ITSM process stays where it is; LynxTrac feeds it instead of competing with it.
Scope, stated plainly
Webhook-level and one-way: LynxTrac creates incidents, it does not sync their lifecycle back. Resolving the incident in ServiceNow does not clear the alert in LynxTrac. Teams needing deeper CMDB or bidirectional integration should talk to us about what is actually planned before committing.
Incident creation from alert rules
Bind specific rules to ServiceNow so genuine incidents file automatically while routine notifications stay in email or Slack.
Context that survives the handoff
Device, event, severity, and a link back to the source view ride along, so the assignee is not starting from a bare summary line.
Inbound intake stays flexible
ServiceNow-side intake (Flow Designer, inbound REST) shapes the payload into your incident schema, keeping your categorization rules in your hands.
Setting it up
Point a LynxTrac webhook target at your ServiceNow inbound endpoint and select the alert rules that should create incidents.
Payload mapping is configured in ServiceNow, which means your assignment rules, categories, and SLAs apply unchanged.
See it connected to your own workflow
The free tier covers 2 servers forever, which is enough to wire this up and judge it on your infrastructure rather than ours.