Page Comparison

...

• bridgeserver2-prod-AWSCWRequestErrorAlarm - Errors in the Bridge logs. Common errors include:

  • https://sagebionetworks.jira.com/browse/BRIDGE-3321 - Broken Pipehttps://sagebionetworks.jira.com/browse/BRIDGE-3330 - Struts Error

  • https://sagebionetworks.jira.com/browse/BRIDGE-3194 - MissingServletRequestParameterException for startTime, type, and includeDeleted

  • https://sagebionetworks.jira.com/browse/BRIDGE-2492 - Illegal % escape characters in URL throws exception

  • Jira Legacy
    server System JIRA serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key BRIDGE-3331

    - Adherence report duplicate key exception

  • Jira Legacy
    server System JIRA serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key BRIDGE-3369

    - NO_SCHEDULE enum constant error

• bridgeworker-prod-AWSCWRequestErrorAlarm - Similar to above, but for the Worker.

• bridgeserver2-prod-AWSCW4XXAlarm-B675MRYR0N2M - HTTP 4XX’s from Bridge Server (excludes 401s, which happen all the time). This is

• bridgeserver2-antivirus-prod-VirusScannerLambdaErrorAlarm - Errors in our antivirus scanner. We don’t currently have a good grasp on which errors are important to look at. See Jira LegacyserverSystem JIRAserverIdba6fb084-9827-3160-8067-8ac7470f78b2keyBRIDGE-3392For more documentation on (known) antivirus errors, see Virus Scanning of Files

• Jenkins build became unstable / is still unstable - Our integration tests failed. See http://build-system.sagebase.org:8081/ This could either mean a bug was found in our code or our dev or staging environments are unhealthy. It is important to keep our integ test pipeline reliable, so that we can reliably catch bugs before they go to production. Common failures include:

• Jira Legacy
  server System JIRA serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key DHP-856

Jira LegacyserverSystem JIRAserverIdba6fb084-9827-3160-8067-8ac7470f78b2keyDHP-857

Sumo Logic Dashboards

See https://www.sumologic.com/

...