Database Management

SQL Sentry Portal Bug - Upgrade to 2023.4 causes issue with Portal not loading with GraphQL Error trying to resolve field 'targetHealth'

The purpose of this internal article is to address the know bug in the portal that is being experienced by several SQL Sentry Portal Users after upgrading to version 2023.4.

First published date

11/30/2023 9:12 PM

Last published date

2/20/2025 11:59 PM

Overview

Overview of repro steps for bug:
 
  1. Customer upgraded to SQL Sentry Version 2023.4 and above.
  2. Launched the portal and on the dashboard it appears for a few seconds then the data disappears. (Error stack around 'targetHealth' and seeing a Health Score of 0 along with this error stack is acceptable to link for this bug.)
Full Error Stack Example with WEB_URL as the placeholder for Portal URL being used:


GraphQL error: Error trying to resolve field 'targetHealth'.
Error: GraphQL error: Error trying to resolve field 'targetHealth'. at new n (WEB URL) at n.getCurrentResult (WEB_URL) at n.getQueryResult (WEB_URL) at i.getExecuteResult 
(WEB_URL) at n.execute 
(WEB_URL) at Gh 
(WEB_URL) at Kh 
(WEB_URL) at u8 
(WEB_URL) at Cse 
(WEB_URL) at aa (WEB_URL)




image.png

Additionally there might be some alternative error stacks on this and might present a different flavor of this bug, but to clarify the Alternative Error Stack within the screenshot below is NOT related to this known bug.

image.png
 

Product section

SQL Sentry (SQLS)

Cause

No root cause determined at this time other than upgrading to 2023.4 version of SQL Sentry. As a side note you might come across a Health Score of 0 along with this error stack for 'targetHealth', which would be acceptable to link it to the bug, but if you were to see a Health Score of 0 without this error stack, then it is not apart of this bug. Health scores simply being 0 without this error explicitly being observed is not this Bug. Its most likely the behavior related to the formula for calculating the health score was not originally meant to be exposed at lower levels below Global, as this is not possible in the thick client. It is also because of this that calculations don’t seem to make sense when compared at various levels. i.e. The score for a group compared to the score of the targets in that group.

image.png

Resolution

Backlog item created to address this issue as it is affecting several SQL Sentry Users for the Portal Enhanced Feature.  Fix is planned for release in 2024.2 release