Custom queries, segmentation, and aggregation of session data

Dynatrace captures detailed user session data each time a user interacts with your monitored application. This data includes all user actions and high level performance data. Using either the Dynatrace API or Dynatrace User Sessions Query Language (USQL), you can easily run powerful queries, segmentations, and aggregations on this captured data. To assist you, this topic provides detail about keywords and functions, syntax, working with Real User Monitoring tables, automated queries, and more.

Select your preferred approach:

Keywords and functions

The following keywords have been defined to access user session data:

AND, AS, ASC, BETWEEN, BY, DESC, DISTINCT, FALSE, FROM, GROUP, IN, IS, JSON, LIMIT, NOT, NULL, OR, ORDER, SELECT, STARTSWITH, TRUE, WHERE, LIKE, FILTER

The following functions have been defined to access user session data:

SUM, MAX, MIN, AVG, MEDIAN, COUNT, YEAR, MONTH, DAY, HOUR, MINUTE, DATETIME, TOP, PERCENTILE, KEYS

Keywords, functions, and column names are case-insensitive. String-matches in WHERE conditions are case-sensitive.

Syntax

A typical query is built from the following keywords:

SELECT <columns> FROM <table> WHERE <condition> GROUP BY <grouping> ORDER BY <ordering>

However, the only mandatory elements are SELECT <columns> and FROM <table>.

SELECT browserType, userId, city, AVG(userActionCount) AS "Average user action count", AVG(duration) AS "Average duration", count(*) AS "Sessions", SUM(totalErrorCount) AS "Errors" FROM usersession WHERE ip between '52.179.11.1' and '52.179.11.255' GROUP BY browserType, userId, city

Frequently used keywords

SELECT <columns>

Selects one or more columns from the specified data table or performs aggregation functions from the set of supported functions.

columns: [DISTINCT] <column>, <column>, ... | function(<parameter>) |
<column> AS <alias> | JSON

SELECT country, city, browserfamily FROM usersession
SELECT DISTINCT country, city, useractioncount FROM usersession
SELECT country, city, avg(duration) AS average FROM usersession GROUP BY country, city

FUNNEL

Allows you to use a predefined funnel format for a query. Can be used to chart the flow of specific user actions. Can also be combined with custom session properties and other conditions.

It changes the syntax of any query to the following:

SELECT FUNNEL (<condition> AS <alias>, <condition>, ...) FROM <table> WHERE <condition>

SELECT COUNT(*) FROM usersession where useraction.name = "AppStart"
SELECT COUNT(*) FROM usersession where useraction.name = "AppStart" AND useraction.name = "searchJourney"
SELECT COUNT(*) FROM usersession where useraction.name = "AppStart" AND useraction.name = "searchJourney"  AND useraction.name = "bookJourney"

SELECT FUNNEL (useraction.name = "AppStart", useraction.name = "searchJourney", useraction.name = "bookJourney")
FROM usersession

SELECT FUNNEL (useraction.name="login", useraction.name = "searchJourney", useraction.name = "bookJourney")
FROM usersession

FROM <table>

You can only specify one table. Tables for user session data are as follows.

SELECT country, city, browserfamily FROM usersession
SELECT name, starttime, endtime, duration FROM useraction ORDER BY duration DESC

WHERE <condition>

You can combine multiple conditions using Boolean logic and parentheses within the WHERE clause, such as WHERE (city = 'Barcelona' AND country = 'Spain') to include only cities named Barcelona that are in Spain.

condition: (condition AND condition) | (condition OR condition) | field IN(...) |
field IS <value> | field IS NULL | field = <value> | field > <value> | field < <value> |
field <> <value> | field IS NOT <value> | field BETWEEN <value> AND <value> | ...

However, only the right-hand side of conditions can contain a value, so you can't compare between two fields.

SELECT country, city, browserfamily FROM usersession WHERE country = 'Albania' AND screenWidth > 1000

SELECT TOP(country, 20), TOP(city, 20), TOP(duration, 10), AVG(duration) AS average
FROM usersession
WHERE duration BETWEEN 1000 AND 2000
GROUP BY TOP(country, 20), TOP(city, 20), TOP(duration, 10)

GROUP BY <grouping>

Whenever fields are aggregated, you must specify corresponding GROUP BY keywords to indicate how the aggregation is to be performed.

grouping: <column>, ...

SELECT city, count(*) FROM usersession GROUP BY city
SELECT MONTH(starttime) as month, count (*) FROM usersession
GROUP BY month

