- Events
-
Partners
- Government
- Customer Portal
- Contact Us
- Contact Sales
-
English
Making sure web servers are working as expected—and there aren’t any serious delays—is essential to maintaining productivity and customer satisfaction.
SolarWinds® ipMonitor® comes with two monitors, the HTTP monitor and HTTPS monitor, which can constantly check your HTTP and HTTPS endpoints to help you ensure they’re working properly.
If the HTTP monitor or HTTPS monitor detects any issues, ipMonitor can send an alert notifying the proper members of your team, so they can act fast to address them.
Ensuring your web servers and webpages are performing optimally often entails more than just checking if they’re able to accept incoming sessions. SolarWinds ipMonitor comes with features designed to help you more easily ensure optimal web application and web server performance.
For example, the HTTPS monitor in ipMonitor can allow you to more easily:
One of the biggest reasons to make sure your web servers are functioning properly is to provide the best end-user experience. SolarWinds ipMonitor is designed to make maintaining and improving the end-user experience easier with its included user experience monitors, such as the HTTP User Experience monitor.
The HTTP User Experience monitor can help you confirm your web server can accept incoming sessions and transmit requested resources (like the results of a CGI script or a webpage). Like the standard HTTP monitor, it can help ensure the web server is performing as it should, such as responding within a certain number of seconds. By keeping track of your web server’s performance and alerting you when something goes wrong, the HTTP User Experience monitor can help you ensure end users get the best experience possible.
SolarWinds ipMonitor includes the Device Discovery Wizard, which searches for devices in your network and lets you control the discovery methods and range of IP addresses to scan. You can then use the wizard to create new monitors based on your detected resources.
ipMonitor also comes with SmartMonitor technology, which is designed to suggest the best monitors and data collection settings for nearly everything on your network. SmartMonitor can help you spend less time trying to figure out how to configure settings by hand and more time monitoring your devices.
An HTTP monitor is a tool used to check the availability of webpages from designated checkpoints. The goal is to get an error-free response from the web server, but if that doesn’t occur, an HTTP monitor can also collect data to help you more easily determine what might be interfering with the response.
An HTTP monitor can help you ensure webpages are functioning properly. When your webpages have slow response times, end users are more likely to become frustrated and bounce. An HTTP monitor can help you stay on top of issues by continuously monitoring your infrastructure and alerting you as soon as a potential problem arises and needs your attention. By using an HTTP monitor, you can more easily avoid having end users be the first ones to report an issue to you.
An HTTP monitoring tool performs regular, automated checks on your webpages to identify issues.
For example, with SolarWinds ipMonitor, every time a monitor test fails, the monitor counts it and checks against the pre-set number of failures allowed before an alert is generated. When a test succeeds, the sequential failure count resets to zero. When the HTTP monitor reaches its maximum number of test failures, an alert is automatically triggered, notifying you of the issue. If you have automated remediation features in place, an alert can trigger those actions.
Determining exactly when and how your HTTP monitor performs tests in SolarWinds ipMonitor depends on the settings you put in place when first adding the monitor. Once you’ve finished the basic first steps of adding an HTTP or HTTPS monitor, you have a chance to set specifications for your monitoring. These include:
SolarWinds ipMonitor is designed to make the HTTP monitoring process simpler with intuitive features to help with everything from device discovery to automated recovery.
You can install and have ipMonitor up and running typically in minutes. The tool’s Discovery Wizard and SmartMonitor can help you identify where to add monitors and which monitors you should add for each of your devices. Once you add an HTTP or HTTPS monitor, ipMonitor can continuously test the associated webpages to check for failures. You can easily set the parameters for these tests, including specifying test parameters, the timing of the tests, and how many test failures need to occur before a notification is automatically triggered. ipMonitor comes with more than 14 different built-in notification types, which means you can choose to get alerted in whichever way is most useful to you.
ipMonitor is also built to go beyond simply identifying when there are issues with your webpage. ipMonitor includes automated remediation and recovery features designed to automatically address many of the failures it detects without requiring your input.
An HTTP monitor is a tool used to check the availability of webpages from designated checkpoints. The goal is to get an error-free response from the web server, but if that doesn’t occur, an HTTP monitor can also collect data to help you more easily determine what might be interfering with the response.
An HTTP monitor can help you ensure webpages are functioning properly. When your webpages have slow response times, end users are more likely to become frustrated and bounce. An HTTP monitor can help you stay on top of issues by continuously monitoring your infrastructure and alerting you as soon as a potential problem arises and needs your attention. By using an HTTP monitor, you can more easily avoid having end users be the first ones to report an issue to you.
An HTTP monitoring tool performs regular, automated checks on your webpages to identify issues.
For example, with SolarWinds ipMonitor, every time a monitor test fails, the monitor counts it and checks against the pre-set number of failures allowed before an alert is generated. When a test succeeds, the sequential failure count resets to zero. When the HTTP monitor reaches its maximum number of test failures, an alert is automatically triggered, notifying you of the issue. If you have automated remediation features in place, an alert can trigger those actions.
Determining exactly when and how your HTTP monitor performs tests in SolarWinds ipMonitor depends on the settings you put in place when first adding the monitor. Once you’ve finished the basic first steps of adding an HTTP or HTTPS monitor, you have a chance to set specifications for your monitoring. These include:
SolarWinds ipMonitor is designed to make the HTTP monitoring process simpler with intuitive features to help with everything from device discovery to automated recovery.
You can install and have ipMonitor up and running typically in minutes. The tool’s Discovery Wizard and SmartMonitor can help you identify where to add monitors and which monitors you should add for each of your devices. Once you add an HTTP or HTTPS monitor, ipMonitor can continuously test the associated webpages to check for failures. You can easily set the parameters for these tests, including specifying test parameters, the timing of the tests, and how many test failures need to occur before a notification is automatically triggered. ipMonitor comes with more than 14 different built-in notification types, which means you can choose to get alerted in whichever way is most useful to you.
ipMonitor is also built to go beyond simply identifying when there are issues with your webpage. ipMonitor includes automated remediation and recovery features designed to automatically address many of the failures it detects without requiring your input.
ipMonitor
Verify if a web server can accept incoming sessions
Automatically discover devices
Stay on top of issues with customizable dashboards and alerts
