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.
They don’t even have an e-mail address.
ruaok
lol
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
Any objections to going down this path?
ruaok
this feels very odd to me.
alastairp
it feels a bit weird to me to have /user/[username] work differently for one specific url
zas
should we forbid some user names to prevent future clashes with pages?
ruaok
I think I would prefer to take over the profile and put at fat message there.
but open to other solutions. one single redirect is weird and kludgy
bitmap
my first though was to put a message on the page, yea
zas
I agree with ruaok on this
bitmap
thought*
ruaok
simple too. :)
Freso
That can be done too. :)
ruaok
Freso: you can do that, yes?
Freso
Alright. Any objections to putti
ruaok: Yep.
reosarevok
But then we need to actually avoid this being autoremoved later :)
ruaok
cool, onward.
yvanzo
kiss
reosarevok
So I guess you need to also add a verified email
ruaok
make en edit?
or that.
Freso
reosarevok: I was thinking of registering it with support@
reosarevok
Freso: sure, works
Freso
Anyway.
ruaok: Improved MB monitoring
ruaok
aight.
so, we have a telegram group that we get reports about our services being in bad health.
but, it seems that it is easy to turn off notifications -- something I really try and avoid.
for obvious reasons.
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.
I'd like to improve on this.
let me go on a tangent for a minute....
back at EMusic my boss told the web and hosting teams that every 500 error will get a "page" to the whole dev team.
every single one. at all times of day.
he felt that 500s were totally inexcusable and made the punishment for them rather high.
I'm not advocating that.
but I think it is an interesting engineering philosophy. what can we do do bring out 500s to near zero>
?
that is a more philisophical question, I would like the dev team to think about.
alastairp
one thing I've noticed is that because all alerts are concentrated in 2 groups, its quite difficult to see what's yours
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.
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
reosarevok
Same
ruaok
alastairp: that's is good observation, perhaps we need to have them separated by teams.
zas
I have a bunch of ideas about improving monitoring and alerting
ruaok
agreed.
hmm.
alastairp
sometimes it feels to me like many alerts aren't actionalable by anyone, either
bitmap
right. I do have the notifications on now (sorry about that) but am open to ways to improve this
ruaok thinks
alastairp
one of the things in the google SRE book talks about how alerts should be actionable
ruaok
bitmap: can you please circle the team and think up a stop gap measure for improving things for the next.... 2 months?
yvanzo
I used to monitor SIR using grafana directly than telegram
bitmap
yes, I'll have a think
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
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.
how does that sound?
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_)
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
bitmap
ruaok: sounds good to me
ruaok
alastairp: the load ones are BS anyway. I need to fix aretha and patton to be more reasonable.
bitmap
these consul template issues just seem so opaque to me
ruaok
I think having alerts for team MB, team hosting (zas) and team pythonbrainz might make sense.
zas
yes
ruaok
bitmap: alastairp and lucifer have been doing great (laborious) work on this to improve that for pythongbrainz.
thongbrainz?
jeez, mr. kaye.
zas
;)
ruaok
alastairp, bitmap lets chat about consul improvements when we're all back from vacay, shall we?
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
we need to tweak these notifiations
ruaok
yes to all that.
bitmap
yeah, let's do that
ruaok
k.
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)
Freso
reosarevok:
reosarevok
Oh, damn, we wanted to add a quick talk about one more thing too - bitmap, can you add it to the agenda?
In the meanitme
*meantime
So: the general idea of that ticket is "how do we get more people to beta"
ruaok
summertime and then we decide to have a full meeting? heh.
reosarevok
Do people think it's too invasive to have a "go check beta" banner on prod whenever beta is out?
ruaok
a full banner, yes.
something less intrusive, perhaps.
bitmap
reosarevok: well I tried to set the topic and it crashed Konversation, lol
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
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.
Freso
Oh, remind me to look at it tomorrow?
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
And that to make us treat credits differently
But I don't have a good idea of how to do / maintain it without also bringing more unwanted visibility to the names, so
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?
So they don't just wait there for some answer?
Freso
SGTM
reosarevok
Ok, will do that for now
yvanzo
Thanks
Freso
Alright.
And I think that concludes the meeting _just_ in time for the 1h mark!