LIMIT <limit>

Allows you to limit the number of returned results. For example, you can select only the top 10 results when it is combined with ordering.

The framework always applies an upper limit to prevent system overload. If LIMIT is not used, 50 results are returned by default.

SELECT city, starttime FROM usersession ORDER BY starttime DESC LIMIT 10

LIMIT can also be used to increase the number of results in cases where the LIMIT clause is missing, because then a default limit is applied.

ORDER BY <ordering>

Allows you to order the results by columns, in either ascending or descending order. The order is ascending if not specified.

The ordering is done by frequency. For example, the top 5 returned cities are the most frequently occurring ones. By specifying a field in the ORDER BY clause, you can add a sort-by value for strings, dates, and numbers.

Ordering by enums or by function values such as AVG and SUM orders the returned results, but you may not get the top items. For example, if you request the top 5 results by AVG(duration), requesting only 10 may add results even at the top.

ordering: <column> ASC | <column> DESC | <column>, ...

SELECT useraction.name, starttime FROM usersession ORDER BY starttime DESC

SELECT DISTINCT city, COUNT(*) FROM usersession ORDER BY COUNT(*) DESC

SELECT avg(duration) AS average, count(*) as number, day(startTime) as startDay
FROM usersession where duration < 2000
GROUP BY startTime
ORDER BY average

SELECT avg(duration) AS average, count(*) as number, day(startTime) as startDay
FROM usersession where duration < 2000
GROUP BY startTime
ORDER BY number DESC, average ASC

LIKE

Allows you to compare data with an expression by using wildcard characters to match the specified pattern. You can use the following characters:

String values are case-sensitive. For example, SELECT city FROM usersession WHERE userId LIKE "*dynatrace*" matches me@dynatrace.com but not me@dynaTrace.com. To avoid this, use the ? wildcard character as in this example: SELECT city FROM usersession WHERE userId LIKE "*dyna?race*"

SELECT userId FROM usersession WHERE userId LIKE "AU\%40KWM"

SELECT userId FROM usersession WHERE userId like "AU\*40KWM"

SELECT userId FROM usersession WHERE userId LIKE "AU\?40KWM"

SELECT userId FROM usersession WHERE userId LIKE "AU\\%40KWM"

SELECT CONDITION(COUNT(userSessionId), WHERE useraction.name LIKE '*search.html'),
       CONDITION(COUNT(userSessionId), WHERE useraction.name LIKE '*booking-payment1.html')
FROM usersession
WHERE city LIKE "%York"
    OR city LIKE "S*Francisco"
    AND city LIKE "L*inz"

SELECT FUNNEL (useraction.name LIKE "*start", useraction.name LIKE "Jou%rney", useraction.name LIKE "bookJourn*ey") FROM usersession

SELECT COUNT(*) FROM usersession where useraction.name LIKE "*start"
SELECT COUNT(*) FROM usersession where useraction.name LIKE "*start" AND useraction.name LIKE "Jou%rney"
SELECT COUNT(*) FROM usersession where useraction.name LIKE "*start" AND useraction.name LIKE "Jou%rney" AND useraction.name LIKE "bookJourn*ey"

FILTER

Allows you to filter for functions that have numeric values, thereby displaying only specific results from aggregations.

SELECT useraction.application,
AVG(usersession.doubleProperties.bookings)
FILTER > 1500
FROM usersession
WHERE usersession.doubleProperties.bookings IS NOT NULL
GROUP BY useraction.application

Frequently used functions

MIN(field)

Queries the minimum value of a numeric or date field.

SELECT MIN(duration), MAX(duration), AVG(duration), MEDIAN(duration)
FROM usersession

MAX(field)

Queries the maximum value of a numeric or date field.

SELECT MIN(duration), MAX(duration), AVG(duration), MEDIAN(duration)
FROM usersession

AVG(field)

Queries the average value of a numeric or date field. May be NaN if the field is always null.

SELECT MIN(duration), MAX(duration), AVG(duration), MEDIAN(duration)
FROM usersession

MEDIAN(field)

Queries the median value of a numeric or date field.

SELECT MIN(duration), MAX(duration), AVG(duration), MEDIAN(duration)
FROM usersession

SUM(field)

Computes the sum of a numerical field.

SELECT TOP(name, 20), SUM(duration) FROM useraction
GROUP BY name

COUNT(field), COUNT(*), COUNT(DISTINCT field)

