Thread: dynamic monitoring

dynamic monitoring

From
Brad DeJong
Date:
Hi all,

In the section on dynamic monitoring, I found the following
sentence confusing. I originally read it as "enclose the script"
and "used to allow that too to be checked" instead of "enclose
the script used" and "to allow that too to be checked".

    When discussing information found using dynamic tracing,
    be sure to enclose the script used to allow that too to be
    checked and discussed.

Could it be rephrased as something like this?

    When discussing information found using dynamic tracing,
    be sure to enclose the script used to find the information
    so that both the script and the information can be checked
    and discussed.

Regards,
Brad

C:\src\postgresql\doc\src\sgml>git diff -p
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 71c4f96d05..d89261326a 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -7428,7 +7428,8 @@ Total time (ns)                        2312105013
    be meaningless. In most cases where problems are found it is the
    instrumentation that is at fault, not the underlying system. When
    discussing information found using dynamic tracing, be sure to enclose
-   the script used to allow that too to be checked and discussed.
+   the script used to find that information so that both the script
+   and the information can be checked and discussed.
   </para>
   </sect2>

Re: dynamic monitoring

From
Robert Treat
Date:
On Fri, Feb 21, 2025 at 1:18 PM Brad DeJong <bpd0018@gmail.com> wrote:
>
> Hi all,
>
> In the section on dynamic monitoring, I found the following
> sentence confusing. I originally read it as "enclose the script"
> and "used to allow that too to be checked" instead of "enclose
> the script used" and "to allow that too to be checked".
>
>     When discussing information found using dynamic tracing,
>     be sure to enclose the script used to allow that too to be
>     checked and discussed.
>
> Could it be rephrased as something like this?
>
>     When discussing information found using dynamic tracing,
>     be sure to enclose the script used to find the information
>     so that both the script and the information can be checked
>     and discussed.
>
> Regards,
> Brad
>
> C:\src\postgresql\doc\src\sgml>git diff -p
> diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
> index 71c4f96d05..d89261326a 100644
> --- a/doc/src/sgml/monitoring.sgml
> +++ b/doc/src/sgml/monitoring.sgml
> @@ -7428,7 +7428,8 @@ Total time (ns)                        2312105013
>     be meaningless. In most cases where problems are found it is the
>     instrumentation that is at fault, not the underlying system. When
>     discussing information found using dynamic tracing, be sure to enclose
> -   the script used to allow that too to be checked and discussed.
> +   the script used to find that information so that both the script
> +   and the information can be checked and discussed.
>    </para>
>    </sect2>

+1 from me.

Robert Treat
https://xzilla.net