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

I found an audio circuit and I built it just fine, but I find it a bit too quiet. How do I amplify the output so that it is a bit louder?

A Trivial Diagnosis

What is the highest possible scrabble score for placing a single tile

Can I say "fingers" when referring to toes?

Non-trope happy ending?

How much theory knowledge is actually used while playing?

Is this toilet slogan correct usage of the English language?

Delete multiple columns using awk or sed

Microchip documentation does not label CAN buss pins on micro controller pinout diagram

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Creating two special characters

C++ copy constructor called at return

Mimic lecturing on blackboard, facing audience

Does the reader need to like the PoV character?

How do you make your own symbol when Detexify fails?

Giving feedback to someone without sounding prejudiced

What are some good ways to treat frozen vegetables such that they behave like fresh vegetables when stir frying them?

Why is it that I can sometimes guess the next note?

Why is the Sun approximated as a black body at ~ 5800 K?

How to draw a matrix with arrows in limited space

What does Apple's new App Store requirement mean

Stack Interview Code methods made from class Node and Smart Pointers

A variation to the phrase "hanging over my shoulders"

Why can't the Brexit deadlock in the UK parliament be solved with a plurality vote?



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













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

    311413




    311413












    • 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

            Can't initialize raids on a new ASUS Prime B360M-A motherboard2019 Community Moderator ElectionSimilar to RAID config yet more like mirroring solution?Can't get motherboard serial numberWhy does the BIOS entry point start with a WBINVD instruction?UEFI performance Asus Maximus V Extreme

            Identity Server 4 is not redirecting to Angular app after login2019 Community Moderator ElectionIdentity Server 4 and dockerIdentityserver implicit flow unauthorized_clientIdentityServer Hybrid Flow - Access Token is null after user successful loginIdentity Server to MVC client : Page Redirect After loginLogin with Steam OpenId(oidc-client-js)Identity Server 4+.NET Core 2.0 + IdentityIdentityServer4 post-login redirect not working in Edge browserCall to IdentityServer4 generates System.NullReferenceException: Object reference not set to an instance of an objectIdentityServer4 without HTTPS not workingHow to get Authorization code from identity server without login form

            2005 Ahvaz unrest Contents Background Causes Casualties Aftermath See also References Navigation menue"At Least 10 Are Killed by Bombs in Iran""Iran"Archived"Arab-Iranians in Iran to make April 15 'Day of Fury'"State of Mind, State of Order: Reactions to Ethnic Unrest in the Islamic Republic of Iran.10.1111/j.1754-9469.2008.00028.x"Iran hangs Arab separatists"Iran Overview from ArchivedConstitution of the Islamic Republic of Iran"Tehran puzzled by forged 'riots' letter""Iran and its minorities: Down in the second class""Iran: Handling Of Ahvaz Unrest Could End With Televised Confessions""Bombings Rock Iran Ahead of Election""Five die in Iran ethnic clashes""Iran: Need for restraint as anniversary of unrest in Khuzestan approaches"Archived"Iranian Sunni protesters killed in clashes with security forces"Archived