Get Recommendation Monitoring Result
Fetches the results of periodic continuous monitoring for a specific recommendation session to identify if the context has drifted.
Notes:
- Results are only available if
monitoring_enabledis true for the session AND system-wide monitoring is active. - Compares the original context against the latest effective members (VMs/servers) and segmentation strategies.
- If
rerun_recommendedis true, the environment has changed significantly and the user should trigger a newANALYZEaction via the PUT endpoint.
The id of the resource
The recommendation resource is present. Status may indicate further information.
{
"id": "d81c4105-3da3-4cb5-8a08-51f082c175ae",
"rerun_recommended": false,
"rerun_recommended_reasons": [],
"last_monitoring_start_time": 1779144510094,
"latest_segmentation_strategies": [],
"latest_effective_vms": [],
"latest_effective_physical_servers": []
}recommendation id
A flag that indicates whether the recommendation has to be rerun possibly because effective vm's have changed. It is recommended that the user rerun this recommendation when this flag is set.
A further explanation of why the rerun_recommended was set to true. EFFECTIVE_MEMBERS_CHANGED means that new members may have been added/removed from the original context members for whom the recommendation was generated for. Or infrastructure classification of members of the original context got changed. PERMISSIVE_MODE_CHANGED alert can be set when the security policy's application connectivity preference value was changed from what it was configured with during start of recommendation session. SEGMENTATION_STRATEGIES_CHANGED alert can be set when the security policy's application connectivity preference value was changed from what it was configured with during start of recommendation session. POLICY_APPLIED_TO_SCOPE_CHANGED alert can be set when the security policy's applied to scope was changed from what it was configured with during start of recommendation session. NONE means that no reason could be given for why the rerun_recommended to be set or there may have been multiple reasons. NON_CONTEXT_EFFECTIVE_MEMBERS_CHANGED Non context effective members refers to the computes that are communicating with the context boundary provided as input. If any of the non-context workloads changed their Infrastructure classification or got deleted after analysis was run then this rerun alert reason will be set.
Timestamp in milliseconds since epoch.
If periodic monitoring is enabled for this recommendation and also system-wide, this value denotes the latest segmentation strategies/application connectivity preference set on the specified security policy at the time of the last periodic monitoring run. If this value is different than at the time the recommendation was run, then rerun will be recommended. This field will be the same as segmentation_strategies when security_policy is not provided as input to the recommendation session.
If periodic monitoring is enabled for this recommendation and also system-wide, this value denotes the latest effective vms at the time of the last periodic monitoring run. This is a function of user provided context_groups and context_vms at the time of the last monitoring run for this recommendation. The group latest membership is used to recalculate this value. Any deleted vms will be removed when this value is set. Comparing this value with context_effective_vms can identify the vms that have been added or removed since the last time recommendation was generated. Assuming no further boundary changes happened after the last monitoring run, this is the boundary that would be used as an input to generate recommendation if it were rerun again now via the /rerun API.
[Deprecated] If periodic monitoring is enabled for this recommendation and also system-wide, this value denotes the latest effective physical servers at the time of the last periodic monitoring run. This is a function of user provided context_groups and context_physical_servers at the time of the last monitoring run for this recommendation. The group latest membership is used to recalculate this value. Any deleted physical servers will be removed when this value is set. Comparing this value with context_effective_physical_servers can identify the vms that have been added or removed since the last time recommendation was generated. Assuming no further physical server boundary changes happened after the last monitoring run, this is the physical server boundary that would be used as an input to generate recommendation if it were rerun again now via the /rerun API.
Bad Request
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Unauthorized
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Forbidden
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Failed
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Required
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Too Many Requests
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Error
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
curl -H 'Authorization: <value>' https://{api_host}/intelligence/recommendations/{id}/monitoring-result