We have set up the DataDog log integration and we are trying to stitch it together with our other logging. The plan to do this was to set a command id with a unique value and use that to match everything up. We are setting that value in our calls but when we search the logs we don’t see that value anywhere. Our understanding was the command ID would be part of the logs, is that incorrect?
CommandsSubmission test = CommandsSubmission.create(damlProperties.getApplicationId(),
policyNumber + "-" + UUID.randomUUID().toString(),
Collections.singletonList(cmd))
.withActAs(platformAdminIdentifier)
.withWorkflowId(damlProperties.getWorkflowID());
@RyanMedlen i do see command-id in the canton participant logs? could you give an example (with any sensitive data removed) where you are not seeing what is expected?
bats-canton-participant-1 | 2023-06-02 18:53:01,315 [canton-env-execution-context-25] INFO c.d.p.a.s.ApiSubmissionService - Submitting commands for interpretation, context: {participant: “participant0”, tid: “bf106487ec4f99db20cecf21267b5ea4”, commands: {readAs: , deduplicationPeriod: {duration: “PT30S”}, submittedAt: “2023-06-02T18:53:01.280284Z”, ledgerId: “ledger”, applicationId: “admin-ping”, submissionId: “65f17077-ca2d-4ee7-8c3a-58890ce00084”, actAs: [“ledger::1220bb8254fe19d1807e13859e414c6ee97a9fdee3cb106c1e71c3dd626bdde17d96”], commandId: “418472ce-35a2-485b-bdf9-4a0e271ed82f-ping-98e396d7-71b6-453e-a780-c4c625801699”, workflowId: “admin-ping”}}
I found out that the reporter was using a QA ledger where the code change is only in DEV and when I verified the issue I also used a QA ledger 
I just integrated our DEV ledger so when it shows up I will validate but I do see requests with command id(just wrong ones which makes sense since its QA). I will update this once I’m sure. Thanks for checking.