Deploying DMP Producer

This section provides detailed instructions on how to deploy HCL CDP DMP Producer using Devtron on AWS.

Before you begin

Make sure the following prerequisites are in place:

  • Create a secret named cdp-producer in the AWS Secrets Manager.

  • Ensure the secret contains valid data for database connections, Kafka configurations, and SMTP settings.
  • Confirm Devtron is set up and has access to the required OCI registry.

Procedure

  1. Configure Registry Access:
    • Navigate to Global Configurations > Container/OCI Registry.
    • Select the required repository, such as hcl-ecr.
    • In the List of repositories, check whether the /dmp-producer is included and save the repository configuration.
  2. Sync Helm Charts:
    • Navigate to the Chart Store.

    • Select Source and locate the hcl-ecr source.
    • Click the Refresh icon to fetch the latest images and charts.
  3. Select and Initialize Deployment:
    • In the search bar, search for dmp-producer and select the chart.
    • Select Configure & Deploy.

    • Enter the App Name as dmp-producer and select the appropriate Project and Environment (e.g., cdp-dev-app).
  4. Update Configuration:
    In the YAML section, update the ConfigMap data with the required environment variables.
    BucketType: minio
ConfigRefreshInterval: "10"
CronExpr: 0 */5 * * * ?
DMPProducerBatchSize: "1000"
DMPProducerEventType: "100"
DbDriver: org.mariadb.jdbc.Driver
EncryptionEnabled: "true"
EventBatchSize: "1000"
EventQueueLength: "100000"
EventThreadPoolMax: "96"
EventThreadPoolMin: "96"
EventThreadTTL: "5"
GraphEnabledCampaignIds: dummy
HostNameOverride: generic-hostname-override
IS_SMTP: "true"
KMS_HASHICORPVAULT_ENDPOINT: ""
KMS_HASHICORPVAULT_ENDPOINT_TOKEN: ""
KMS_IMPLEMENTATION: HashiCorpVault
KafkaExecutorServiceMaxThreads: "32"
KafkaExecutorServiceMinThreads: "32"
KafkaExecutorServiceQueuseSize: "1"
KafkaExecutorServiceThreadTTL: "5"
KafkaProducerEventType: "1111"
KafkaProducerGraphNbaTopicName: generic_nba_graph_topic
KafkaProducerHostName: generic-kafka-host
KafkaProducerHostname: generic-producer-hostname
KafkaProducerMeta: "true"
KafkaProducerNbaTopicName: generic_nba_topic
KafkaProducerPoolSize: "10"
KafkaProducerTaxonomyTopicName: generic_taxonomy_topic
LOG_LEVEL_APP: info
LOG_LEVEL_ROOT: info
MaxEventBatchLag: "16"
MaxS3DownloadRetries: "3"
MaxWaitForConnectionReestablish: "5"
MetricPrefix: generic-app-prefix
MinioAccessKey: ""
MinioEndPointUrl: ""
MinioSecret: ""
NbaFileBatchSleepInMs: "1000"
RawNBAConfigS3Location: "/path/to/s3/config"
RawNbaConfigDownloadDir: /data/config/download
RawNbaDownloadDir: /data/nba/download
SMTPhost: ""
SMTPpassword: YOUR_ENCRYPTED_PASSWORD
SMTPport: "20225"
SMTPusername: generic_smtp_user
SchedulerIntervalInMin: "2"
SegmentNameMacro: SegmentNameMacro
TSDBHostName: generic-tsdb-host
TSDBServerAddress: ""
TSDBServerPort: "443"
TaxonomyDownloadDir: /data/taxonomy/download
alertToEmailId: alert-recipient@example.com
allowedRegions: region-1
aps1_host: ""
aps1_namespace: generic-namespace
aps1_port: "13000"
defaultSegmentNotifyEmail: alerts@example.com
emailType: SMTP
expiry: "-1"
failureSubject: Ingestion Failed
fromEmailId: no-reply@example.com
funnelSegmentNameMacro: |
  "{ segmentname }": null
funnelWaitTime: "60000"
hashicorpvault.endpoint: ""
hashicorpvault.endpoint.token: ""
host: ""
kms.implementation: HashiCorpVault
namespace: generic-namespace
pii_expiry: "-1"
pii_host: ""
pii_namespace: pii-namespace
pii_port: "13000"
pii_region: region-1
port: "13000"
queue_names: TEST
Queue_provider: sqs
region: region-1
segmentIdMacro: segmentIdentifier
sqs_threads: "12"
sqs_url_prefix: ""
successSubject: Ingestion Completed
supported_regions: region-1
timeout: "3000"
uploadSuccessEmailIds: no-reply@example.com
userListFailedHTML: /path/to/UserListFailed.html
userListInternalErrorHTML: /path/to/UserListInternalError.html
userUploadErrorFunnelHTML: /path/to/Failed.html
userUploadFailureFunnelHTML: /path/to/Failed.html
userUploadSuccessFunnelHTML: /path/to/success.html
userUploadSuccessHTML: /path/to/UserUploadSuccess.html

  5. Search the Chart Values for account ID and replace it with the target account ID.
  6. Click Deploy, and navigate to App Details to verify the pod is in running status.