Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105907 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 89895 invoked from network); 13 Jun 2019 17:11:40 -0000 Received: from unknown (HELO mail-yb1-f169.google.com) (209.85.219.169) by pb1.pair.com with SMTP; 13 Jun 2019 17:11:40 -0000 Received: by mail-yb1-f169.google.com with SMTP id p8so7886209ybo.13 for ; Thu, 13 Jun 2019 07:24:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ncsu.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=OYBLGvwylPkxif3H/xntYSuB3Q9bP672SgybfpkWPqM=; b=EYJUF/7yldUcc8O/j8qUTX9b018ma+UYZ+h2n1ZH1fcMa6Bt3yJlgdFDr3wewK44hK d2aqrTGY3N01O2JfTZv7iINY1GcsfiidI10Is/jqRdIUD9tALp4TC8gwgDnwTly/KdQY ZK8gPA6E9xMGVTGW/2D/oCdvWYbaxrD+zdGqZGfu4OBzsRd/KVE42jWVzmSNiQfpn5Ph K1g39qdUAu2Hv9GFrEQvGh3e9MaPqEv0UfFR8pYEWA3yCkXppoTYBg/Z8fwqPmI8jVmm ew5Gzjws7n5TjNgfg5Y6fQLG1La0YfxIQKgolBIXmVed4IoEtipB5xsXySIlwRVA1vAx t7cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=OYBLGvwylPkxif3H/xntYSuB3Q9bP672SgybfpkWPqM=; b=C2N7d4rT3XjqpMqG0wHwflKP4wgMt6j5DTShVfpTo16tnL0lhrOQ4guUYC1Z/oZi35 uWAWEmqo05nQ2fIHGSBZ43iGA1FW9AASLnj6+vXTJql87SRxY3mWGq17o0PU/mtjdW0U QEqYTJ0TNiHa5npsSB4irPRrFKrK5JiliGmRGlfAq5GxmnKp2+2SGoEw4ErxdQjys61W 4nx0lUGpJeT7YNHxLTvNj1wvWGvkdY1rZ3cCD7DqDGwWz0/f7x7w5pDU0Ug1N1ONNtJ8 /c94RVuFNrCAmyoDjkTrMNid5IR90Oba1CK9VEnjbWwNKMJjn0gxAkHS7lIYqDMoaVTt Rt9A== X-Gm-Message-State: APjAAAVc6BDG2LeA5D5yTtgtn0l6P1d9un+LLfCnfsV/DIotofCVNZ8Z aSLSOFw7IQtjNYjMi3YFjGemyFzUMxcxVSgIZqmrsMvRJAE= X-Google-Smtp-Source: APXvYqwRqkDHPoTS+KUOrSYVnzjg5qY6Od6UNmgxf2Gygi9q8ym9u+FOce5Bc/cE6/gth9mS312M0T1If0/MSh4t3ZE= X-Received: by 2002:a25:f50d:: with SMTP id a13mr2483313ybe.376.1560435889567; Thu, 13 Jun 2019 07:24:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 13 Jun 2019 10:24:38 -0400 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] The real world ... From: mdwheele@ncsu.edu (Dustin Wheeler) On Thu, Jun 13, 2019 at 9:36 AM Marco Pivetta wrote: > > You'd still see the DSN in the traces. > My understanding is that if using pdo.dsn.mysql via INI, you wouldn't see the username / password in traces. I only learned about this configuration reading through Sjon's PR, but looks reasonable. To the original issue Lester faces: The crux of all this is "don't use exceptions to do customer support"! Most, if not all, log aggregation software (Splunk, ELK-stack, etc.) give you the ability to configure dashboards or reports to highlight different levels of "fail-boat" in the environment. We do this in our environment, which is very heterogeneous and uncontrolled; filled with undergraduates, graduates, faculty, staff, other IT organizations and everything in-between. Not only do I have to deal with *my* logs, but I also have to help facilitate improvements to tenant applications. If it were me, I would be looking to your system administrators to improve the configuration and management of your application monitoring. If you don't have any automated monitoring (Splunk or ELK (free), Telegraf/InfluxDB, Nagios even), look into these things. Configure these to solve this problem rather than having customers be the "free" monitoring solution as a default. If I tried to pitch to my team that we would just use our users as THE monitoring solution, I'd not only get some strange looks, but also a can of surstr=C3=B6mming thrown in my face. As developers and system administrators, we can do better by our users to prevent these types of errors before they hit them. We can do this through improvements to our software design life cycle (or, to keep it simple... write tests and develop somewhere other than production). Ultimately, we're never going to catch everything... but customers reporting literal exceptions should be... exceptional :) P.S. I fully understand the "real world" sentiment even if I perceive a different reality than yours. In the "real world", people get set in their ways and higher-ed is no better a place that I have found to observe this. However, in my experience, even the saltiest of faculty with their 50 year old "Fortran codes" are amenable to change if it makes their lives easier. Applying some of these strategies *will* improve quality of work-life and *will* improve your business. Having customers report low-level exceptions / stack-traces cannot be "good for business" and must lower confidence in the product. Cheers, --=20 Dustin Wheeler | Software Developer NC State University mdwheele@ncsu.edu "If you don't know where you're going, it's easy to iteratively not get the= re."