Cynteo Alert Bridge Documentation

Connect Azure Monitor alerts to SolarWinds Service Desk automatically

Configuration Options

Learn about the configuration options available during deployment of Cynteo Alert Bridge.


Required Settings

These are configured during initial deployment:

VariableTypeDescriptionExample
SOLARWINDS_API_TOKENSecretSolarWinds API tokenBearer abc123...
SOLARWINDS_BASE_URLStringSolarWinds instance URLhttps://api.samanage.com
REQUESTER_EMAILStringDefault requester emailazure@company.com

Optional Settings

These options can be configured during deployment to customize behavior:

Incident Mapping

VariableTypeDefaultDescription
INCIDENT_CATEGORYString"Infrastructure"Default category name
INCIDENT_SUBCATEGORYString"Azure Monitor"Default subcategory
ASSIGNEE_GROUPStringnullAuto-assign to team
INCIDENT_PREFIXString"Azure Alert:"Prefix for incident names

Priority Mapping

VariableTypeDefaultDescription
SEV0_PRIORITYString"Critical"Priority for Sev0
SEV1_PRIORITYString"High"Priority for Sev1
SEV2_PRIORITYString"Medium"Priority for Sev2
SEV3_PRIORITYString"Low"Priority for Sev3
SEV4_PRIORITYString"Low"Priority for Sev4

Filtering

VariableTypeDefaultDescription
SEVERITY_FILTERStringnullOnly process these severities (comma-separated)
IGNORE_RESOLVEDBooleanfalseDon’t update incidents on resolution
MIN_SEVERITYStringnullMinimum severity to process

Advanced Options

VariableTypeDefaultDescription
DEDUP_WINDOW_HOURSNumber24How long to track alerts for dedup
MAX_DESCRIPTION_LENGTHNumber32000Truncate descriptions
TIMEZONEString"UTC"Timezone for timestamps
ENABLE_DEBUG_LOGGINGBooleanfalseVerbose logging

Note: Configuration options are set during deployment. Contact your administrator or support@cynteocloud.com for configuration changes.


Configuration Examples

These examples show how different settings affect incident creation:

Example 1: Custom Priority Mapping

{
  "SEV0_PRIORITY": "Critical",
  "SEV1_PRIORITY": "High",
  "SEV2_PRIORITY": "Medium",
  "SEV3_PRIORITY": "Low",
  "SEV4_PRIORITY": "Low"
}

Example 2: Severity Filtering

Only create incidents for critical and high severity:

{
  "SEVERITY_FILTER": "Sev0,Sev1"
}

Or use minimum severity:

{
  "MIN_SEVERITY": "Sev2"
}

Example 3: Custom Categories

{
  "INCIDENT_CATEGORY": "Cloud Services",
  "INCIDENT_SUBCATEGORY": "Azure Monitoring",
  "ASSIGNEE_GROUP": "Cloud Operations Team"
}

Example 4: Multiple Environments

For different environments (dev/staging/prod), use different prefixes:

Production:

{
  "INCIDENT_PREFIX": "[PROD] Azure Alert:",
  "ASSIGNEE_GROUP": "Production Support"
}

Staging:

{
  "INCIDENT_PREFIX": "[STAGING] Azure Alert:",
  "ASSIGNEE_GROUP": "Dev Team"
}

Understanding Your Configuration

The deployment wizard collects these settings and applies them automatically. All configuration is managed by your Azure administrator.

For questions about your specific configuration or to request changes, contact support@cynteocloud.com.


See Also


Questions? Contact support@cynteocloud.com