File: control

package info (click to toggle)
mtail 3.0.9-1
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 7,348 kB
  • sloc: yacc: 617; makefile: 232; sh: 104; lisp: 77; awk: 17
file content (45 lines) | stat: -rw-r--r-- 1,813 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: mtail
Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org>
Uploaders: Martina Ferrari <tina@debian.org>,
Section: net
Testsuite: autopkgtest-pkg-go
Priority: optional
Build-Depends: debhelper-compat (= 13),
               dh-golang,
               golang-any,
               golang-github-fsnotify-fsnotify-dev,
               golang-github-golang-groupcache-dev,
               golang-github-google-go-cmp-dev,
               golang-github-pkg-errors-dev,
               golang-github-prometheus-client-golang-dev (>= 1.11~),
               golang-glog-dev (>= 1.2.0~),
               golang-go | gccgo,
               golang-go.opencensus-dev,
               golang-golang-x-tools,
               tzdata,
Standards-Version: 4.7.0
Vcs-Browser: https://salsa.debian.org/go-team/packages/mtail
Vcs-Git: https://salsa.debian.org/go-team/packages/mtail.git
Homepage: https://github.com/google/mtail/
Rules-Requires-Root: no
XS-Go-Import-Path: github.com/google/mtail

Package: mtail
Architecture: any
Depends: adduser,
         tzdata,
         ${misc:Depends},
         ${shlibs:Depends},
Built-Using: ${misc:Built-Using},
Description: Extract monitoring data from logs for collection in a timeseries database
 Mtail is a tool for extracting metrics from application logs to be exported
 into a timeseries database or timeseries calculator for alerting and
 dashboarding.
 .
 It aims to fill a niche between applications that do not export their own
 internal state, and existing monitoring systems, without patching those
 applications or rewriting the same framework for custom extraction glue code.
 .
 Metrics are exported for scraping by a collector as JSON or Prometheus format
 over HTTP, or can be periodically sent to a collectd, StatsD, or Graphite
 collector socket.