Azure Java Web App with Application Insights showing 404 every 5 minutesApplication Insights not showing data in Azure Preview PortalApplication Insights No data since deployed to Azure web appAzure Resource Template Dependencies / Application InsightsApplication Insights support multiple environment for JavaJPetShop and Azure Application InsightAzure 'Web App on Linux' app service Application loggingInstalling Application Insights as an Azure App Service Extension or via NuGet?Azure Application Insights for custom Java methodsUnable to link Spring boot application with Azure Application insight using application.properties, when logback.xml is usedHow to enable application insights for Azure Web App virtual directories

AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?

Is the Joker left-handed?

Could gravitational lensing be used to protect a spaceship from a laser?

Combinations of multiple lists

Took a trip to a parallel universe, need help deciphering

How can I fix/modify my tub/shower combo so the water comes out of the showerhead?

Why can't we play rap on piano?

Can I ask the recruiters in my resume to put the reason why I am rejected?

What exploit are these user agents trying to use?

Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?

I'm flying to France today and my passport expires in less than 2 months

Did Shadowfax go to Valinor?

Why is the 'in' operator throwing an error with a string literal instead of logging false?

Where does SFDX store details about scratch orgs?

Why does Arabsat 6A need a Falcon Heavy to launch

When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?

How to take photos in burst mode, without vibration?

Arrow those variables!

Why is consensus so controversial in Britain?

Does a druid starting with a bow start with no arrows?

Is "remove commented out code" correct English?

Alternative to sending password over mail?

Would Slavery Reparations be considered Bills of Attainder and hence Illegal?

Why is Collection not simply treated as Collection<?>



Azure Java Web App with Application Insights showing 404 every 5 minutes


Application Insights not showing data in Azure Preview PortalApplication Insights No data since deployed to Azure web appAzure Resource Template Dependencies / Application InsightsApplication Insights support multiple environment for JavaJPetShop and Azure Application InsightAzure 'Web App on Linux' app service Application loggingInstalling Application Insights as an Azure App Service Extension or via NuGet?Azure Application Insights for custom Java methodsUnable to link Spring boot application with Azure Application insight using application.properties, when logback.xml is usedHow to enable application insights for Azure Web App virtual directories






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I have a Java Web App running in Azure Web App with Application Insights enabled and the javaagent configured in Application Settings.



In the insights, I see a 404 request to the web server (GET /) every 5 minutes, for which I do not have a handler (intentionally). The insights show no other dependencies involved and there is no Apache/Azure logs for the IP address of the culprit, but it seems it would be coming from the web app itself?



Is there a health check that is created automatically and how does one configure/disable it but keep the other insights like dependencies?



Java 8



Tomcat 8.5 (latest)



Spring Boot application



EDIT: I do not have the Spring Boot Actuator configured, for what its worth










share|improve this question






















  • Probably due to the always on setting of the web app.

    – Peter Bons
    Mar 8 at 5:14

















0















I have a Java Web App running in Azure Web App with Application Insights enabled and the javaagent configured in Application Settings.



In the insights, I see a 404 request to the web server (GET /) every 5 minutes, for which I do not have a handler (intentionally). The insights show no other dependencies involved and there is no Apache/Azure logs for the IP address of the culprit, but it seems it would be coming from the web app itself?



Is there a health check that is created automatically and how does one configure/disable it but keep the other insights like dependencies?



Java 8



Tomcat 8.5 (latest)



Spring Boot application



EDIT: I do not have the Spring Boot Actuator configured, for what its worth










share|improve this question






















  • Probably due to the always on setting of the web app.

    – Peter Bons
    Mar 8 at 5:14













0












0








0








I have a Java Web App running in Azure Web App with Application Insights enabled and the javaagent configured in Application Settings.



In the insights, I see a 404 request to the web server (GET /) every 5 minutes, for which I do not have a handler (intentionally). The insights show no other dependencies involved and there is no Apache/Azure logs for the IP address of the culprit, but it seems it would be coming from the web app itself?



Is there a health check that is created automatically and how does one configure/disable it but keep the other insights like dependencies?



Java 8



Tomcat 8.5 (latest)



Spring Boot application



EDIT: I do not have the Spring Boot Actuator configured, for what its worth










share|improve this question














I have a Java Web App running in Azure Web App with Application Insights enabled and the javaagent configured in Application Settings.



In the insights, I see a 404 request to the web server (GET /) every 5 minutes, for which I do not have a handler (intentionally). The insights show no other dependencies involved and there is no Apache/Azure logs for the IP address of the culprit, but it seems it would be coming from the web app itself?



Is there a health check that is created automatically and how does one configure/disable it but keep the other insights like dependencies?



Java 8



Tomcat 8.5 (latest)



Spring Boot application



EDIT: I do not have the Spring Boot Actuator configured, for what its worth







azure-application-insights azure-web-app-service






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 8 at 0:02









jrobkcjrobkc

178




178












  • Probably due to the always on setting of the web app.

    – Peter Bons
    Mar 8 at 5:14

















  • Probably due to the always on setting of the web app.

    – Peter Bons
    Mar 8 at 5:14
















