Authentication Events
The total number of authentication events CanadaLogin recorded, including both successful and failed attempts.
An authentication event is what IBM Verify records when someone presents an authentication method. A single sign-in raises more than one: the password is one event, a second factor is another.
Calculation
Sum failed_logins and successful_logins over the selected reporting period.
To track volume over time, bin the same sum by week. Truncating from_date to the week groups each day into its Monday-anchored bin, so the result is one authentication event total per Monday-to-Sunday week.
Overall:
SELECT
SUM(failed_logins + successful_logins) AS total_authentication_events
FROM ibm_verify_events_transformed.events_auth_total_logins
-- set the reporting window; see the timespans note in cookbook/notes.qmd
WHERE CAST(from_date AS DATE) BETWEEN DATE '2026-01-01' AND DATE '2026-05-28';By week:
SELECT
date_trunc('week', CAST(from_date AS DATE)) AS week_start,
SUM(failed_logins + successful_logins) AS total_authentication_events
FROM ibm_verify_events_transformed.events_auth_total_logins
-- set the reporting window; see the timespans note in cookbook/notes.qmd
WHERE CAST(from_date AS DATE) BETWEEN DATE '2026-01-01' AND DATE '2026-05-28'
-- date_trunc('week', ...) anchors each bin to its Monday
GROUP BY date_trunc('week', CAST(from_date AS DATE))
ORDER BY week_start;Overall:
tbl(con, in_schema("ibm_verify_events_transformed", "events_auth_total_logins")) |>
# set the reporting window; see the timespans note in cookbook/notes.qmd
filter(
as.Date(from_date) >= as.Date("2026-01-01"),
as.Date(from_date) <= as.Date("2026-05-28")
) |>
summarise(
total_authentication_events = sum(failed_logins + successful_logins, na.rm = TRUE)
)By week:
tbl(con, in_schema("ibm_verify_events_transformed", "events_auth_total_logins")) |>
# set the reporting window; see the timespans note in cookbook/notes.qmd
filter(
as.Date(from_date) >= as.Date("2026-01-01"),
as.Date(from_date) <= as.Date("2026-05-28")
) |>
# floor_date(..., "week") translates to Athena's date_trunc('week', ...),
# which anchors each bin to its Monday
mutate(week_start = floor_date(as.Date(from_date), "week")) |>
group_by(week_start) |>
summarise(
total_authentication_events = sum(failed_logins + successful_logins, na.rm = TRUE)
) |>
arrange(week_start)Interpretation notes
This counts authentication events. It does not count sign-ins, and it does not count people. A single sign-in that uses a second factor records more than one successful event (see the events_auth_total_logins caveat), so the total runs ahead of how often people actually signed in. No table in the catalog counts sign-ins directly. Use a unique-user metric when the question is about reach. In the weekly view, the first and last weeks of the reporting window are usually partial (the window rarely starts or ends on a Monday), so a low count in a boundary week may reflect fewer days rather than a real dip in volume.
Alternative names
- authentication event volume
- total authentication attempts
- total sign-in attempts