report configs

[Wessel Dankers]

On 2003-06-07 23:45:28+0200, Wessel Dankers wrote:
> oi!
> 
> I found this snippet in an old Config API proposal:

[snip snippet]

Other proposal:

    <param name="report"> <!-- list -->
      <param name="header">Summary</param>
      <param name="requests-summary"/>
      <param name="requests-summary-by-method"/>
      <param name="header">All Requests</param>
      <param name="top-requesting-hosts"> <!-- dictionary -->
        <param name="hosts_to_show">10</param>
      </param>
      <param name="top-requested-names">
        <param name="names_to_show">10</param>
      </param>

<!-- You may want to uncomment those if you run a
     version of Bind9 that doesn't log the resolver method.
      <param name="requesttype-distribution"/>
      <param name="requests-by-period">
        <param name="period">1d</param>
      </param>
      <param name="requests-by-timeslot">
        <param name="timeslot">1h</param>
      </param>
-->
      
      <param name="requesttype-by-method"/>
      <param name="req-by-period-by-method">
        <param name="period">1d</param>
      </param>
      <param name="req-by-timeslot-by-method">
        <param name="timeslot">1h</param>
      </param>

      <param name="header">Recursive Requests</param>
      <param name="select-resolver"> <!-- filter -->
        <param name="method">recurs</param>
      <param>
      <param name="top-requesting-hosts">
        <param name="hosts_to_show">10</param>
      </param>
      <param name="top-requested-names">
        <param name="names_to_show">10</param>
      </param>

      <!-- filter ends here, but how can we tell? -->
	  	  
      <param name="header">Non Recursive Requests</param>
      <param name="select-resolver">
        <param name="method">nonrec</param> <!-- filter -->
        <param name="top-requesting-hosts">
          <param name="hosts_to_show">10</param>
        </param>
        <param name="top-requested-names">
          <param name="names_to_show">10</param>
        </param>
      </param>
    </param>

Pros:
• The report gets selected using the usual config mechanism (we'd have to
  activate the "services" sections for that).
• It uses standard Config components.

Cons:
• The filtering scope is not explicit (it's another layer on top of the XML
  structure, in a sense).
• There's still no differentiation between different schemata. (But that
  can be added).



-- 
Wessel Dankers <wsl at logreport.org>

“Sticky bits on disk.”

-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org