2

I've flagged Keep a check on 404s for moderator attention, but I can't decide myself it if's appropriate for SQA or not. So, meta. Basically, the person wants to know how best to long-term monitor a Web site for availability/errors. To me, that's not a test question. That would totally be a test question if it was about how to monitor a Web site so I can detect problems when I'm testing it, but not "How can I notify someone if my production site goes down?" The fact that the QA department in their organization is irrelevant; it's not being done as part of a test/QA activity.

https://devops.stackexchange.com/questions/920/how-to-create-a-centralised-dashboard-to-monitor-multiple-cloud-amazon-and-goog

is probably an answer to the question, or at least a starting point.

6
  • 1
    I've marked the flag as "helpful" initially but then could not decide if it is appropriate to be closed - it is still related to testing but is also related to devops/monitoring and overall tooling around testing a site for dead links. We've been also closing a lot recently and seeing that the OP is an active user with sqa site history and defending the question contributed to the decision to not close. Thanks. – alecxe Sep 12 '17 at 20:02
  • 1
    Understood, and, as I said, it's partly a philosophical question. Also a site question about whether we want to answer the same question in multiple places on multiple stackexchanges, or just have a canonical answer in one place. – Kevin McKenzie Sep 12 '17 at 20:16
  • 1
    I'm also torn on this one. Long-term monitoring for site failures/errors is a network management/devops activity, but it's not rare for test teams to find themselves pushed into activities that aren't, strictly speaking, test activities. – Kate Paulk Sep 13 '17 at 11:45
  • It is clearly not a test activity. The question I believe is "Is it a QA activity?", or more succinctly, "Is it a QA activity we support on this site?" – corsiKa Sep 13 '17 at 20:14
  • In my opinion it's definitely a QA question and something I do fairly regular for the company I work at. In the end I think that the difference between Dev Ops and QA engineering is pretty much only semantics. The availability of a system is pretty much the highest priority for product quality (you can have the best app on the face of the planet, if no one can access it it's crap) and if you host for a costumer it's one of you companies quality concerns to assure that the app stays online. – Daniel Sep 18 '17 at 10:06
  • @KevinMcKenzie I understand the desire to have a canonical answer in one place, but I don't think that's what we want to optimize for. There will always be ambiguity about where to put some kinds of questions. If we try to optimize for "each question belongs in at most one place", some people won't bother to ask questions at all, even when they're reasonable questions. – user246 Sep 18 '17 at 14:06
2

No, site monitoring questions aren't appropriate.

2

Yes, site monitoring problems are appropriate.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .