cloudforet-io/monitoring

Monitoring Service

monitoring's Issues

the notification_policy option of ProjectConfig must be applied when alerts are created manually

Change authorization scope of monitoring escalation policy

• PROJECT -> DOMAIN_OR_PROJECT

Add Account field to alert service

Account is an important element in managing alerts.
We decided to add it as a structured field to Alert.

Refactor Monitoring Webhook REST Interface

Fix notification policy bug

Low Urgency alarm occurs even when Notification Policy is set to High Urgency.

Refactor alert number field

1. Change Type
   integer -> string

2. Change uniquely by domain

Prevent negative numbers from being reflected in escalate_minutes and repeat_count

Example of EscalationPolicy.update

{
    "escalation_policy_id": "ep-1234567890", 
    "name": "qa-test", 
    "rules": [
        {"notification_level": "LV1", "escalate_minutes": 15},
        {"notification_level": "LV2", "escalate_minutes": -15}, 
        {"notification_level": "LV3"}, 
        {"notification_level": "LV4"}, 
        {"notification_level": "LV5"}
    ], 
    "repeat_count": -2, 
    "finish_condition": "RESOLVED", 
    "domain_id": "domain-1234567890"
}

Apply user validation when using methods of add_responder or remove_responder

Upgrade to metadata for multiple data sources of Metric and Log

Added a value called supported_providers to metadata to display monitoring and logs using multiple data sources for one cloud service resource.

For example,

...
plugin_info:
  metadata:
    supported_providers:
    - aws
    - all

In the meantime, the secret_data passed to the DataSource used the secret_id obtained from the cloud service's collection_info, but now, if there is a secret_id in the metadata of the DataSource, it takes precedence.