HTTP GET Monitor Configuration Guide on the Elven Platform

With HTTP GET monitoring from the Elven Platform, you can track the performance of services within your own infrastructure, such as private endpoints, internal systems, or applications operating in networks isolated from the public internet.

This type of monitoring is ideal for environments where external access is not allowed, whether due to security, compliance, or the network’s own structure.

To enable this, simply create a Cloud and an Environment within the Elven Platform, and install a dedicated agent in your infrastructure. This agent will be responsible for performing the checks directly from inside your network, ensuring visibility into internal services without compromising security.

Even though it is designed for restricted environments, the configuration process remains simple: you define automatic checks, adjust alerts as needed, and can even set up rules for automatic incident creation. Everything is designed to notify you before something impacts your users or operations.

Here, we use the HTTP GET method, ideal for making simple and fast requests that retrieve information from the server without modifying its state. With it, the agent checks whether the service is online, responds correctly, and meets the expected parameters—simulating exactly how real requests would behave.

In other words, with HTTP GET monitoring from inside your network, you have a lightweight, efficient, and tailored solution to ensure the stability and performance of your internal services, with all the intelligence and automation that the Elven Platform delivers.

Accessing the HTTP GET Monitor

• Navigate to the main menu and click on Services Hub.

• Under Internet Services, select the GET item.

Resource Monitoring

Monitoring the availability of your services has never been easier. Start by giving a clear name to the resource you want to track (Resource Name) to make identification easier. Then, adjust the interval between checks (Interval) and the response timeout (Timeout).

Select where the monitoring agent is located (Checkpoint Cloud) by choosing an Environment—if it doesn’t exist, you can create one using + Checkpoint. Add the Healthcheck URL, and if needed, configure advanced options such as Skip SSL Validation or enable TLS Renegotiation to meet specific security requirements.

Use the available fields to customize monitoring requests. For example, include custom headers (Header and Value); to add more than one header, use the + button. You can also define a Validation String to validate specific responses. These steps help ensure that the data collected accurately reflects the state of the monitored resource, providing valuable insights and proactive support for your operation.

Automatic Incident Opening

You can configure automatic incident opening to ensure a quick response to critical issues. To begin, define the incident severity, allowing you to prioritize according to urgency. Next, adjust the Check Interval, specifying the check frequency in seconds to continuously monitor the resource. This helps ensure you're always one step ahead, detecting problems as soon as they arise.

Additionally, select the team to be notified whenever an incident occurs and enable the "Enable to set up automatic incidents opening" option to ensure the configuration is active. With this setup, the platform automates incident management, making the response process faster and more efficient, without the need for manual intervention. This ensures your team is always ready to resolve any issue with speed and precision.

Maintenance Window

We also have Maintenance Window, an essential feature for managing planned maintenance periods in your application. During this time frame, checks are temporarily paused, preventing monitoring, alerts, and notifications from being triggered while you perform updates or adjustments. This allows maintenance to proceed smoothly, without generating unnecessary notifications or false alarms, ensuring your operation continues in an orderly manner without unexpected interruptions in performance reports.

For example, imagine you need to update the payment system of an e-commerce platform, making backend adjustments such as installing new security certificates. To do this, you can configure a Maintenance Window for a specific time, such as 12/13/2024, from 2:00 PM to 2:30 PM. During this period, the Elven Platform suspends checks, preventing the monitoring system from logging temporary failures or triggering false alerts. This way, you can make the necessary changes calmly, knowing that the monitoring system won’t be affected during maintenance. This approach ensures that the update is carried out in an organized manner, without affecting the user experience or generating unwanted notifications.

Application Opening Hours

You can also rely on the Application Opening Hours feature, which allows you to configure your application's operating hours. This functionality is essential for customizing monitoring based on the periods when your application is actually active, avoiding alerts and notifications outside of business hours. This makes monitoring more aligned with your business’s real needs, ensuring more accurate reports and efficient management.

For example, imagine your application operates only from Monday to Friday, between 9:00 AM and 6:00 PM. You can configure Application Opening Hours to reflect this schedule by specifying the working days and time periods. With this setup, the Elven Platform automatically disables checks outside of those hours, preventing the logging of failures that don’t affect end users and avoiding unnecessary alerts. This approach optimizes performance analysis, focusing only on relevant periods and providing a clearer view of your application’s health during its operating hours.

Glossary of Technical Terms

GET: HTTP protocol method used to request data from a resource on the server. GET requests are read-only and do not alter the server’s state.

Resource Name: Unique name assigned to the monitored resource to facilitate its identification on the platform.

Interval: Time interval, in seconds, between checks performed by the platform to monitor the resource.

Timeout: Time limit to wait for a response from a check before considering it a failure.

Checkpoint: Environment where the monitoring agent is configured.

Healthcheck URL: The address (URL) used to verify the availability of the monitored resource.

Skip SSL Validation: Setting that skips SSL certificate validation during resource checks, useful in testing or development environments.

TLS Renegotiation: Option that allows renegotiation of TLS security protocols if necessary for the monitored resource.

Header: Additional information sent in the HTTP request to customize or authenticate the monitoring.

Validation String: String of characters used to validate the resource’s response and ensure it matches the expected result.

Check Interval: Frequency, in seconds, at which the platform performs checks to detect issues with the resource.

Enable to set up automatic incidents opening: Setting that enables the automatic creation of incidents if problems are detected, notifying the responsible team.

Incident Severity: Priority level assigned to an incident to determine the urgency of its resolution.