Thanks for the ticket. Actually, you can use authentication [1] right now. `username` column available in SYS.CLIENT_CONNECTIONS [2] right now .
You can set username in client configuration [3] [1] https://ignite.apache.org/docs/latest/security/authentication [2] https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#client_connections [3] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConfiguration.html#getUserName-- > 17 февр. 2023 г., в 14:06, Ganguly Gundeboina <[email protected]> > написал(а): > > Raised ticket for the same > > https://issues.apache.org/jira/browse/IGNITE-18832 > > Regards, > Ganguly > > On Fri, Feb 17, 2023 at 1:07 AM Николай Ижиков <[email protected] > <mailto:[email protected]>> wrote: >> Hello, Mikhail. >> >> «Experimental feature» is a label that *some* views can be changed - like >> columns added or removed, etc. >> This happened several time in «secondary» views like SYS.JOBS >> <http://sys.jobs/>, SYS.TASKS or similar. >> >> So, any user can rely on system views - they are not going anywhere. >> >> System views specifically developed to give user ability to monitor system >> objects like connections, caches, etc. >> So, this is *correct* way to track thin client connections to the cluster. >> >> > Can someone take the enhancement to capture thin client name >> >> Please, file a ticket. >> >>> 17 февр. 2023 г., в 11:44, Mikhail Pochatkin <[email protected] >>> <mailto:[email protected]>> написал(а): >>> >>> Hi, Gunguly. >>> >>> The system views are an experimental feature and can be changed in future >>> releases [1]. This is a serious reason to not make logic in your >>> application based on this feature. Why don't you want to use public API >>> instead of experimental system views? >>> >>> [1] System Views | Ignite Documentation (apache.org) >>> <https://ignite.apache.org/docs/2.14.0/monitoring-metrics/system-views> >>> пт, 17 февр. 2023 г. в 09:34, Ganguly Gundeboina <[email protected] >>> <mailto:[email protected]>>: >>>> Hi, >>>> >>>> Can someone take the enhancement to capture thin client name in >>>> sys.client_connections table. This is required for monitoring clients. >>>> >>>> Regards, >>>> Gangaiah >>>> >>>> On Wed, Feb 15, 2023 at 2:05 AM Ganguly Gundeboina >>>> <[email protected] <mailto:[email protected]>> wrote: >>>>> Hi, >>>>> >>>>> We could see the sys.client_connections table, but does not have any >>>>> hostname/client name column. It's good to have the name column so that >>>>> can populate the client name. >>>>> >>>>> We are using 2.13. In any higher version are we enhanced this table? >>>>> >>>>> Regarding user attributes, can share the details of how can access the >>>>> attributes on the server side. >>>>> >>>>> Regards, >>>>> Gangaiah >>>>> >>>>> On Thu, Nov 11, 2021 at 10:11 PM Pavel Tupitsyn <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>>> Hi, >>>>>> >>>>>> If we are talking about Java thin client: >>>>>> >>>>>> 1. Automatic reconnect and retry is enabled out of the box. >>>>>> 2. You can use ClientConfiguration.setUserAttributes to assign custom >>>>>> key/value pairs to a client instance. Those attributes are accessible on >>>>>> the server side. >>>>>> 3. For client-side only logic, there is no built-in way to assign a name >>>>>> to a client, but you can do that with a HashMap<IgniteClient, String> >>>>>> >>>>>> On Thu, Nov 11, 2021 at 6:20 PM Ganguly Gundeboina >>>>>> <[email protected] <mailto:[email protected]>> wrote: >>>>>>> Hi, >>>>>>> >>>>>>> Want to assign specific instance name to thin clients to monitor the >>>>>>> clients. When thin client disconnected due to any reason, want to take >>>>>>> manual action like starting the client. >>>>>>> >>>>>>> We are using 2.11, can we assign? >>>>>>> >>>>>>> Regards, >>>>>>> Gangaiah >>> >>> >>> -- >>> best regards, >>> Pochatkin Mikhail. >>