Probably due to the always on setting of the web app.

– Peter Bons
Mar 8 at 5:14





Probably due to the always on setting of the web app.

– Peter Bons
Mar 8 at 5:14












2 Answers
2






active

oldest

votes


















0














Could be because you set Always On feature. If you don't have any webjob you can turn it off.



At least you can you can verify that by temporarily turning off Always On and verifying that those requests stop.



Also, as you know, you can see list of health checks in application insight.






share|improve this answer























  • Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

    – jrobkc
    Mar 11 at 13:31











  • Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

    – Kamran
    Mar 11 at 14:04






  • 1





    After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

    – jrobkc
    Mar 12 at 23:16



















0














As an alternative, when Always On is off, the auto deploy still works as long as something is hitting the app service. One option for this is to use Availability tests from Application Insights to hit the url. I created a custom controller in my web app to handle those requests.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55054767%2fazure-java-web-app-with-application-insights-showing-404-every-5-minutes%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Could be because you set Always On feature. If you don't have any webjob you can turn it off.



    At least you can you can verify that by temporarily turning off Always On and verifying that those requests stop.



    Also, as you know, you can see list of health checks in application insight.






    share|improve this answer























    • Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

      – jrobkc
      Mar 11 at 13:31











    • Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

      – Kamran
      Mar 11 at 14:04






    • 1





      After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

      – jrobkc
      Mar 12 at 23:16
















    0














    Could be because you set Always On feature. If you don't have any webjob you can turn it off.



    At least you can you can verify that by temporarily turning off Always On and verifying that those requests stop.



    Also, as you know, you can see list of health checks in application insight.






    share|improve this answer























    • Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

      – jrobkc
      Mar 11 at 13:31











    • Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

      – Kamran
      Mar 11 at 14:04






    • 1





      After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

      – jrobkc
      Mar 12 at 23:16














    0












    0








    0







    Could be because you set Always On feature. If you don't have any webjob you can turn it off.



    At least you can you can verify that by temporarily turning off Always On and verifying that those requests stop.



    Also, as you know, you can see list of health checks in application insight.






    share|improve this answer













    Could be because you set Always On feature. If you don't have any webjob you can turn it off.



    At least you can you can verify that by temporarily turning off Always On and verifying that those requests stop.



    Also, as you know, you can see list of health checks in application insight.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Mar 10 at 14:31









    KamranKamran

    321413




    321413












    • Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

      – jrobkc
      Mar 11 at 13:31











    • Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

      – Kamran
      Mar 11 at 14:04






    • 1





      After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

      – jrobkc
      Mar 12 at 23:16


















    • Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

      – jrobkc
      Mar 11 at 13:31











    • Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

      – Kamran
      Mar 11 at 14:04






    • 1





      After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

      – jrobkc
      Mar 12 at 23:16

















    Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

    – jrobkc
    Mar 11 at 13:31





    Thanks, it does seem like this is the culprit. I'm still struggling to understand the scope of exactly what is "always on". Does this mean the tomcat container and related wars will be unavailable if idle for a period?

    – jrobkc
    Mar 11 at 13:31













    Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

    – Kamran
    Mar 11 at 14:04





    Azure unloads your site if it is idle for the standard 20 minute timeout, which can cause slow responses for the initial site users after it is unloaded. Enabling Always On essentially causes Azure to ensure that it remains in a running state.

    – Kamran
    Mar 11 at 14:04




    1




    1





    After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

    – jrobkc
    Mar 12 at 23:16






    After some more reading and testing, without Always On, the java process running tomcat will shut down. The next request must wait for tomcat to start, wars to deploy and then process the request. For future readers, this will create headaches when deploying to a staging slot that has shut down. As an aside, you are supposed to be able to set the application setting WEBSITE_SWAP_WARMUP_PING_PATH which you can point to a custom Controller, but I cannot seem to get this to work with Tomcat...

    – jrobkc
    Mar 12 at 23:16














    0














    As an alternative, when Always On is off, the auto deploy still works as long as something is hitting the app service. One option for this is to use Availability tests from Application Insights to hit the url. I created a custom controller in my web app to handle those requests.






    share|improve this answer



























      0














      As an alternative, when Always On is off, the auto deploy still works as long as something is hitting the app service. One option for this is to use Availability tests from Application Insights to hit the url. I created a custom controller in my web app to handle those requests.






      share|improve this answer

























        0












        0








        0







        As an alternative, when Always On is off, the auto deploy still works as long as something is hitting the app service. One option for this is to use Availability tests from Application Insights to hit the url. I created a custom controller in my web app to handle those requests.






        share|improve this answer













        As an alternative, when Always On is off, the auto deploy still works as long as something is hitting the app service. One option for this is to use Availability tests from Application Insights to hit the url. I created a custom controller in my web app to handle those requests.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 13 at 22:05









        jrobkcjrobkc

        178




        178



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55054767%2fazure-java-web-app-with-application-insights-showing-404-every-5-minutes%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            1928 у кіно

            Захаров Федір Захарович

            Ель Греко