Counts the number of rows that match.

SELECT country, COUNT(*), COUNT(city), COUNT(DISTINCT city)
FROM usersession
GROUP BY country

SELECT country, COUNT(*), COUNT(city), COUNT(DISTINCT city)
FROM usersession
GROUP BY country

TOP(field, n)

Returns the top <n> results from a field. The default is 1 (the top value) if n is not specified.

SELECT TOP(name, 20), SUM(duration)
FROM useraction
GROUP BY name

SELECT TOP(country, 20), TOP(city, 3), COUNT(*)
FROM usersession
GROUP BY country

YEAR(datefield), MONTH(datefield), DAY(datefield), HOUR(datefield), MINUTE(datefield)

Returns the given element extracted from a date field.

SELECT starttime,
DATETIME(starttime), YEAR(starttime), MONTH(starttime), DAY(starttime), HOUR(starttime), MINUTE(starttime)
FROM usersession
ORDER BY starttime DESC

DATETIME(datefield [, format [, interval]])

Formats the selected date field with the given format string. The default format is yyyy-MM-dd HH:mm.

The allowed letters within the format string are:

The year|month|week intervals are for a single interval. For d (days), h (hours), m (minutes), or s (seconds), you can use a number followed by the letter for the format string, such as 5m. For example, SELECT DISTINCT DATETIME(starttime, 'HH:mm', '5m'), COUNT(*) FROM usersession counts sessions in five-minute time blocks.

SELECT DATETIME(starttime, 'yyyy-MM') FROM usersession
SELECT DISTINCT DATETIME(starttime, 'HH:mm', '5m'), COUNT(*) FROM usersession

Similar to other date functions (YEAR, MONTH, DAY, HOUR, and MINUTE), you can use DATETIME to format a result (even the result of other functions like MAX, MIN, AVG, or CONDITION), create histograms, or retrieve a list of timestamps where there are results, for example, the days of a week when an application was used.

SELECT application, DATETIME(MAX(starttime)) AS LastUsedTime FROM useraction GROUP BY application

SELECT DATETIME(starttime, "HH") AS hourOfDay, COUNT(*) FROM usersession GROUP BY hourOfDay

SELECT application, DATETIME(starttime, "E") AS daysOfWeek FROM useraction GROUP BY application

SELECT DATETIME(CONDITION(MAX(startTime), WHERE name = "index.jsp")) FROM useraction

CONDITION(function, condition)

Allows you to combine multiple functions with various conditions.

The allowed functions within the format string are as follows:

You can combine multiple conditions using Boolean logic and parentheses with the CONDITION function, such as CONDITION(COUNT(*), WHERE city = 'Barcelona' AND country = 'Spain') to include only cities named Barcelona that are in Spain.

CONDITION(function, condition)

condition:
(condition AND condition) | (condition OR condition) | field IN(...) |
field IS <value> | field IS NULL | field = <value> | field > <value> | field < <value> |
field <> <value> | field IS NOT <value> | field BETWEEN <value> AND <value> | ...

You can also use the FILTER clause filter for functions that have numeric values, thereby displaying only specific results from aggregations.

SELECT CONDITION(COUNT(usersessionId), WHERE userActionCount > 2 AND useraction.name = "search.jsp") FILTER > 1000, city FROM usersession GROUP BY city

SELECT CONDITION(COUNT(usersessionId), WHERE userActionCount > 2 AND useraction.name = "search.jsp") FROM usersession

SELECT CONDITION(SUM(usersession.duration), WHERE name = "index.jsp") AS c1, CONDITION(SUM(usersession.duration), WHERE name = "search.jsp") AS c2, CONDITION(SUM(usersession.duration), WHERE name IS NOT "index.jsp" AND name IS NOT "search.jsp") AS c3 FROM useraction WHERE (duration > 1000 OR usersession.userActionCount > 4)

SELECT CONDITION(SUM(usersession.duration), WHERE name = "index.jsp") AS c1 FROM useraction WHERE (duration > 1000 OR usersession.userActionCount > 4) ORDER BY c1

SELECT DATETIME(CONDITION(MIN(startTime ), WHERE useraction.application = "RUM Default Application" ), "yyyy-MM-dd" ) FROM usersession

PERCENTILE

Represents a value below which there's a percentage of data points lower in value. Useful in detecting the speed of your application for customers who receive the slowest response time.

