PenfieldAI helm chart values file
How to choose which services to enable
When you get values file using helm show values penfieldai/penfieldai > penfield-values.yaml you will see there are various services that are there. By default only Pathfinder services are enabled. If you need help which services need to be enabled then you can follow the below table. Some of them are optional depends on your SEIM/SOAR tool integration.
Here is the quick overview each of the services in the values file that helps which and when you should enable it. You will have deployment type either Pathfinder only or Pathfinder + ITSM.
| Name | Description | Pathfinder | Pathfinder + ITSM | Feature that uses service |
|---|---|---|---|---|
| kafka | Kafka as a queuing system | Required | Required | - |
| kratos | Kratos is required for authentication purposes | Required | Required | - |
| postgres-db | Database service for storing processed data from various services | Required | Required | - |
| mongo-db | Database service for storing processed data from various services | Required | Required | - |
| milvus | Vector Database service | Required | Required | - |
| airflow | ETL pipelines | Required | Required | - |
| minio | Storage solution | Required | Required | - |
| aihandler-service | Microservice for events consumer and producer that invokes the AI backend | No | No | Alert Assignment |
| analyst-availability-service | Microservice to track and provide analyst availability | No | No | Alert Assignment |
| cloudsoar-inbound-integration | Microservice ingest incoming data from CloudSoar | No | Optional | CloudSoar inbound integration |
| data-pipeline | To process data after incident and interaction events are received in realtime or on schedules | No | Required | - |
| datastorer-service | Microservice that process integration incoming data from kafka and stores into mongo DB | No | Required | - |
| helix-inbound-integration | Microservice to ingest incoming data from Helix | No | Optional | Helix inbound integration |
| helix-outbound-integration | Microservice to process outgoing data to Helix | No | Optional | Helix outbound integration |
| incident-service | Microservice owns the incidents and process the incidents data | No | Required | - |
| ingestion-api | Hosts APIs for pushing incident data and events to Penfield | No | No | For development use only |
| interaction-service | Microservice owns the interactions | Required | Required | - |
| jira-inbound-integration | Microservice to ingest incoming data from jira | No | Optional | Jira inbound integration |
| nlp-service | Microservice for nlp service | Required | Required | Jira inbound integration |
| queue-balancing-service | Microservice to balance analyst queues | No | No | Alert Assignment |
| queuing-service | Microservice for maintaining and surfacing analyst queues | No | No | Alert Assignment |
| reinforcement-learning-service | Microservice hosts the reinforcement learning model and APIs for model training and serving | No | No | Alert Assignment |
| sentinel-inbound-integration | Microservice to ingest incoming data from Microsoft Sentinel | No | Optional | Sentinel inbound integration |
| soc-data-analytics-service | Microservice to compute and return soc level analytical metrics and data points | No | Required | - |
| web | Microservice for PenfieldAI dashboard | Required | Required | - |
| xsoar-inbound-integration | Microservice to ingest incoming data from Cortex XSOAR | No | Optional | XSOAR inbound integration |