You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After deploying the stack using this repo it is observed that the detailed monitoring is disabled for main node. Since its the main node of jenkins which manages everything and is a single point failure, it makes sense to have detailed monitoring enabled.
We do not have any means to enable it using 1.127.0 version of cdk.
Looks like the issue was resolved aws/aws-cdk#19346 in version 1.151.0.
We might need to upgrade the cdk version to enable this feature.
Describe the bug
After deploying the stack using this repo it is observed that the detailed monitoring is disabled for main node. Since its the main node of jenkins which manages everything and is a single point failure, it makes sense to have detailed monitoring enabled.
We do not have any means to enable it using 1.127.0 version of cdk.
Looks like the issue was resolved aws/aws-cdk#19346 in version 1.151.0.
We might need to upgrade the cdk version to enable this feature.
This is not an issue for agent nodes as those are deployed via jenkins ec2 cloud plugin where we have enabled monitoring by default https://github.com/opensearch-project/opensearch-ci/blob/main/lib/compute/agent-node-config.ts#L96
To reproduce
Deploy the stack and see that the MainNode monitoring is disabled
Acceptance Criteria
Detail monitoring enabled for main node as well
Expected behavior
Monitoring should be enabled for main node
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: