GET Website Configuration Guide on the Elven Platform

With the Website GET feature of the Elven Platform, you can monitor your services in a simple and efficient way using the GET method of the HTTP protocol. This functionality is ideal for tracking public endpoints, web pages, or any resource that responds to read requests.

The goal is to simplify: you can easily configure automatic checks, receive real-time alerts, and even set rules for incident creation whenever something is not working as expected. All of this ensures you’re quickly informed when something is offline or responding unexpectedly.

And there’s more: no need to install agents in your infrastructure. Website GET uses the external agent network of the Elven Platform, which performs monitoring from the outside—just like your users would access the service in the real world.

In other words, no need to configure environments, clouds, or install agents. Just create your check and start monitoring in a fast, lightweight, and flexible way.

Now, let’s understand a bit more about the HTTP GET method. It is widely used to request data from a server, such as web pages, files, or API responses. Unlike POST, GET does not send data in the request body. It simply retrieves information based on the accessed URL.

Because it’s a lightweight and straightforward method, GET is ideal for simple and quick checks, such as verifying if a page is available, if a service is online, or if an API responds as expected.

In monitoring, it stands out for enabling immediate responses at low cost, making it perfect for maintaining constant visibility into the health of your services.

Accessing the Website via GET

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

• Under Internet Services, select the Website GET item.

Resource Monitoring

Monitoring the availability of your services has never been easier. Start by giving a clear Resource Name to the item you want to track, making it easier to identify. Then, adjust the Interval between checks and the Timeout for responses.

Select the Checkpoint Cloud where the monitoring agent is located (e.g., AWS), and choose the specific Checkpoint region (e.g., N. Virginia) to ensure maximum accuracy. This setup uses the default agent from the Elven Platform, eliminating the need to create a new environment. 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 collected data accurately reflects the status of the monitored resource, providing valuable insights and proactive support for your operations.

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

Additionally, the Maintenance Window is an essential feature for managing planned maintenance periods in your application. During this time, monitoring checks are temporarily paused, preventing alerts and notifications from being triggered while you perform adjustments or updates. This allows maintenance to proceed smoothly, without generating unnecessary notifications or false alarms, ensuring your operations continue 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 by making backend adjustments, such as installing new security certificates. To do this, you can configure the 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 the 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 will not be affected during maintenance. This approach ensures 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 way, monitoring becomes 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 the 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 operational 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 automatic incident creation if issues are detected, notifying the responsible team.

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