Suite of libraries and applications for collecting high volume performance counter data
Перейти к файлу
microsoft-github-policy-service[bot] 4cb1ae2d74
Auto merge mandatory file pr
This pr is auto merged as it contains a mandatory file and is opened for more than 10 days.
2022-11-28 19:14:22 +00:00
doc Update metricsystem_swagger.yaml 2015-11-11 16:24:57 -08:00
src removed unnecessary references 2016-01-13 11:08:34 -08:00
unittest Add support for legacy Bing format data files. 2015-09-28 20:56:17 -07:00
.gitattributes Initial public source release. 2015-06-15 21:34:40 -07:00
.gitignore Initial public source release. 2015-06-15 21:34:40 -07:00
LICENSE Add support for LZ4Net compression streams to support legacy Bing data formats. Update license accordingly. 2015-09-28 20:10:46 -07:00
MetricSystem.sln Update missed copyright messages, add a REST API doc (not 100% complete but close) 2015-09-09 17:22:34 -07:00
MetricSystem.sln.DotSettings Add ReSharper settings file. 2015-09-29 15:04:55 -07:00
README.md Initial public source release. 2015-06-15 21:34:40 -07:00
SECURITY.md Microsoft mandatory file 2022-08-15 21:16:43 +00:00

README.md

MetricSystem

Suite of libraries and applications for collecting high volume performance counter data

Documentation

A full set of documentation is (or will be!) available in the doc/ directory of the code.

Structure

This code is broken into a set of libraries (some with interdependencies) and associated unit test code. The following libraries are provided:

  • Client: Client for reading from and writing to MetricSystem servers.
  • Configuration: Code for providing JSON-based configuration of counters and the (unreleased) service.
  • Data: The core data libraries for reading/writing/querying raw MetricSystem data.
  • Schemas: Bond schemas used when interacting with MetricSystem server APIs.
  • Server: An HTTP server which provides RESTful API access to underlying MetricSystem data (on this and other servers).
  • Utilities: Stuff that didn't fit elsewhere and was commonly used across multiple projects. Every sufficiently large project has one of these. There's probably a So-and-so-from-usenet's law for this.