While creating an environment, you state the cloudlet limits for each node. In such a way, the resources are limited and the spends are regulated. When the traffic grows an application requests more resources for normal work. And, if the limits created by you are too low, this can lead to failure in app performance.
To monitor your application’s load and the amount of resources it requires, you can configure a set of automatic notification triggers. They are executed if the usage of a particular resource type is above/below the stated value (%) during the appropriate time period. As a result, you’ll get an email notification about your application’s load change.
In order to configure an alert, follow the next instruction:
1. Click the Settings button for the desired environment:
2. In the opened tab, navigate to the Monitoring > Load Alerts section:
Here, if such is stated within your hosting service provider’s settings, you can find a bunch of default triggers, which are automatically added during environment creation. These ones, if exist, are to notify you when the RAM, CPU, disk, inodes or network traffic usage at any node is coming close to current resource limits (according to the predefined by hoster levels of consumption for notification).
3. Using the buttons in the tool panel, you can either Add a new alert or Edit, Remove, Enable/Disable the already existing ones (including the default triggers set). Also, alerts list can be Refreshed using the corresponding button.Let’s consider a case of setting up your own trigger – for that, click on the Add button, circled in the image above.
4. In the opened Add alert frame, define the following values:
After you’ve stated all the preferable configurations, click Add button.
5. As soon as alert is configured and activated, it will appear within list with the name you’ve specified in the previous step.
6. As a result, every time the resource usage comes above/below the stated percentage (depending on the condition stated) during the specified time period, the system will send you an email notification with the current level of consumption, some recommendations on this issue and direct link for the node’s scaling limit adjustment:
Note: that if an environment is shared with other users, they will also receive the same preconfigured load notifications via their emails.
In this way, you can set up a number of different triggers for any existing node in your environment.
You can view the history of triggers’ executions for the nodes of a particular environment within its settings.
1. Navigate to the Monitoring > Events History section. The Load Alerts notification Type will be chosen automatically (whilst the second option in the appropriate list is devoted to auto horizontal scaling history).
2. Using the Period drop-down list, define the time interval you’d like to view the alerts for. The available values are: day, week, month and custom (where the last one allows to specify the required dates manually).
3. As a result, you’ll see the list of alerts, that were activated during the stated period. It includes information on:
4. Click on a particular load alert to see its Details to the right. This pane contains some additional information:
In such a way, you can configure a set of alerts and to be sure that CirrusGrid will inform you about your application load changes.
In case you have any questions left on configuring alert notifications or just need more detailed information on this functionality, feel free to appeal for our technical experts' assistance at Stackoverflow.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.