RE: [DebMetrics] Looking for feedback on manifest format
Joseph,
This is excellent news. I have been working to collect and deliver metrics internally to describe bug/fix trends as well as code volatility. You may want to abstract the database from the manifest. Exposing the fields and database names to an external API is asking somebody to screw with your data in ways you never planned for. It also ties many external users directly to your schema. By doing this, changing the schema in the future will be difficult (if not impossible).
Bill Brothers | HP Cloud | +1 916 521 8560
________________________________________
From: Joseph Bisch [joseph.bisch@gmail.com]
Sent: Tuesday, May 13, 2014 10:04 AM
To: debian-qa@lists.debian.org
Subject: [DebMetrics] Looking for feedback on manifest format
Hello,
I am a student participating in Google Summer of Code. For GSoC, I am
working on Debian Metrics Portal that will provide a uniform interface
for adding, updating, and viewing metrics related to Debian. The data
will be pushed or pulled from a variety of sources, but during GSoC
only a select few sources will be implemented.
I am seeking feedback on a manifest file format. This file will be
used to define data sources. Below is the current iteration of the
format:
[script1]
type = pull|push
kind = static|transient
deps = dep1, dep2, dep3, ... # optional; can be used to define dependencies
freq = min hour dom month dow year # crontab format
url = http://www.example.com/script # for push metrics; don't include for pull
tablename = Name
fields = field1, field2, field3, ... # ts is field, but isn't defined by client
types = Integer, Integer, Integer, ... # correspond to the fields in fields
format = json|xml|fixed_width|tab|csv
[script2]
type = pull|push
...
...
...
The metrics portal will be able to handle both remote push metrics
that will call a remote script and pull metrics where a script will
run locally on the metrics portal server. Some data is historical (not
changing) whereas some is changing. That is the reason for kind. Types
matches SQLAlchemy types. Format specifies the output format of the
script.
If you want to follow my coding check out the git repo[0]. Progress
will be updated on the soc-coordination mailing list and my blog[1]
which is syndicated on planet.d.o.
[0] http://anonscm.debian.org/gitweb/?p=users/josephbisch-guest/debmetrics.git;a=summary
[1] http://www.josephbisch.com/
Joseph
--
To UNSUBSCRIBE, email to debian-qa-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] CAO+PtjuxdZpa4qe5mMpSwmdxv+npxXdZR7kuaY0xCYMxME+iAA@mail.gmail.com">https://lists.debian.org/[🔎] CAO+PtjuxdZpa4qe5mMpSwmdxv+npxXdZR7kuaY0xCYMxME+iAA@mail.gmail.com
Reply to: