On 31 Mar 2021, at 10:25, Nuno Costa <nunoco...@gmail.com> wrote:What I meant regarding the tips was if someone knows if this is something to worry about or if is working as expected, since I did not found anything related to this change :)
ThanksOn Tuesday, 30 March 2021 at 20:33:46 UTC+1 Nuno Costa wrote:Hi All,After upgrading 2 instances to from 2.16.17 to 3.2.7, we noticed that sshd_log now shows sshd-SshDaemon instead of sshd-SshServer.2.16.17[2021-03-14 00:00:00,094 +0530] 3ba09891 [sshd-SshServer[57ed8f95]-nio2-thread-32] anotheruser LOGIN FROM anotherip3.2.7[2021-03-14T23:59:59.805+0530] f4512207 [sshd-SshDaemon[37a14aa1](port=22)-nio2-thread-57] someuser LOGIN FROM someipgerrit show-caches --show-threads command in 3.2.7 is also not showing sshd-SshServer (nor sshd-SshDaemon which I would assume to be the replacement now).Same for REST API call "/a/config/server/summary/". It will no longer return sshd-SshServer as used to.I see that the documentation[1] is still mentioning sshd-SshServer but did not see any mention to this specific change.Does anyone have some tips?Thanks,Nuno
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/50072599-9bed-4566-907c-b7f75c7d7044n%40googlegroups.com.
I believe the logging format has the thread name on it, so what you see isn’t a difference in the way Gerrit logs its SSHD data but rather the name of the current thread service that log line print.Bottom line: it’s nothing you should be worried about :-)
Thanks,Nuno
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/f0b0a103-6999-430f-9a11-b068ac304199n%40googlegroups.com.
Can you explain what is end user issue with the outputs? What isn’t working in v3.2.7?I have honestly lost the focus of the discussion :-)
With regards to the changes, the list of changes between 2.16.7 and 3.2.7 is *huge*, over 9k commits between the two releases.See the full list of changes on the release notes pages at [1], [2] and [3].
On 8 Apr 2021, at 15:51, Nuno Costa <nunoco...@gmail.com> wrote:Hi Matthias,Thanks for the reply and checking on your environment.If that is "working as designed", it is ok for us. Just wanted to make sure of it and pass the information to the team.Since we are just passing the json file returned by the API call to the monitoring system, we don't need to do anything besides removing a graph that have an empty timeline after the upgrade :)
On Thursday, 8 April 2021 at 15:28:03 UTC+1 Matthias Sohn wrote:On Thu, Apr 8, 2021 at 2:54 PM Nuno Costa <nunoco...@gmail.com> wrote:Can you explain what is end user issue with the outputs? What isn’t working in v3.2.7?I have honestly lost the focus of the discussion :-)Sorry, some times I want to give as much info as possible and with that some times it does not help :)To sum up, our issue is that "sshd-SshServer" is no longer part of cli command "gerrit show-caches --show-thread" and REST API call "/a/config/server/summary/" outputs.We were monitoring that specific metric and with 3.2.7 there is no longer that metric and we wanted to understand why.With regards to the changes, the list of changes between 2.16.7 and 3.2.7 is *huge*, over 9k commits between the two releases.See the full list of changes on the release notes pages at [1], [2] and [3].I went through all of them and did not find anything related. Maybe I did not search for the right keywords.I found documentation still mentioning "sshd-SshServer" and not "sshd-SshDaemon, as I mention in the first post.I'm just wondering if this is really a bug and we are the only ones affected by it before opening a bug report :)I think what you are observing is that sshd thread names changed between 2.16 and 3.2.
I can confirm that this is the case by looking at some of our own servers, but I didn't try to find the changewhich did this renaming. I don't think we consider thread names to be API.-Matthias
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/e43171cd-f6cd-4ec9-8875-86c3a7d7495bn%40googlegroups.com.
Hi believe there is a misconception here: you are considering the “show-caches” a monitoring API whilst it really isn’t.Also, you are using the thread name of the output as “key” for a metric, which isn’t the purpose of the command.Using a ’non-feature’ is risky because it may change at any time and we do not have any functional test for it.Why don’t you rely on Gerrit metrics [1] for extracting that information about SSH?
On 8 Apr 2021, at 19:19, Nuno Costa <nunoco...@gmail.com> wrote:Hi believe there is a misconception here: you are considering the “show-caches” a monitoring API whilst it really isn’t.Also, you are using the thread name of the output as “key” for a metric, which isn’t the purpose of the command.Using a ’non-feature’ is risky because it may change at any time and we do not have any functional test for it.Why don’t you rely on Gerrit metrics [1] for extracting that information about SSH?I cannot agree more with you on that but that's how it was implemented at the time.I see that elastic search one is deprecated and that would be useful because we use the ELK stack (being fed by json/log files) for the monitoring/analytics.
Without going the custom plugin path, JMX seems to be promising.
Any other tips are appreciated :)Nuno
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/8bd681ef-c02e-4344-883b-fbac7858bf6an%40googlegroups.com.
Hi believe there is a misconception here: you are considering the “show-caches” a monitoring API whilst it really isn’t.Also, you are using the thread name of the output as “key” for a metric, which isn’t the purpose of the command.Using a ’non-feature’ is risky because it may change at any time and we do not have any functional test for it.Why don’t you rely on Gerrit metrics [1] for extracting that information about SSH?I cannot agree more with you on that but that's how it was implemented at the time.I see that elastic search one is deprecated and that would be useful because we use the ELK stack (being fed by json/log files) for the monitoring/analytics.The ELK stack is deprecated as “index backend for Gerrit” but it isn’t deprecated at all for analytics.
See the Gerrit Analytics presentation at [5].
Without going the custom plugin path, JMX seems to be promising.The Prometheus/Grafana stack is the one you should be looking at [6].