Hi created a new mockup with a little variation. The "error" counter is
there as a placeholder really, I don't know how useful would be that.
@Evan I think we could easily add a second line in the "active users"
chart for admins. Or maybe one line for each defined rol.
[image: Inline images 1]
What do you think?
JOSE MIGUEL GALLAS OLMEDO
ASSOCIATE QE, mobile
Red Hat
<
Hi Evan,
it might be possible, there is some info attached to each Login event,
e.g. the identity provider. I’ll look into that. But i’m not sure if we
should display this information in the default dashboard, I think it’s use
case-dependent: sometimes you are interested in the roles and sometimes
almost all users have the same role anyway. Maybe we can add that
information to the database but not display it by default, but add
documentation for users who want to add it to Grafana themselves?
Regards,
Peter
Am 23.01.2018 um 20:36 schrieb Evan Shortiss <eshortis(a)redhat.com>:
Looks neat. Would adding information related to roles/user type be useful,
e.g "admin" vs standard "user" logins and activity levels per login
type?
Is it even possible?
On Tue, Jan 23, 2018 at 5:56 AM, Peter Braun <pbraun(a)redhat.com> wrote:
> Hi everybody,
>
> we’re currently discussing what the Grafana Dashboard for KeyCloak should
> look like and what kind of data is important to display. A crude mockup
> image is attached. The following metrics are candidates:
>
>
> - *Currently Logged in Users*: the number of active users over time.
> Unsure yet if we can track this reliably in KeyCloak.
> - Question/Problem: can KeyCloak reliably track this? We get the
> number of Logins and Logouts, but i’m not sure when exactly a logout is
> triggered. What if a user just logs in with KeyCloak, gets the token but
> never logs out? This is probably better suited to be tracked through SDK
> usage metrics.
>
>
>
> - *Failed Login Attempts*: useful for brute force detection. We have
> a counter for this and want to display it as a line graph over time as well
> as a bar chart for every month.
>
>
>
> - *User by Identity Provider*: The percentage of users by identity
> provider (Google, Facebook Github…). This information should be available
> in the KeyCloak Login events which are tracked.
>
>
>
> - *Memory usage over time*: A line chart showing the memory usage
> over a timespan (last day?). This data is already returned from the
> KeyCloak metrics endpoint.
>
>
> I’d appreciate any suggestions and opinions on this!
>
>
> Thanks,
> Peter
>
>
> <Bildschirmfoto 2018-01-23 um 11.32.17.png>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
EVAN SHORTISS
MOBILE DEVELOPER
Red Hat NA <
https://www.redhat.com/>
Los Angeles
evan.shortiss(a)redhat.com M: +1-781-354-2834 IM: @evanshortiss
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
@redhatnews <
https://twitter.com/redhatnews> Red Hat
<
https://www.linkedin.com/company/red-hat> Red Hat
<
https://www.facebook.com/RedHatInc>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev