Network Monitoring Request Schema 1.0

Operating systemsOS : Windows
Program licensingScript Licensing : Freeware
CreatedCreated : Mar 1, 2007
Size downloadDownloads : 3
Program licensing
Thank you for voting...

 The schema should therefore allow the specification ...

 The schema should therefore allow the specification of the following information for tests that they wish performed, or test data they wish to retrieve:
What: measurement/metric information
Where: source & destination identifiers
When: time information
How: test parameters
General Demands:
   1. Where possible and appropriate use equivalent schema element names and structures to those used in the NMWG response schema [1].
   2. It should be possible to specify a query (albeit a simple one) with a minimum amount of information. This would be a test start and end point, a time, and a test type (metric/measurement). Note: this is a definition of the minimum set of information required to request a test or historic data, not the minimum set of values to be contained in a message based on the schema. Default values could be defined for non-specified information. For example, if it was not specified in the message, the start point of a test could be assumed to be the system receiving the request.
What - Measurement/Metric Information:
   1. The measurement to be made/metric data to provided (characteristic) should be specified using a DAMED style name [2], as in NM-WG schema [1].
   2. To avoid making the schema overly complex, and to avoid overloading the receiving system, it should only be possible to specify one characteristic in each message based on the schema.
   3. In addition to basic metrics, it should also be possible to request statistical data concerning a characteristic (e. g. min, max and average values).
   4. The schema should be extensible to allow requests to be made for statistical data that is currently unsupported by the NM-WG schema [1].
   5. To find the minimum value of a statistic over a past period would require a system to look over all the data from that past period. If the requestor then wanted the maximum value, the process would have to be repeated. To cut down on receiving system overhead it should be possible to request multiple statistical analyses in the same request message.
   6. A means should be provided to specify a sample interval on which statistical analyses should be made. This should default to the whole period time period for which a request has been made. The sample interval should be measured in seconds, to match other time related parameters, as discussed in a later section.
Where - Source & Destination Information:
   1. The method of specifying addresses for test source and destination points should be flexible, to allow IP addresses (both IPv4 and v6), hostnames, and even textual names to be used. As an example of the latter, a user may want to refer to a test source and destination as “ core router” and “ edge router” , thus hiding the IP addresses. This would however require the requestor and receiver to have prior knowledge of such names.
When - Time Information:
   1. The schema should provide two basic means of specifying the time period for which tests should be run, or data should retrieved.
         1. a start and end time, which returns all matching data/test results between those times
         2. a target time and time tolerance which returns a single value
Note: these time types can request the scheduling of tests, if the times are at all in the future.

Network Monitoring Request Schema 1.0 scripting tags: network monitoring, schema, xml schema, request, request schema, test, data. What is new in Network Monitoring Request Schema 1.0 software script? - Unable to find Network Monitoring Request Schema 1.0 news. What is improvements are expecting? Newly-made Network Monitoring Request Schema 1.1 will be downloaded from here. You may download directly. Please write the reviews of the Network Monitoring Request Schema. License limitations are unspecified.