What is included in the PagerDuty Integration service during configuration?
The PagerDuty Integration service allows you to create and manage incidents in PagerDuty based on events in Nutanix X-Play. To configure the PagerDuty Integration service, you need to provide the following information:
Service Name: The name of the PagerDuty service that you want to integrate with X-Play.
API Key: The API key generated from the PagerDuty service settings.
Plays: The plays that you want to trigger incidents in PagerDuty. You can select one or more plays from the list of available plays in X-Play. You can also specify the incident priority, escalation policy, and alert details for each play.
Alert Grouping: (Optional) The alert grouping strategy that you want to use for the PagerDuty incidents. You can choose from the following options:
Intelligent: PagerDuty will group alerts based on their content and context.
Time: PagerDuty will group alerts based on the time they are received.
An administrator has noticed an increasing number of inactive VMS being left powered on within the environment over the course of OS migrations, using Playbooks, which two Actions should the administrator use to start documenting which VMS are marked as inactive to take future Automated actions on? (Choose two.)
The administrator should assign the VMs to an Inactive:VM category as an action and trigger a playbook on alert with the Inactive VM alert policy. By doing this, they can create a custom category to group and identify the inactive VMs and use a custom alert policy to trigger a playbook that can perform automated actions on them, such as powering them off, deleting them, or sending notifications. This is based on the general practices in managing VMs in a multicloud environment, as well as the specific features and requirements of Nutanix X-Play and Nutanix Calm.Reference:
How to create custom categories | Prism central | Nutanix Community
When a developer launches the created Blueprint within the Blueprint Editor, the application gets deployed correctly. However, when the Blueprint is launched via Marketplace, it gets a check login error.
What is causing this issue?
