Navigation

    Best APM Solution for Oracle WebLogic Server & FMW Product Family
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Download

    SOLVED Timeout service - alert configuration

    General Support & Troubleshooting
    2
    4
    25
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wlcommunityusers
      wlcommunityusers last edited by

      Please help by indicating if there is any alert to be able to monitor if a service responds with timeout.

      Community Users Case Notes (Diary)

      1 Reply Last reply Reply Quote 0
      • D
        Deniz Bedel - WLSDM Team last edited by deniz.bedel-wlsdmteam

        Greetings,
        I will tell you how to get a mail notification when a service returns a time out error. The settings I describe here will work for all services running on your domain.

        • The following settings are valid if the service’s timeout logs can be monitored via diagnostic log.
        • If the service throw “Caused by: java.net.ConnectException: Connection timed out” in the diagnostic log file, these settings can be used.
        • To investigate the issue in depth, I would kindly ask you to tell us what kind of service you are using and send us the log file with the errors returned by this service.

        By following the steps below, you will create a Log Inspector Notifications rule. When this rule is defined, e-mail notification will be sent automatically.


        Instructions

        Create Log Inspector Rule

        1. Expand the Configuration category.
        2. Click on the Monitoring & Diagnostics tool.
        3. Click on the top right button (the button marked 2 in Figure 1).
        4. In the pop-up window specify the name of your Log inspector. We recommend that the name chosen here is chosen carefully so that it is easy to understand later.
        5. Select Diagnostic Log*[1]* as Log Type and click Next.
        6. Type “Caused by: java.net.ConnectException: Connection timed out” in the Search String box. (Double quotes should be deleted.)
        7. Turn off the Case Sensitive option.
        8. Under Row/Line Fetch Method, select “Current line”.
        9. Turn on Attach Line(s). Type 15 in the before and after boxes. (This value will print the first 15 and last 15 lines when the searched word is found in Search String). Click the Next button.
        10. Click on Managed servers. You will see that it moves to the right side. Click Next.
        11. Set Tail Line Count as 1000. (This is the recommended value. It can be changed later).
        12. Set Result Match Count to 1. (This is the recommended value. It can be changed later.) If this value is set to 1, notification will be provided for each match.
        13. Turn on Enable Current Monitoring Configuration. Click on the Save button.

        You will automatically receive email notifications from all the settings you make here. If you want to check manually, you can use the Log Inspector Notifications tool (Figure 6).
        (Representative screenshots of the steps are below.)

        [1] Enable you to access diagnostic data about specific feature components in Oracle Fusion Middleware.

        Representative Screenshots


        98545db5-2d47-4c8a-8ae4-c33b23fb5e87-image.png Figure 1

        65a20fe2-ead1-47af-8f67-34247b950a32-image.png Figure 2

        0b534544-8049-4c0c-be03-600cddab08f0-image.png Figure 3

        5ffadaea-7e73-44cd-8b72-fc10867df641-image.png Figure 4

        379ea278-fa66-461f-8deb-cacd68eaadae-image.png Figure 5

        ae9657f2-bf10-4067-ae49-6ffa9e0e9a58-image.png Figure 6


        Best regards.

        1 Reply Last reply Reply Quote 0
        • D
          Deniz Bedel - WLSDM Team last edited by deniz.bedel-wlsdmteam

          Greetings,
          I will tell you how to get a mail notification when a service returns a time out error. The settings I describe here will work for all services running on your domain.

          • The following settings are valid if the service’s timeout logs can be monitored via diagnostic log.
          • If the service throw “Caused by: java.net.ConnectException: Connection timed out” in the diagnostic log file, these settings can be used.
          • To investigate the issue in depth, I would kindly ask you to tell us what kind of service you are using and send us the log file with the errors returned by this service.

          By following the steps below, you will create a Log Inspector Notifications rule. When this rule is defined, e-mail notification will be sent automatically.


          Instructions

          Create Log Inspector Rule

          1. Expand the Configuration category.
          2. Click on the Monitoring & Diagnostics tool.
          3. Click on the top right button (the button marked 2 in Figure 1).
          4. In the pop-up window specify the name of your Log inspector. We recommend that the name chosen here is chosen carefully so that it is easy to understand later.
          5. Select Diagnostic Log*[1]* as Log Type and click Next.
          6. Type “Caused by: java.net.ConnectException: Connection timed out” in the Search String box. (Double quotes should be deleted.)
          7. Turn off the Case Sensitive option.
          8. Under Row/Line Fetch Method, select “Current line”.
          9. Turn on Attach Line(s). Type 15 in the before and after boxes. (This value will print the first 15 and last 15 lines when the searched word is found in Search String). Click the Next button.
          10. Click on Managed servers. You will see that it moves to the right side. Click Next.
          11. Set Tail Line Count as 1000. (This is the recommended value. It can be changed later).
          12. Set Result Match Count to 1. (This is the recommended value. It can be changed later.) If this value is set to 1, notification will be provided for each match.
          13. Turn on Enable Current Monitoring Configuration. Click on the Save button.

          You will automatically receive email notifications from all the settings you make here. If you want to check manually, you can use the Log Inspector Notifications tool (Figure 6).
          (Representative screenshots of the steps are below.)

          [1] Enable you to access diagnostic data about specific feature components in Oracle Fusion Middleware.

          Representative Screenshots


          98545db5-2d47-4c8a-8ae4-c33b23fb5e87-image.png Figure 1

          65a20fe2-ead1-47af-8f67-34247b950a32-image.png Figure 2

          0b534544-8049-4c0c-be03-600cddab08f0-image.png Figure 3

          5ffadaea-7e73-44cd-8b72-fc10867df641-image.png Figure 4

          379ea278-fa66-461f-8deb-cacd68eaadae-image.png Figure 5

          ae9657f2-bf10-4067-ae49-6ffa9e0e9a58-image.png Figure 6


          Best regards.

          1 Reply Last reply Reply Quote 0
          • wlcommunityusers
            wlcommunityusers last edited by

            Thanks for your help.

            Community Users Case Notes (Diary)

            1 Reply Last reply Reply Quote 0
            • D
              Deniz Bedel - WLSDM Team last edited by

              We are very glad that you have resolved the issue and it was a great pleasure to support you.

              Best regards

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              WLSDM: Native WebLogic Monitoring & Diagnostics

              Copyright © 2021 WLSDM Community & Support Portal | WLSDM.COM | WLSDM Blog