New-Farm-OPS-Requirments_688988220

The purpose of this page is to describe the requirements in order to operate a new SMAX SaaS farm.

Monitoring:

APM:
- A dedicated tenant with sample data deployed.
  - Disable SLT from the monitoring tenant
  - Applications to be created: SLA, Major functionalities, internal SLA. The SLA application name should include the farm id from CT.
  - Add the SLA application to SMAX SLA, Add the internal SLA application to SMAX internal SLA. Verify that the KPIs were populated properly.
SiteScope:
- Connect bastion server to the domain
  - In case of a new region, ask PSDC to give the team members access and permissions in the SiteScope
  - Copy and modified scripts from existing farms to the new bastion server and update the environment variable accordingly.
  - Create an IAM user with sufficient permissions and use its keys for the AWS monitors.
  - Open Rabbitmq ports so the SiteScope can reach them
  - Make sure that the SiteScope can communicate with the bastion server.
  - Deploy monitors from the templates
Prometheus - enable Prometheus and Grafana

Schedule idol compact to run periodically (daily\weekly)
Setup AWS backup jobs to backup RDS and EFS every 6 hours and keep the backups for one week
The bastion server should be deployed from an AMI. If this farm is deployed in a new region or account, work with PSDC to copy the AMI accordingly.

Add the farm to CT.
Add a new environment to the PCS prod tenant.
Add a service health page to the farm. Make sure you can add incident reports and maintenance windows via the operational console
Verify that the APM data is populated.
In case of a new AWS account - set SAML authentication to all OPS people - ticket to PSDC.
Add password to passwords file in S3.
Create individual users with bo admin permissions to all ops members.
DWG reports - make sure the reports covers the new farm