FMX Solutions
New in JSM — Section 5 of 893 / 120 min

New in JSM · 25 min

Don't Just Rebuild Opsgenie

JSM introduces capabilities that can simplify the operating model and reduce unnecessary alert noise. Read these five in order — they tell one story.

  1. Reduce Noise
  2. Normalize Alerts
  3. Automate Response
  4. Connect Operational & Jira Work
  5. Control Planned Noise

Multiple related alerts can be grouped so responders can understand an operational event rather than processing every alert independently.

  • Reduce alert fatigue
  • Identify related signals
  • Handle related alerts together
  • Associate multiple alerts with an incident
  • Improve situational awareness
Think About It
“If 50 alerts represent one outage, do responders need 50 separate operational conversations?”

Alert policies allow incoming alerts to be automatically handled based on defined conditions — before routing, escalation or automation get involved.

  • Adjust priority
  • Assign responders
  • Add tags
  • Suppress known noise
  • Standardise incoming alerts
  • Modify alert behaviour
Best Practice
Use policies to normalise and simplify alert handling before adding unnecessary downstream automation.

Automation can remove repetitive operational decisions.

  1. Critical alert
  2. Initiate incident workflow
  1. Specific integration / condition
  2. Assign team
  1. Major incident declared
  2. Add responders
  3. Initiate communications
Watch Out
Automation should simplify the operating model, not hide an overly complex one. Avoid dozens of overlapping rules when better routing or service ownership would solve the problem more cleanly.

Reusable distinction

Integrations bring events INTO Operations. Syncs connect Operations alerts WITH Jira work items.

Integration — inbound

  1. External System
  2. Integration
  3. JSM Alert

Sync — bidirectional

JSM AlertSyncJira Work Item
  • Bidirectional synchronisation
  • Alert / Jira work item relationship
  • Status synchronisation
  • Information synchronisation
  • Replacing certain legacy integration patterns
Admin Tip
Syncs are especially important for administrators familiar with older Opsgenie-to-Jira integration models — that relationship is now a first-class capability rather than a configured integration.

Planned maintenance should not generate unnecessary operational noise.

  • Planned maintenance windows
  • Suppression
  • Temporarily disabling operational mechanisms where appropriate
  • Avoiding false incident generation during known changes
Best Practice
Plan the maintenance window at the same time as the change — not after the alerts start arriving.
Section message

Migration is the moment to let these capabilities change the design — not the moment to reproduce legacy configuration in a new place.

PreviousOpsgenie → JSMNext · 12 minReporting