Unique Visitors HIGHER or equal to Total Visits

[Suryanto_1]

Our user complains that when they use a custom lasts 9 hours. The unique visitors are higher than the total visitors.  

From the time dropdown, we test with various timelines and is not just the customs having issues.

Our Enterprise Web Dashboard shows the following
Last 2 hours (The issue will sometimes occur)
Total Visits 310 Unique Visitors 326
Yesterday (The issue will always occur - Unique > Total)
Total Visits 3315 Unique Visitors 3346
Last 72 hours (The issue will always occur - Unique > Total)
Total Visits 10083 Unique Visitors 10542

Is anyone also facing this issue? Can someone confirm the DEFAULT query for Total Visits and Unique Visitors?

I doubt we modified the query before. Even if we do the same query now wouldn't have caused this strange behavior.

[dannemca]

Can you tell us where are you seeing this data? If it is in a Dashboard, you can click on the tile and see the details, where you can see the query for it.

[ChadTurner]

If you can provide a screen capture that would be best. Users commonly confuse Unique users and Session Count which then raise questions like this. 

[Suryanto_1]

Enterprise Web Dashboard

Total Visits

SELECT count(*) AS "Total Visits" FROM usersession
WHERE userType = "REAL_USER" AND applicationType = "WEB_APPLICATION"

Unique Visitors

SELECT count(DISTINCT internalUserId) AS "Unique Visitors" FROM usersession
WHERE userType = "REAL_USER" AND applicationType = "WEB_APPLICATION"

[ChadTurner]

I dont see any issues with the query you are using. I know there can be issues with live sessions vs completed sessions when using the USQL vs nonUSQL as USQL wont look at live sessions, but that isn't the case here. 

I've tested it in our environment and its working as expected. What cluster version are you on? 

[Suryanto_1]

We are on Dynatrace Managed version. 1.272.139

I just went in to the dashboard to confirm the query were correct.

The issue still happen but intermittence. This time round it occurs for last 7 days.

U just need to play around with all the pre-set last xx hours/days to reproduce the issue.

How can I tell if the query are USQL or nonUSQL? Are those the default query?

One thing I notice in the view details. Not sure if it matters and if they are the default.

Total Visits. Compare with previous timeframe - DISABLED

Unique Vistors. Compare with previous timeframe - ENABLED

Dynamic time-frame shift - CHECKED

Kindly advice

[ChadTurner]

I cant get the issue to reproduce, but my cluster version is 1.276.181.20231002-204711 - is it possible to upgrade your cluster and see if the issue is still present?

[Suryanto_1]

Dynatrace Managed current latest version release is 1.274.

I assume the release for 1.276 would be in a few days time.

FYI. This issue was reported few months back when our users discover it.

There were trying to use custom time like past 9 hours.

At that time we were on Dynatrace Managed version 1.268.

Anyway, would keep this thread active and see if others faces the same issue.

[Suryanto_1]

We perform upgrade but the issue still remain. 

Is there way to reset or re-create this default dashboard - " Enterprise Web Dashboard"?

We have two other account/license and we confirm everything is the same (default)

[Suryanto_1]

Seeing is believing. Heres the screenshot. Please advice

[Suryanto_1]

We are still facing this issue. Intermittently in a way. Any further advice?

From what we observed. Specifically, if you are zooming into less than 24 hours of data.

Be it if you are using the default presets of last xx hours or custom datetime set. 

[Suryanto_1 · Accepted solution]

Results returned by the COUNT(DISTINCT <field>) function are approximate to prevent high memory usage. If COUNT(DISTINCT <field>) is used on a high-cardinality field, results might be even more rough.

High-cardinality fields are those fields that have only few duplicates. There is no suggestion to use this or not use count(distinct <field>) but just the result is an approximate value, not an actual value.

https://docs.dynatrace.com/docs/platform-modules/digital-experience/session-segmentation/custom-quer...

This is due to a limitation from ElasticSeach as shown here which is still the same in their current latest 8.11 release

https://www.elastic.co/guide/en/elasticsearch/reference/7.17/search-aggregations-metrics-cardinality....
https://www.elastic.co/guide/en/elasticsearch/reference/8.11/search-aggregations-metrics-cardinality....