[Merge Tasks] Validate why we are still creating Merge Tasks

Description

CAPL - Bug default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Geny Isam Hamud Herrera
02 - PROBLEM (WHAT'S THE ISSUE?):

After deploy the Tenant User integrated with PubSub we are still having some Merge Tasks running
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):

Reduce the number of merge tasks that are running on tenants that are SQL Processing Only

Activity

Automation for Jira 18 March 2024, 16:04 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 18 March 2024, 16:03 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 18 March 2024, 16:03 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 15 March 2024, 13:40 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by rfschroeder,douglascoimbra.

Automation for Jira 15 March 2024, 13:39 Jira Internal Users

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

feat: CAPL-5383 Done - Adding datamodel label to merge tasks

Automation for Jira 11 March 2024, 16:08 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 1 March 2024, 20:01 Jira Internal Users

@Geny Isam Hamud Herrera ,
@Pedro Buzzi , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Lucas Noetzold , @Renan Schroeder

This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12, 2024-03-01, 2024-03-25

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Douglas Coimbra Lopes 20 February 2024, 17:42 Jira Internal Users

Thanks, @Gabriel DAmore Marciano @Geny Isam Hamud Herrera . This card is validated by the QA team.

Gabriel DAmore Marciano 20 February 2024, 17:05 Jira Internal Users

@Douglas Coimbra Lopes I talked with @Geny Isam Hamud Herrera and the only task that is going to have the entity template name is the EXACT_MERGE since thats the only task we have a 1:1 with number of records being merged. So, all good for this card.

Douglas Coimbra Lopes 19 February 2024, 22:07 Jira Internal Users

@Gabriel DAmore Marciano The entityTemplate name is being displayed empty for tasks REPROCESS_MERGES & MERGE_REALTIME_RECORDS_FROM_CDS

cc @Geny Isam Hamud Herrera

Douglas Coimbra Lopes 19 February 2024, 18:32 Jira Internal Users

Golden Records added to the Explore:

Reprocessing Entity Mapping CPU with staging

mdmuser SQL processing

Automation for Jira 19 February 2024, 15:19 Jira Internal Users

Apos criar nova Org, mesmo criando novos dados direto. no explore para o DM, nao sao criados as metricas
• Verificado no mdm & worker. Evidencias + detalhes no card, estou a disposicao para maiores detalhes.

Sent by Slack - platform-internal - Douglas Coimbra Lopes

Automation for Jira 19 February 2024, 14:58 Jira Internal Users

@Geny Isam Hamud Herrera ,
@Douglas Coimbra Lopes , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Lucas Noetzold , @Renan Schroeder

Flag was removed since you have just transitioned the issue status/column.

Automation for Jira 19 February 2024, 14:58 Jira Internal Users

@Geny Isam Hamud Herrera ,
@Douglas Coimbra Lopes , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Lucas Noetzold , @Renan Schroeder

Flag was removed since you have just transitioned the issue status/column.

Automation for Jira 19 February 2024, 14:57 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 February 2024, 14:57 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 February 2024, 14:57 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 19 February 2024, 12:54 Jira Internal Users

:fine2: Fiz o teste novamente no adicionando o golden record direto no Explore. Novamente nao consta nos logs o merge aplicado ao DM.
• Detalhes + evidencias no card. Estou a disposicao para maiores detalhes.

Sent by Slack - platform-internal - Douglas Coimbra Lopes

Douglas Coimbra Lopes 19 February 2024, 12:53 Jira Internal Users

@Geny Isam Hamud Herrera We’ve added 2 records that fit on the DM Merge RUle. However, the merge is not being caught on the metrics

https://newdeskubra.qarol.ai/newtnantdoug/carol-ui/explore/search/newdm/rt

credentials: douglas.coimbra@totvs.com.br/Carol3.0!

worker: http://localhost:8081/actuator/prometheus

mdm http://localhost:8081/actuator/prometheus

Geny Isam Hamud Herrera 15 February 2024, 16:21 Jira Internal Users

Automation for Jira 15 February 2024, 16:01 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: CAPL-5383 Done - Adding datamodel label to merge tasks

Automation for Jira 15 February 2024, 15:53 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: CAPL-5383 Done - Adding datamodel label to merge tasks

Automation for Jira 14 February 2024, 22:53 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: CAPL-5383 Done - Adding datamodel label to merge tasks

Automation for Jira 13 February 2024, 01:24 Jira Internal Users

@Geny Isam Hamud Herrera ,
@Douglas Coimbra Lopes , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Renan Schroeder

Flag was removed since you have just transitioned the issue status/column.

Automation for Jira 12 February 2024, 19:44 Jira Internal Users

@Geny Isam Hamud Herrera ,
@Gabriel DAmore Marciano , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Renan Schroeder

This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12, 2024-03-04

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 8 February 2024, 18:32 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Douglas Coimbra Lopes 8 February 2024, 13:37 Jira Internal Users

@Geny Isam Hamud Herrera When a record is added directly on the DM Explore, it does not generate metrics for the respective entity template. It was checked on mdm & worker pods.

Sandbox DM Link: https://totvsacepitekus.qarol.ai/devtenantdoug/carol-ui/explore/search/newtestccapl5383/rt

ENTITYTEMPLATE: newtestccapl5383

ADDING GOLDEN RECORD MANUALLY

Douglas Coimbra Lopes 8 February 2024, 13:35 Jira Internal Users

LEGACY MERGE RULES APPLIED TO THE DM

iNTAKE SENT FITTING WITH THE MERGE RULE

REPROCESS MERGE TASK CAPTURED ON ACTUATOR

Automation for Jira 7 February 2024, 01:14 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: CAPL-5383 Done - Adding datamodel label to merge tasks

Geny Isam Hamud Herrera 27 January 2024, 01:02 Jira Internal Users
Automation for Jira 23 January 2024, 16:26 Jira Internal Users

@Geny Isam Hamud Herrera ,

This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.