SELECT name, usersession.country, usersession.browserFamily,
AVG(duration),
MEDIAN(duration),
PERCENTILE(duration, 99)
FROM useraction
WHERE useraction.name = "easytravel/rest/login"
GROUP BY usersession.country, usersession.browserFamily, name
ORDER BY usersession.continent

KEYS(customProperty)

Returns keys of user action or user session properties according to the property data type defined in the argument.

Check the table below to understand whether keys of user action properties or keys of user session properties are returned.

KEYS(customProperty)

Table

Action properties

Session properties

KEYS(<dataType>Properties)

useraction

KEYS(<dataType>Properties)

usersession

KEYS(useraction.<dataType>Properties)

useraction

KEYS(useraction.<dataType>Properties)

usersession

KEYS(usersession.<dataType>Properties)

useraction

KEYS(usersession.<dataType>Properties)

usersession

The <dataType> part of the function can take the following values:

SELECT KEYS(stringProperties) FROM useraction WHERE application = "easyTravel demo application"
SELECT KEYS(useraction.longProperties) FROM usersession WHERE applicationType="WEB_APPLICATION" ORDER BY keys(useraction.longProperties)
SELECT KEYS(usersession.stringProperties) FROM useraction WHERE usersession.city ="Berlin"

For fetching distinct keys of action or session properties, use DISTINCT KEYS(customProperty).

SELECT DISTINCT KEYS(stringProperties) FROM useraction WHERE useraction.application = "easyTravel demo application" ORDER BY keys(stringProperties)
SELECT DISTINCT KEYS(doubleProperties) FROM usersession

Mathematical operations

The following operations are supported as part of queries:

Syntax

Number/NumericField/DateTimeField/Function OPERATOR Number/NumericField/DateTimeField/Function

Function: YEAR, MONTH, DAY, HOUR or MINUTE Operator: +, -, *, /, %, or MOD

SELECT 7 + 80 * 100, duration + startTime, MONTH(startTime) - 1
FROM usersession

Conditions

All conditions must start with an identifier, such as a field name, and must be compared against a value. Two fields can't be compared against each other.

Basic operators

The basic operators for comparison are =, !=, <>, <, >, <=, >=, IS, and IS NOT.

To check if the value of a field is present, compare the field against NULL.

SELECT userId FROM usersession WHERE userActionCount > 3

Ranges

Ranges are handled by keywords such as BETWEEN or NOT BETWEEN, <lowerLimit>, and <upperLimit>.

SELECT DISTINCT ip FROM usersession
WHERE ip BETWEEN '192.168.0.0' AND '192.168.255.255'

SELECT startTime FROM useraction
WHERE NOT startTime BETWEEN $NOW - DURATION("2h") AND $NOW

SELECT ip, browserType, userId, city
FROM usersession
WHERE NOT ip BETWEEN '52.179.11.1' AND '52.179.11.255'

Sets

The IN keyword can be used shorten "WHERE" <field> = val1 OR <field> = val2 OR <field> = val3.

SELECT userId FROM usersession WHERE city IN ("NEW YORK", "San Francisco")

String conditions

The "STARTSWITH" string condition checks whether a string or an enum field starts with the specified text.

SELECT city FROM usersession WHERE userId STARTSWITH "dynatrace"

Datetime values

When conditions are run on a datetime field, the following value formats are supported:

For the formats where time is optional, the following time formats are supported:

SELECT starttime FROM usersession WHERE starttime > "8.8.2018 8:00"

Condition optimization

IN

When your query contains multiple "equals" conditions for the same field via OR, use the IN function instead, as it's more performant. For example, you can rewrite the following query using the IN function.

SELECT COUNT(*) FROM userevent
WHERE pageReferrer = "/some/page/referrer/1"
  OR pageReferrer = "/some/page/referrer/2"
  OR pageReferrer = "/some/page/referrer/3"
  OR pageReferrer = "/some/page/referrer/4"
  OR pageReferrer = "/some/page/referrer/5"

SELECT COUNT(*) FROM userevent
WHERE pageReferrer IN ("/some/page/referrer/1",
  "/some/page/referrer/2",
  "/some/page/referrer/3",
  "/some/page/referrer/4",
  "/some/page/referrer/5")

NOT IN

To optimize the speed of your queries, use arrays for queries: instead of using several NOT, <>, or != operators, use the NOT IN operator.

