7:55 a.m.
Hi,
we just discussed this topic with Stian on
https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure if it
is worth to do or not so we should ask other KC devs for their opinion.
Server Info page contains, beside Providers info, only keycloak version
and server time. It should be good for real management/operations (based
on my few year's experience with jboss.org JIRA, SSO and other system's
operation) to extend it with other informations like:
* server uptime
* version, vendor and variant of jre used to run it
* basic info about OS (type, version)
* info about OS user KC runs under
* info about locale nad timezone used for JVM
* JVM memory statistics (total and free heap mem, perm gen mem)
* basic info about DB in case of JPA (JDBC url, JDBC driver type and
version, DB type and version) or info about used mongo (version etc)
This page should contain this info for all cluster nodes in clustered
environment.
Stian objected that this info is available form EAP/WF console, but I
think it is a bit problematic for common KC admin to access it there as
it is not integrated with KC console.
WDYT?
Thanks in advance
Vl.
--
Vlastimil Elias
Principal Software Engineer
jboss.org Development Team
9:58 a.m.
+1 To add it
----- Original Message -----
From: "Vlastimil Elias" <velias(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 13 July, 2015 2:55:48 PM
Subject: [keycloak-dev] Extend informations shown on Server Info page
Hi,
we just discussed this topic with Stian on
https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure if it is
worth to do or not so we should ask other KC devs for their opinion.
Server Info page contains, beside Providers info, only keycloak version and
server time. It should be good for real management/operations (based on my
few year's experience with jboss.org JIRA, SSO and other system's operation)
to extend it with other informations like:
* server uptime
* version, vendor and variant of jre used to run it
* basic info about OS (type, version)
* info about OS user KC runs under
* info about locale nad timezone used for JVM
* JVM memory statistics (total and free heap mem, perm gen mem)
* basic info about DB in case of JPA (JDBC url, JDBC driver type and
version, DB type and version) or info about used mongo (version etc)
This page should contain this info for all cluster nodes in clustered
environment.
Stian objected that this info is available form EAP/WF console, but I think
it is a bit problematic for common KC admin to access it there as it is not
integrated with KC console.
WDYT?
Thanks in advance
Vl.
--
Vlastimil Elias
Principal Software Engineer
jboss.org Development Team
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
10:08 a.m.
Yeah +1. Who cares if it is already in WF. Its not like you're
duplicating anything that complicated.
On 7/13/2015 10:58 AM, Stian Thorgersen wrote:
+1 To add it
----- Original Message -----
> From: "Vlastimil Elias" <velias(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Monday, 13 July, 2015 2:55:48 PM
> Subject: [keycloak-dev] Extend informations shown on Server Info page
>
> Hi,
>
> we just discussed this topic with Stian on
> https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure if it is
> worth to do or not so we should ask other KC devs for their opinion.
> Server Info page contains, beside Providers info, only keycloak version and
> server time. It should be good for real management/operations (based on my
> few year's experience with jboss.org JIRA, SSO and other system's operation)
> to extend it with other informations like:
>
>
> * server uptime
> * version, vendor and variant of jre used to run it
> * basic info about OS (type, version)
> * info about OS user KC runs under
> * info about locale nad timezone used for JVM
> * JVM memory statistics (total and free heap mem, perm gen mem)
> * basic info about DB in case of JPA (JDBC url, JDBC driver type and
> version, DB type and version) or info about used mongo (version etc)
>
>
> This page should contain this info for all cluster nodes in clustered
> environment.
> Stian objected that this info is available form EAP/WF console, but I think
> it is a bit problematic for common KC admin to access it there as it is not
> integrated with KC console.
>
> WDYT?
>
> Thanks in advance
>
> Vl.
> --
> Vlastimil Elias
> Principal Software Engineer
> jboss.org Development Team
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10:33 a.m.
On 7/13/2015 11:08 AM, Bill Burke wrote:
Yeah +1. Who cares if it is already in WF. Its not like you're
duplicating anything that complicated.
Yes, this kind of stuff is meant to be
duplicated. Anything exposed as
DMR is already accessible from multiple management clients including
CLI, CLI GUI, Web Console, jconsole, JON, etc. Much of it is also
exposed as JMX, which in this case wraps DMR.
We do need to make sure that any new runtime stats are exposed as DMR.
That way, any WildFly/EAP tool can consume it.
On 7/13/2015 10:58 AM, Stian Thorgersen wrote:
> +1 To add it
>
> ----- Original Message -----
>> From: "Vlastimil Elias" <velias(a)redhat.com>
>> To: keycloak-dev(a)lists.jboss.org
>> Sent: Monday, 13 July, 2015 2:55:48 PM
>> Subject: [keycloak-dev] Extend informations shown on Server Info page
>>
>> Hi,
>>
>> we just discussed this topic with Stian on
>> https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure if it is
>> worth to do or not so we should ask other KC devs for their opinion.
>> Server Info page contains, beside Providers info, only keycloak version and
>> server time. It should be good for real management/operations (based on my
>> few year's experience with jboss.org JIRA, SSO and other system's
operation)
>> to extend it with other informations like:
>>
>>
>> * server uptime
>> * version, vendor and variant of jre used to run it
>> * basic info about OS (type, version)
>> * info about OS user KC runs under
>> * info about locale nad timezone used for JVM
>> * JVM memory statistics (total and free heap mem, perm gen mem)
>> * basic info about DB in case of JPA (JDBC url, JDBC driver type and
>> version, DB type and version) or info about used mongo (version etc)
>>
>>
>> This page should contain this info for all cluster nodes in clustered
>> environment.
>> Stian objected that this info is available form EAP/WF console, but I think
>> it is a bit problematic for common KC admin to access it there as it is not
>> integrated with KC console.
>>
>> WDYT?
>>
>> Thanks in advance
>>
>> Vl.
>> --
>> Vlastimil Elias
>> Principal Software Engineer
>> jboss.org Development Team
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
1:35 p.m.
+1 to add it as well.
I wonder if we should create service to return all this info, so we can
use it in more places? For example we can display the info in server.log
at startup (even if it duplicates some wildfly logged info) and also
display it in stacktrace when some exception happen. This might help
support team to save some pain (they won't need to ask people about JVM,
OS, database, configured providers etc as everything will be in the
stacktrace attached to the support ticket)
Marek
On 13.7.2015 17:33, Stan Silvert wrote:
On 7/13/2015 11:08 AM, Bill Burke wrote:
> Yeah +1. Who cares if it is already in WF. Its not like you're
> duplicating anything that complicated.
Yes, this kind of stuff is meant to be duplicated. Anything exposed as
DMR is already accessible from multiple management clients including
CLI, CLI GUI, Web Console, jconsole, JON, etc. Much of it is also
exposed as JMX, which in this case wraps DMR.
We do need to make sure that any new runtime stats are exposed as DMR.
That way, any WildFly/EAP tool can consume it.
> On 7/13/2015 10:58 AM, Stian Thorgersen wrote:
>> +1 To add it
>>
>> ----- Original Message -----
>>> From: "Vlastimil Elias" <velias(a)redhat.com>
>>> To: keycloak-dev(a)lists.jboss.org
>>> Sent: Monday, 13 July, 2015 2:55:48 PM
>>> Subject: [keycloak-dev] Extend informations shown on Server Info page
>>>
>>> Hi,
>>>
>>> we just discussed this topic with Stian on
>>> https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure if it is
>>> worth to do or not so we should ask other KC devs for their opinion.
>>> Server Info page contains, beside Providers info, only keycloak version and
>>> server time. It should be good for real management/operations (based on my
>>> few year's experience with jboss.org JIRA, SSO and other system's
operation)
>>> to extend it with other informations like:
>>>
>>>
>>> * server uptime
>>> * version, vendor and variant of jre used to run it
>>> * basic info about OS (type, version)
>>> * info about OS user KC runs under
>>> * info about locale nad timezone used for JVM
>>> * JVM memory statistics (total and free heap mem, perm gen mem)
>>> * basic info about DB in case of JPA (JDBC url, JDBC driver type and
>>> version, DB type and version) or info about used mongo (version etc)
>>>
>>>
>>> This page should contain this info for all cluster nodes in clustered
>>> environment.
>>> Stian objected that this info is available form EAP/WF console, but I think
>>> it is a bit problematic for common KC admin to access it there as it is not
>>> integrated with KC console.
>>>
>>> WDYT?
>>>
>>> Thanks in advance
>>>
>>> Vl.
>>> --
>>> Vlastimil Elias
>>> Principal Software Engineer
>>> jboss.org Development Team
>>>
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
2:54 p.m.
On 7/13/2015 2:35 PM, Marek Posolda wrote:
+1 to add it as well.
I wonder if we should create service to return all this info, so we
can use it in more places?
This stuff should be available via DMR. Not sure if
we will also need
to expose as a service.
For example we can display the info in server.log at startup (even if
it duplicates some wildfly logged info) and also display it in
stacktrace when some exception happen. This might help support team to
save some pain (they won't need to ask people about JVM, OS, database,
configured providers etc as everything will be in the stacktrace
attached to the support ticket)
GSS has some cool stuff we can integrate with that
will help them
troubleshoot. I think the next version of web console in EAP exposes
it. Saw a prototype several months ago. It lets you create a case and
send logs, config files, etc. If I remember correctly, it also lets you
search the solutions database. We need to talk to GSS about this before
we craft something on our own.
Marek
On 13.7.2015 17:33, Stan Silvert wrote:
> On 7/13/2015 11:08 AM, Bill Burke wrote:
>> Yeah +1. Who cares if it is already in WF. Its not like you're
>> duplicating anything that complicated.
> Yes, this kind of stuff is meant to be duplicated. Anything exposed as
> DMR is already accessible from multiple management clients including
> CLI, CLI GUI, Web Console, jconsole, JON, etc. Much of it is also
> exposed as JMX, which in this case wraps DMR.
>
> We do need to make sure that any new runtime stats are exposed as DMR.
> That way, any WildFly/EAP tool can consume it.
>> On 7/13/2015 10:58 AM, Stian Thorgersen wrote:
>>> +1 To add it
>>>
>>> ----- Original Message -----
>>>> From: "Vlastimil Elias" <velias(a)redhat.com>
>>>> To: keycloak-dev(a)lists.jboss.org
>>>> Sent: Monday, 13 July, 2015 2:55:48 PM
>>>> Subject: [keycloak-dev] Extend informations shown on Server Info page
>>>>
>>>> Hi,
>>>>
>>>> we just discussed this topic with Stian on
>>>> https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure
>>>> if it is
>>>> worth to do or not so we should ask other KC devs for their opinion.
>>>> Server Info page contains, beside Providers info, only keycloak
>>>> version and
>>>> server time. It should be good for real management/operations
>>>> (based on my
>>>> few year's experience with jboss.org JIRA, SSO and other system's
>>>> operation)
>>>> to extend it with other informations like:
>>>>
>>>>
>>>> * server uptime
>>>> * version, vendor and variant of jre used to run it
>>>> * basic info about OS (type, version)
>>>> * info about OS user KC runs under
>>>> * info about locale nad timezone used for JVM
>>>> * JVM memory statistics (total and free heap mem, perm gen
>>>> mem)
>>>> * basic info about DB in case of JPA (JDBC url, JDBC driver
>>>> type and
>>>> version, DB type and version) or info about used mongo
>>>> (version etc)
>>>>
>>>>
>>>> This page should contain this info for all cluster nodes in clustered
>>>> environment.
>>>> Stian objected that this info is available form EAP/WF console,
>>>> but I think
>>>> it is a bit problematic for common KC admin to access it there as
>>>> it is not
>>>> integrated with KC console.
>>>>
>>>> WDYT?
>>>>
>>>> Thanks in advance
>>>>
>>>> Vl.
>>>> --
>>>> Vlastimil Elias
>>>> Principal Software Engineer
>>>> jboss.org Development Team
>>>>
>>>> _______________________________________________
>>>> keycloak-dev mailing list
>>>> keycloak-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
5:40 p.m.
All he wants is server info. Don't see a problem duplicating this info
on our server info page. GSS stuff sounds cool.
On 7/13/2015 3:54 PM, Stan Silvert wrote:
On 7/13/2015 2:35 PM, Marek Posolda wrote:
> +1 to add it as well.
>
> I wonder if we should create service to return all this info, so we
> can use it in more places?
This stuff should be available via DMR. Not sure if we will also need
to expose as a service.
> For example we can display the info in server.log at startup (even if
> it duplicates some wildfly logged info) and also display it in
> stacktrace when some exception happen. This might help support team to
> save some pain (they won't need to ask people about JVM, OS, database,
> configured providers etc as everything will be in the stacktrace
> attached to the support ticket)
GSS has some cool stuff we can integrate with that will help them
troubleshoot. I think the next version of web console in EAP exposes
it. Saw a prototype several months ago. It lets you create a case and
send logs, config files, etc. If I remember correctly, it also lets you
search the solutions database. We need to talk to GSS about this before
we craft something on our own.
>
> Marek
>
> On 13.7.2015 17:33, Stan Silvert wrote:
>> On 7/13/2015 11:08 AM, Bill Burke wrote:
>>> Yeah +1. Who cares if it is already in WF. Its not like you're
>>> duplicating anything that complicated.
>> Yes, this kind of stuff is meant to be duplicated. Anything exposed as
>> DMR is already accessible from multiple management clients including
>> CLI, CLI GUI, Web Console, jconsole, JON, etc. Much of it is also
>> exposed as JMX, which in this case wraps DMR.
>>
>> We do need to make sure that any new runtime stats are exposed as DMR.
>> That way, any WildFly/EAP tool can consume it.
>>> On 7/13/2015 10:58 AM, Stian Thorgersen wrote:
>>>> +1 To add it
>>>>
>>>> ----- Original Message -----
>>>>> From: "Vlastimil Elias" <velias(a)redhat.com>
>>>>> To: keycloak-dev(a)lists.jboss.org
>>>>> Sent: Monday, 13 July, 2015 2:55:48 PM
>>>>> Subject: [keycloak-dev] Extend informations shown on Server Info
page
>>>>>
>>>>> Hi,
>>>>>
>>>>> we just discussed this topic with Stian on
>>>>> https://issues.jboss.org/browse/KEYCLOAK-1542 and we are not sure
>>>>> if it is
>>>>> worth to do or not so we should ask other KC devs for their opinion.
>>>>> Server Info page contains, beside Providers info, only keycloak
>>>>> version and
>>>>> server time. It should be good for real management/operations
>>>>> (based on my
>>>>> few year's experience with jboss.org JIRA, SSO and other
system's
>>>>> operation)
>>>>> to extend it with other informations like:
>>>>>
>>>>>
>>>>> * server uptime
>>>>> * version, vendor and variant of jre used to run it
>>>>> * basic info about OS (type, version)
>>>>> * info about OS user KC runs under
>>>>> * info about locale nad timezone used for JVM
>>>>> * JVM memory statistics (total and free heap mem, perm gen
>>>>> mem)
>>>>> * basic info about DB in case of JPA (JDBC url, JDBC driver
>>>>> type and
>>>>> version, DB type and version) or info about used mongo
>>>>> (version etc)
>>>>>
>>>>>
>>>>> This page should contain this info for all cluster nodes in
clustered
>>>>> environment.
>>>>> Stian objected that this info is available form EAP/WF console,
>>>>> but I think
>>>>> it is a bit problematic for common KC admin to access it there as
>>>>> it is not
>>>>> integrated with KC console.
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Vl.
>>>>> --
>>>>> Vlastimil Elias
>>>>> Principal Software Engineer
>>>>> jboss.org Development Team
>>>>>
>>>>> _______________________________________________
>>>>> keycloak-dev mailing list
>>>>> keycloak-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>> _______________________________________________
>>>> keycloak-dev mailing list
>>>> keycloak-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
3475
days inactive
3475
days old
6 comments
5 participants
participants (5)
-
Bill Burke -
Marek Posolda -
Stan Silvert -
Stian Thorgersen -
Vlastimil Elias