Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

Support AWS on Whitehall SLIs dashboard #9895

Merged
merged 1 commit into from
Dec 2, 2019

Conversation

thomasleese
Copy link
Contributor

In AWS the Whitehall Backend machines are called whitehall_backend-* whereas in Carrenza they are named whitehall-backend-*. I've changed the Graphite query to support both - and _ as the separator character.

Trello Card

In AWS the Whitehall Backend machines are called `whitehall_backend-*`
whereas in Carrenza they are named `whitehall-backend-*`. I've changed
the Graphite query to support both `-` and `_` as the separator
character.
Copy link
Contributor

@issyl0 issyl0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where do these names come from? Is one from the hostname and the other from the Puppet class? This seems inconsistent and bound to trip people up. Do we have to do this anywhere else? What would it take to fix the problem?

@thomasleese
Copy link
Contributor Author

@issyl0 It's the fully qualified domain name of the machine. So for example in AWS it's whitehall_backend-ip-10-1-4-133_eu-west-1_compute_internal whereas in Carrenza it's whitehall-backend-1_backend. The Puppet class is defined as whitehall_backend so in terms of consistency, I think the AWS one is more correct (maybe that's why it was decided to go with that naming scheme after migrating to AWS, but I don't know the details on that decision).

In a lot of cases our machine classes are just single words, so this problem doesn't come up as much as we may think.

Having a look in Puppet I can see that in some cases we've added workarounds like this and in some cases we haven't (and the dashboards only work in Carrenza).

However, there are plenty of examples where we've had to add special things like this to support differences between Carrenza and AWS (Cog links in Icinga still don't work properly in AWS is another example) so I'm not sure if it's worth trying to find a nicer solution for this since we'll hopefully be all in AWS soon anyway and then it won't matter anymore.

@thomasleese thomasleese merged commit 371677c into master Dec 2, 2019
@thomasleese thomasleese deleted the fix-whitehall-sli-dashboard branch December 2, 2019 09:53
@issyl0
Copy link
Contributor

issyl0 commented Dec 2, 2019

@thomasleese Yeah, OK. At least it's consistently inconsistent. Roll on when we're fully in AWS and we can remove all these special cases, eh? 💪

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants