Additionally, it turns out that the "edit" account has been unused since 2006 (almost 15 years now), has no edits, votes, ratings, tags, … to their name either.
2021-08-09 22159, 2021
Freso
They don’t even have an e-mail address.
2021-08-09 22131, 2021
ruaok
lol
2021-08-09 22142, 2021
Freso
The account _would_ eventually get removed by some of the MBS tickets to clean up accounts, but I’m thinking it might be good to do it sooner and make /user/edit redirect to /account/edit
2021-08-09 22151, 2021
Freso
Any objections to going down this path?
2021-08-09 22106, 2021
ruaok
this feels very odd to me.
2021-08-09 22111, 2021
alastairp
it feels a bit weird to me to have /user/[username] work differently for one specific url
2021-08-09 22118, 2021
zas
should we forbid some user names to prevent future clashes with pages?
2021-08-09 22132, 2021
ruaok
I think I would prefer to take over the profile and put at fat message there.
2021-08-09 22148, 2021
ruaok
but open to other solutions. one single redirect is weird and kludgy
2021-08-09 22102, 2021
bitmap
my first though was to put a message on the page, yea
2021-08-09 22102, 2021
zas
I agree with ruaok on this
2021-08-09 22106, 2021
bitmap
thought*
2021-08-09 22112, 2021
ruaok
simple too. :)
2021-08-09 22118, 2021
Freso
That can be done too. :)
2021-08-09 22129, 2021
ruaok
Freso: you can do that, yes?
2021-08-09 22132, 2021
Freso
Alright. Any objections to putti
2021-08-09 22136, 2021
Freso
ruaok: Yep.
2021-08-09 22140, 2021
reosarevok
But then we need to actually avoid this being autoremoved later :)
2021-08-09 22146, 2021
ruaok
cool, onward.
2021-08-09 22147, 2021
yvanzo
kiss
2021-08-09 22147, 2021
reosarevok
So I guess you need to also add a verified email
2021-08-09 22150, 2021
ruaok
make en edit?
2021-08-09 22154, 2021
ruaok
or that.
2021-08-09 22104, 2021
Freso
reosarevok: I was thinking of registering it with support@
2021-08-09 22108, 2021
reosarevok
Freso: sure, works
2021-08-09 22112, 2021
Freso
Anyway.
2021-08-09 22121, 2021
Freso
ruaok: Improved MB monitoring
2021-08-09 22124, 2021
ruaok
aight.
2021-08-09 22148, 2021
ruaok
so, we have a telegram group that we get reports about our services being in bad health.
2021-08-09 22124, 2021
ruaok
but, it seems that it is easy to turn off notifications -- something I really try and avoid.
2021-08-09 22131, 2021
ruaok
for obvious reasons.
2021-08-09 22156, 2021
ruaok
and in the end only zas and I get the messages as of late and then have to digging around to see what is up.
2021-08-09 22103, 2021
ruaok
I'd like to improve on this.
2021-08-09 22115, 2021
ruaok
let me go on a tangent for a minute....
2021-08-09 22144, 2021
ruaok
back at EMusic my boss told the web and hosting teams that every 500 error will get a "page" to the whole dev team.
2021-08-09 22100, 2021
ruaok
every single one. at all times of day.
2021-08-09 22123, 2021
ruaok
he felt that 500s were totally inexcusable and made the punishment for them rather high.
2021-08-09 22127, 2021
ruaok
I'm not advocating that.
2021-08-09 22157, 2021
ruaok
but I think it is an interesting engineering philosophy. what can we do do bring out 500s to near zero>
2021-08-09 22158, 2021
ruaok
?
2021-08-09 22116, 2021
ruaok
that is a more philisophical question, I would like the dev team to think about.
2021-08-09 22136, 2021
alastairp
one thing I've noticed is that because all alerts are concentrated in 2 groups, its quite difficult to see what's yours
2021-08-09 22143, 2021
ruaok
more specifically, I would like the MB team to think about how to improve this. turning off telegram notifications will happen again, so that isn't a good solution.
2021-08-09 22158, 2021
alastairp
and so a lot of alerts for something that I'm not directly involved in makes it hard for me to care/think that something might actually be for me
2021-08-09 22102, 2021
reosarevok
Same
2021-08-09 22103, 2021
ruaok
alastairp: that's is good observation, perhaps we need to have them separated by teams.
2021-08-09 22110, 2021
zas
I have a bunch of ideas about improving monitoring and alerting
2021-08-09 22116, 2021
ruaok
agreed.
2021-08-09 22124, 2021
ruaok
hmm.
2021-08-09 22128, 2021
alastairp
sometimes it feels to me like many alerts aren't actionalable by anyone, either
2021-08-09 22130, 2021
bitmap
right. I do have the notifications on now (sorry about that) but am open to ways to improve this
2021-08-09 22141, 2021
ruaok thinks
2021-08-09 22145, 2021
alastairp
one of the things in the google SRE book talks about how alerts should be actionable
2021-08-09 22100, 2021
ruaok
bitmap: can you please circle the team and think up a stop gap measure for improving things for the next.... 2 months?
2021-08-09 22108, 2021
yvanzo
I used to monitor SIR using grafana directly than telegram
2021-08-09 22113, 2021
bitmap
yes, I'll have a think
2021-08-09 22124, 2021
alastairp
"load > 15" followed by "load < 15" 30 seconds later is not actionable at all, and feels like fluff that causes more messages than it's worth
2021-08-09 22138, 2021
ruaok
then lets enjoy our vacations, and then in september, let us have a meeting with zas, bitmap and myself (perhaps alastair) to discuss next steps for more concrete improvements.
2021-08-09 22141, 2021
ruaok
how does that sound?
2021-08-09 22151, 2021
alastairp
(but yes, I'm aware of the counter to that, which is that these alerts can also be useful to point us in the direction of something going wrong, high cpu temp, etc_)
2021-08-09 22152, 2021
zas
I'm delaying upgrading to grafana 8 which has many changes to alert system, and I would like to get rid of influxdb and replace it with prometheus (which would also make us able to get rid of nagios): then we need "per team" telegram alerts, which is quite easy to set up
2021-08-09 22158, 2021
bitmap
ruaok: sounds good to me
2021-08-09 22109, 2021
ruaok
alastairp: the load ones are BS anyway. I need to fix aretha and patton to be more reasonable.
2021-08-09 22134, 2021
bitmap
these consul template issues just seem so opaque to me
2021-08-09 22140, 2021
ruaok
I think having alerts for team MB, team hosting (zas) and team pythonbrainz might make sense.
2021-08-09 22152, 2021
zas
yes
2021-08-09 22104, 2021
ruaok
bitmap: alastairp and lucifer have been doing great (laborious) work on this to improve that for pythongbrainz.
2021-08-09 22113, 2021
ruaok
thongbrainz?
2021-08-09 22120, 2021
ruaok
jeez, mr. kaye.
2021-08-09 22125, 2021
zas
;)
2021-08-09 22144, 2021
ruaok
alastairp, bitmap lets chat about consul improvements when we're all back from vacay, shall we?
2021-08-09 22145, 2021
alastairp
that being said, our sentry logging for this is way too verbose, and I find I'm in the same situation as the telegram alerts
2021-08-09 22154, 2021
alastairp
we need to tweak these notifiations
2021-08-09 22102, 2021
ruaok
yes to all that.
2021-08-09 22102, 2021
bitmap
yeah, let's do that
2021-08-09 22105, 2021
ruaok
k.
2021-08-09 22107, 2021
alastairp
actually, I wanted to bring zas into this conversation about container health too
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: MBS-9841 (reo)
2021-08-09 22136, 2021
Freso
reosarevok:
2021-08-09 22139, 2021
reosarevok
Oh, damn, we wanted to add a quick talk about one more thing too - bitmap, can you add it to the agenda?
2021-08-09 22141, 2021
reosarevok
In the meanitme
2021-08-09 22142, 2021
reosarevok
*meantime
2021-08-09 22154, 2021
reosarevok
So: the general idea of that ticket is "how do we get more people to beta"
2021-08-09 22158, 2021
ruaok
summertime and then we decide to have a full meeting? heh.
2021-08-09 22120, 2021
reosarevok
Do people think it's too invasive to have a "go check beta" banner on prod whenever beta is out?
2021-08-09 22131, 2021
ruaok
a full banner, yes.
2021-08-09 22136, 2021
ruaok
something less intrusive, perhaps.
2021-08-09 22150, 2021
bitmap
reosarevok: well I tried to set the topic and it crashed Konversation, lol
2021-08-09 22100, 2021
zas
it doesn't have to be too obvious, and perhaps only targetted on auto editors?
Let's discuss this tomorrow if you mind, I have too run off
2021-08-09 22107, 2021
reosarevok
We were talking earlier and their implementation seems like it would be misused a lot, and I was especially curious about Freso's ideas on how to deal with this.
2021-08-09 22136, 2021
Freso
Oh, remind me to look at it tomorrow?
2021-08-09 22143, 2021
reosarevok
One option would be to have some specific subset of users (account admins?) be able to set a specific alias as a deadname somehow
2021-08-09 22107, 2021
reosarevok
And that to make us treat credits differently
2021-08-09 22121, 2021
reosarevok
But I don't have a good idea of how to do / maintain it without also bringing more unwanted visibility to the names, so
2021-08-09 22142, 2021
reosarevok
For now, does it seem fine to tell them that we're looking at the idea in-team and seeing what we can come up with?
2021-08-09 22148, 2021
reosarevok
So they don't just wait there for some answer?
2021-08-09 22157, 2021
Freso
SGTM
2021-08-09 22112, 2021
reosarevok
Ok, will do that for now
2021-08-09 22132, 2021
yvanzo
Thanks
2021-08-09 22138, 2021
Freso
Alright.
2021-08-09 22148, 2021
Freso
And I think that concludes the meeting _just_ in time for the 1h mark!