SELECT useraction.name, usersession.userId
FROM useraction
WHERE name = "loading of page /"
  AND usersession.userId IS NOT NULL
    AND usersession.userId <> "Speed Travel Agency"
    AND usersession.userId <> "some user"
    AND usersession.userId <> "easyTravel - One step to happiness"
    AND usersession.userId <> "easyTravel - Booking - Finish"

SELECT useraction.name, usersession.userId
FROM useraction
WHERE name = "loading of page /"
  AND usersession.userId IS NOT NULL
    AND NOT usersession.userId IN ("Speed Travel Agency",
    "some user",
    "easyTravel - One step to happiness",
    "easyTravel - Booking - Finish")

Advanced syntax constructs

Query IP ranges

The IP field can be queried for ranges of addresses. Both BETWEEN ip > <lower ipaddress range> AND ip < <upper ipaddress range> or BETWEEN <lower ipaddress range> AND <lower ipaddress range> work.

SELECT * FROM usersession WHERE ip > '211.44.94.0' AND ip < '212.113.5.0'
SELECT * FROM usersession WHERE ip BETWEEN '211.44.94.0' AND '212.113.5.0'

Query timeframe selector

You can use the following keywords to select the start time and end time as defined in the timeframe selector.

SELECT * FROM usersession WHERE startTime >= $TIME_FRAME_START AND endTime < $TIME_FRAME_END

Timeframe selectors can be used to limit the timeframe on queries that are run on secondary tables (useraction). By default, the timeframe filter is applied on the usersession table, even if the query is run on any secondary table. To apply the filter on a secondary table as well, you can use the timeframe selector to add a condition on the startTime field of the secondary table. See the following example to fetch the name and duration of user actions that occurred only in the query timeframe:

SELECT name, duration FROM useraction
WHERE startTime BETWEEN $TIME_FRAME_START and $TIME_FRAME_END

Query relative timeframe

You can select a timeframe relative to the time when the query was run. The current time is expressed with the $NOW variable.

$NOW [+/-] DURATION("[number]TIME_UNIT")

The following time units are supported to express the duration:

SELECT * FROM usersession WHERE startTime >= $NOW - DURATION("1q") AND endTime <= $NOW
SELECT * FROM useraction WHERE startTime BETWEEN $NOW - DURATION("2h") AND $NOW
SELECT * FROM useraction WHERE usersession.startTime >= $TIME_FRAME_START - DURATION("2h") AND $NOW - DURATION("1h")

Secondary tables for usersession, useraction, userevent, and usererror

When using SELECT with usersession, useraction, userevent, or usererror, columns from the other table can be accessed and included in the results by prefixing column names with the table name.

SELECT city, useraction.name FROM usersession
SELECT usersession.city, name FROM useraction

SELECT usersession.country, name, page FROM userevent

SELECT usersession.country, name, type FROM usererror

SELECT country, userevent.name, usererror.name FROM usersession

When you query from the usersession primary table, you can combine fields from other secondary tables (useraction, userevent, and usererror). You can use fields from the secondary tables in the WHERE condition too.

SELECT city, useraction.name, userevent.page, usererror.type FROM usersession

SELECT city, usererror.name, userevent.page, useraction.duration FROM usersession WHERE usererror.name IS NOT NULL

SELECT * FROM usersession
WHERE userevent.application = "a" OR useraction.application="a"

When you query from any of the secondary tables (useraction, userevent, or usererror), you can use fields only from the usersession primary table; you can't use fields from other secondary tables. For example, the query below fails, as the selected table is userevent, which means that only fields from userevent or usersession can be selected.

SELECT usersession.city, useraction.name, userevent.page, usererror.type FROM userevent

The same limitation applies to other secondary tables—useraction and usererror.

SELECT usersession.userId, name, duration FROM useraction

SELECT usersession.userId, name, type FROM usererror

SELECT * FROM usersession
WHERE useraction.name = "a" AND useraction.name = "b"

SELECT usersession.*, * FROM useraction
WHERE useraction.name = "a" AND useraction.duration > 1000

SELECT COUNT(usersession.userSessionId)
FROM usersession
WHERE userevent.name = 'Page change'
  AND userevent.pageGroup = '/Booking'
  AND userevent.type = 'UserTag'

SELECT COUNT(usersession.userSessionId)
FROM userevent
WHERE userevent.name = 'Page change'
  AND userevent.pageGroup = '/Booking'
  AND userevent.type = 'UserTag'

Filtering using fields of a secondary table

Be careful when filtering using the fields of one of the secondary tables. Consider the examples below.

Example 1

