Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View SiteMonitor on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

Monitors web site up/down status.

Download & Installation

You can download the latest .hpi and install it from the Manage Plugins menu, or install this plugin directly from the Plugins Update Center.


  1. After installing the plugin, go to job configuration page, select 'Add post-build action', and select 'Monitor Site'.
  2. Tick the checkbox, add the URL(s) that you want to monitor, add a comma-separated list of response http status (optional) and a timeout (optional), and save the configuration. If you do not specify a list of http responses or a timeout, the monitor operation will get the default values from global configuration.
  3. Run a build. After it's completed, a link to Site Monitor Report page should appear on the build page. The report page would contain web site status and response code.
  4. It is also possible to configure success response codes and timeout settings in the global configuration page (Manage Jenkins -> Configure System)


Change Log

Version 0.5 (April 30, 2019)
Version 0.5 (Dec 14, 2015)
Version 0.4 (Nov 1, 2011)
  • https support - accepts any cert
Version 0.2 (Feb 14, 2011)
  • Translation updates (Chinese, Japanese)
Version 0.1 (Apr 7, 2010)
  • Initial release


  1. Unknown User (david.conil@gmail.com)


    This plugin is very useful to check if a server is available before triggering any further action. However, it is cumbersome to browse through the jobs (and maintain the information many times) to find out on the build page whether the site is up or not. Is there a plan to make the site monitor overview available on the job page and/or the main hudson page, e.g. as portlet in the Dashboard View?

    Best regards,


    1. Unknown User (cliffano)

      Hi David,

      (Sorry for late reply, I haven't been monitoring this wiki page).

      The idea is that the build should fail when there's a site down. That way you don't have to go through the jobs to check if the sites are up or not, you can use one of Hudson job result notifier plugins to be alerted when a job fails.

      If the job fails, then check one of the sites.
      If the job passes, everything is up, you don't have to do anything.


      1. Unknown User (coolplanet)

        Hello Cliffano,

        i noticed when the job show status 200 but the site is showing proxy error. It cannot detect the page is down. Overall the plugin is very nice. If it can handle user name and password handling that will be perfect.

        Will you consider to continue developing this plugin?

  2. Unknown User (nvi)


    A question about this plugin.

    I tried to use it to test web applications using SPNEGO technology (authentification protocol - an auth. pop-up is displayed when logging in the URL of the application) but it failed.

    I tried with both Firefox (that doesn't support SPNEGO authentification for the moment) and Internet Explorer (it works manually), the results are the sames.

    Do you have an idea why it doesn't work? Or will it work in next release with application using SPNEGO authentification?

    Best regards,


  3. Unknown User (jacobsonz@gmail.com)


    Is there any reason this plugin would not work with https urls? I'm getting this error and I'm not sure if it's my network or the plugin: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target - sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    URL: https: //my url, response code: null, status: EXCEPTION

    Is this a bug?

    Thanks -

    1. Unknown User (salman__awan@hotmail.com)

      Facing this same error when monitoring secure site with https:// prefix. It will be a great to have functionality as most of the corporate websites are on secure channel.

      Business scenario is, at the end of a job that stops, auto deploys build artifacts on server and then starts it, having this basic validation will be first smoke test, before triggering automated smoke test jobs.

      An issue is already logged in Jira here. Anyone wanting this functionality, vote for it.

      1. Unknown User (evernat)

        There is another issue which includes a patch for https here

        1. Unknown User (cliffano)

          Zak, Salman, evernat,

          Please try v0.4, it should handle https with any cert - [http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/sitemonitor/0.4/sitemonitor-0.4.hpi


  4. Unknown User (leolimajr)

    It is an excelent plugin. Thanks for sharing.

    I was wondering if it is possible to allow the use of enviroment variables to define the site URL. Something like:


    I don't know about you, but in my company we use the URL as hudson job name for some automatic scripts due continuos integration process.


    1. Unknown User (ikuoikuo)

      I second this suggestion. I would use it for creating a parametrized SiteMonitor job.

    2. Unknown User (salmira)

      I also need an option to use parameters value (like $SERVER_ADDRESS or https://$SERVER) for parametrized jobs in our continuous integration process...

      Created issue https://issues.jenkins-ci.org/browse/JENKINS-13071

    3. Unknown User (ebrahim_moshaya)

      Any update on this? This would be a great addition!! We need to be able to pass in environment variables

    4. Unknown User (andrusha19)


      I created pull request for this issue. It was accepted and merged into master. But I don't know, when it will appear in update center.

      If you really need this option now, you can download sitemonitor.jpi from my git and replace your sitemonitor.jpi in jenkins/plugins folder. Then you should restart your Jenkins.


      But I left correctness of input parameters on implementor!

  5. Unknown User (xenoky)


    i would like this plugin manages also an uptime percentage like:
    totale success / total try
    over the last N builds (where N is configurable)

  6. Unknown User (fabioribeiro)

    It will be great if plugin could verify pages protected by authentication.

    1. Unknown User (salmira)

      As I found, Site Monitor plugin already works for secured sites like https://server
      (plugin version 0.4, Jenkins ver. 1.454).

  7. Unknown User (xenoky)

    i realized a shell script to calculate the uptime with the info from the logs generated by the SiteMonitor Plugins,
    if someone is interested here is a link with the script.

  8. Unknown User (jimsearle)

    I use this to check that my slaves are alive using http://slaveHostName:3141 which works great.  It would be nice to have an option in this plugin to enable checking all slaves instead of having to manually enter all the urls.

  9. Unknown User (mdp)

    Too bad there is no way to configure the run order of Site Monitor and Deploy plugins except by moving the monitor to a separate job.

    1. Unknown User (cliffano)

      Yea, I've been wanting this feature too, would be great to arrange the order of post build actions.

      Something like this needs to be done in core Jenkins I think.

  10. Unknown User (salmira)

    Plugin results (Site Monitor Report) are shown on the build page only. Its results are not shown in the main project(job) page...

    Is it possible to have an option to publish Site Monitor Report with the last job results?

    Using plugin version 0.4, Jenkins ver. 1.454.

    PS Just found related issue https://issues.jenkins-ci.org/browse/JENKINS-12306

  11. Unknown User (salmira)

    It would be nice to have an option to run Site Monitor as a build step, not only as a post-build action.

    Added an issue: https://issues.jenkins-ci.org/browse/JENKINS-13072

  12. Unknown User (qatest)

    pls add option description in site monitor reporting. sometimes for better accuracy we use ip url in site monitor, however in reporting its only show as below :

    URL                          Response Code          Status      http://xxx.xxx.xxx.xx                          

    pls add description as show below in site monitor config so we can add some description about the ip url (see website description column)

    URL                            website description    Response Code          Status      http://xxx.xxx.xxx.xx                    

  13. Unknown User (qatest)

    im not sure if it a bug, in jenkins build history i can see listing of build history (from 1-9), however clicking the trend link, it shows my current build history number is #2608.

    pls assist, isn't the latest build reflected in build history as well?

  14. Unknown User (pavan_e)


    I have downloaded / installed the "sitemonitor" plugin and installed it on my Jenkins. I do not see the "checkbox with the text 'Monitor Site' as mentioned in the "usage" section on this page. Would someone please let me know on what I am doing wrong? :(

    I have Windows 2008 R2 64 bit with sitemonitor 0.4 version plugin on Jenkins v1.547

  15. Unknown User (jtojan)


    I am using Jenkins 1.610 and installed on WIndows 7. I installed sitemonitor plugin, but the checkbox to add the URL is not appearing. Can someone help on this?

  16. Unknown User (gary4620)

    Ditto to the last two comments. I don't see the checkbox anywhere. Is it only available for certain types of projects?

    1. Unknown User (gary4620)

      I found at least two logged issues for this problem:


      JENKINS-40982 - Getting issue details... STATUS

      JENKINS-28066 - Getting issue details... STATUS


      I didn't see any indication of when they might get resolved.

  17. Unknown User (danieldestro)

    I ran my job to test an invalid URL which returned 404. And the job failed as expected.

    Then I changed to a valid URL and test was successful and job passed as expected.

    When I shutdown the web server and then I run the job again it shows as a valid test, even though the server is down.

    How come that can happen? Is it caching anything?