Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-29207

Datadog socket closed errors appearing in logs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 9.10, 10.10
    • Fix Version/s: None
    • Component/s: Datadog
    • Environment:
      Nuxeo Cloud Preprod & Prod

      Description

      Seeing a new error in nuxeo server logs from the past month+ relating to datadog metric reporting:

      I/O exception (java.net.SocketException) caught when processing request to {s}->https://app.datadoghq.com:443: Socket is closed
      

      This is not something we have seen historically, and it only made its way into operational awareness in the last week when the rate increased on Nationwide preprod and prod while working through MSK implementation troubleshooting.  We are seeing this sporadically in Server Logs going back the last month in Datadog logs. It is showing up in all preprod and prod environments across Nuxeo 9.10 & 10.10 .

      We do NOT know an origination date because our log history only goes back 1 month.  The rate has been gradually increasing over the past month as seen in the attached timeline image.

      Attaching Dev level env links to Datadog for investigation. It has only been showing up in the past 3 weeks for NXIO envs with more involved use of streams, but hosting has been showing it in all Nuxeo versions. NXIO log events: https://app.datadoghq.com/logs?cols=core_host%2Ccore_service&context_event=AQAAAXJS7t26l2WdFgAAAABBWEpTN3QzQWFCUW1zcUFsaUlBQQ&from_ts=1588622673525&index=main&live=true&messageDisplay=inline&query=filename%3Aserver-json.log+%22java.net.SocketException%22&stream_sort=desc&to_ts=1591214673525

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: