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.
When creating a Playbook using alerts, which types of actions can be executed?
An administrator needs to notify the on-call pager after hours using their PagerDuty incident management platform.
How should the administrator integrate notifications via PagerDuty in a Playbook using the least number of configurations possible?
An administrator is trying to save new settings for an Azure integration. but is having issues applying the changes.
What log should the administrator check?
The hercules.log file is the log file for the Calm service, which is responsible for managing the integration with various cloud providers, including Azure. The administrator can check this log file to troubleshoot any issues related to the Azure integration, such as authentication, configuration, or communication errors. The other log files are not relevant for the Azure integration. The sytx.log file is the log file for the Sytx service, which is responsible for managing the Calm UI and API. The durga.log file is the log file for the Durga service, which is responsible for managing the Calm Marketplace and blueprints. The arjun.log file is the log file for the Arjun service, which is responsible for managing the Calm runbooks and playbooks.
[Troubleshooting Calm | Nutanix Community]
An administrator is unable to launch a Calm blueprint (new and old). Launching an existing blueprint under this condition fails with the error message:
The project for this blueprint does not have any associated Nutanix account.
Downloading and uploading the new blueprint also fails with
Launch with Variables' Profile expected to fall as Windows Server VWs attached with deleted Account.
Please modify them to use different account and try again.
Why is the administrator seeing this issue?