Dominik Schulz

When talking about on-call rotations and escalations people tend to get really creative. I'd suggest to try to keep things simple and first introduce an team API. A team would...

I am currently looking into different ways of implementing the team notifications. I will open up another PR when and if I have something that looks good to me.

With PR #13 this branch should be more or less feature complete (wrt. team escalations). @chrissnell While there are still some missing tests and documentation I`d like to hear your...

@chrissnell With everything I feel necessary in the teamescalation branch I'd like to start discussing what is missing to merge this in to master.

Never mind, I just wanted to wait for feedback before merging this into master. Unless I find any blocking issues in the next days, I'll merge the teamescalation branch to...

Hi, I was pretty busy lately. Right now I can't say if I can put any more effort into this project or not. If it's OK for I'd suggest to...

So you're saying that this is rather the maintainers fault? In that case we can't do anything about it and close this issue.

IMHO we should rely on provided API and not heuristics, but we could make this optional.

I've never built anything but amd64/linux docker images. We *may* look into this in the future ...

Thank you for bringing this up. I see two options here: Either you don't use conflicting rows names in your queries, or we rename these fields in the SQL exporter....