Subscription Dashboard - Top 5 nAck reasons report not considering date filter

Description

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

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

@Breno Zipoli Monteiro Papa
02 - PROBLEM (WHAT'S THE ISSUE?):

The Top 5 nAck reasons report on Data Subscription Dashboard is not considering date filter.

Even when subscription data have nAck reasons filled on the table, the report shows No Data.

After some investigation, I noticed that the query sent to big query is not considering the date filter (10/05/2023):

SELECT
  COUNT(1) AS nAckedCount,
  s.responseMessage
FROM
  systemlog_materializedview s
WHERE
  1 = 1
  AND mdmCounterForEntity__DATETIME__ >= DATETIME('2023-12-05T19:05:00')
  AND s.tenantId = 'c0885b64e699400e941f7c3709090d6e'
  AND COALESCE(s.responseMessage, '') <> ''
  AND COALESCE(s.acked, FALSE) = FALSE
  AND s.logtype IN ('SUBSCRIPTION_DEADLETTER',
    'SUBSCRIPTION')
GROUP BY
  s.responseMessage
ORDER BY
  nAckedCount DESC
LIMIT
  5

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):

The query use the same date filter as the other queries on the dashboard.

Activity

Automation for Jira 2 August 2024, 20:18 Jira Internal Users

@Breno Zipoli Monteiro Papa ,
@Renan Fernando Schroeder , @Carlos Affonso Wagner ,

Este issue foi planejada para ser entregue até 2024-09-27. Você pode confirmar consultando o campo Due Date desta issue.

Data já planejadas para esta issue: 2024-09-27

Se o campo External Issue Link estiver preenchido com o link de uma issue válida no Jira Produção o cliente também será notificado no Jira Produção.