SELECT useraction.name FROM usersession WHERE useraction.name="abc"

This query returns a list of all user sessions that contain at least one user action named abc. The result contains a list of all user actions for each session because the query is run on the usersession level.

Example 2

SELECT name FROM useraction WHERE name="abc"

This query retrieves a list of only those user actions that are named abc.

SELECT * FROM table

SELECT * FROM usersession
SELECT useraction.* FROM usersession
SELECT city, useraction.* FROM usersession
SELECT *, useraction.* FROM usersession

JSON export

The JSON keyword adds an additional column that contains the data about the requested entry (a user session, user action, user event, or user error) in JSON format.

If you select the usersession primary table, the full JSON strings for the matching user sessions are returned, regardless of the selected columns.

SELECT usersessionId, browserFamily, useraction.name, useraction.duration, JSON
FROM usersession LIMIT 5

If you select a secondary table (useraction, userevent, or usererror), the full JSON strings for the matching sub-entry (a user action, user event, or user error) are returned.

SELECT name, duration, JSON
FROM useraction LIMIT 5

See also Export user sessions.

Escaping strings

String literals can be put within single or double quotes. However, if you want to use the same quotation mark inside the string, simply double it.

SELECT * FROM usersession WHERE userId = "some 'custom' name for ""my user"""
SELECT * FROM usersession WHERE userId = 'some ''custom'' name for "my user"'

Funnel charting

Funnel charting allows you to track steps through your digital service and investigate the areas of struggle faced by your users. In conjunction with Session Replay, this functionality allows you to see at which point your user is struggling in your application.

SELECT FUNNEL(
useraction.name = "AppStart (easyTravel)" AS "Open easytravel",
useraction.name = "searchJourney" AS "Search journey",
useraction.name = "bookJourney" AS "Book journey",
useraction.matchingConversionGoals = "Payment" OR useraction.matchingConversionGoals = "booking-finished" AS "Booked")
FROM usersession

You can also filter for a specific segment. An example of this is using Session properties to extract the list of high priority customers.

SELECT FUNNEL(
useraction.name = "AppStart (easyTravel)" AS "Open easytravel",
useraction.name = "searchJourney" AS "Search journey",
useraction.name = "bookJourney" AS "Book journey",
useraction.matchingConversionGoals = "Payment" OR useraction.matchingConversionGoals = "booking-finished" AS "Booked")
FROM usersession
WHERE stringProperties.memberstatus="GOLD"

Available user session data tables and fields

For user session data, the following tables are available.

Secondary tables for usersession, useraction, userevent, and usererror include a description of how data in one of those tables is available in the other.

Run USQL queries for custom reports

A REST interface allows you to get results for your custom queries. All you need is to create a unique API token with the User session query language privilege. The ability to query user session data this way is useful in automated testing, data verification, and other automated functions. It includes the following endpoints:

/table: Returns the data as a flat table, even when grouping by various items and performing hierarchical aggregations against the user session data.

/tree: Returns the data as a full hierarchical tree based on the input.

The following query-parameters are available:

query: Needs to be encoded when put into a URL, for example, %20 instead of spaces. startTimestamp/endTimestamp: Allows you to define points in time, passed as the number of milliseconds since the Unix epoch. If not specified, this defaults to the last two hours.

curl --location --insecure -H "Content-Type: application/json" -H "Authorization: Api-Token _token_" \
-XGET "https://{your-environment-id}.live.dynatrace.com/api/v1/userSessionQueryLanguage/table?query=select%20city,count(*)%20from%20usersession%20group%20by%20city"

{
    "columnNames": ["city",    "count(*)"],
    "values": [
        ["Dublin",    23],
        ["N. Virginia (Amazon)",    80],
        ["Portland",    56]
    ]
}

curl --location --insecure -H "Content-Type: application/json" -H "Authorization: Api-Token _token_" \
-XGET "https://{your-environment-id}.live.dynatrace.com/api/v1/userSessionQueryLanguage/tree?query=select%20country,city,count(*)%20from%20usersession%20group%20by%20country,city"

{
    "branchNames": ["country",    "city"],
    "leafNames": ["count(*)"],
    "values": {
        "United States": {
            "Portland": [56],
            "N. Virginia (Amazon)": [83]
        },
        "Ireland": {
            "Dublin": [24]
        }
    }
}

Learn more about user sessions API.

Convert queries into USQL custom metrics

You can convert some queries into USQL custom metrics for your web, mobile, and custom applications.

Limitations