victoriametrics 1.69.0+ds1-1build1 source package in Ubuntu

Changelog

victoriametrics (1.69.0+ds1-1build1) jammy; urgency=medium

  * No-change rebuild against Go 1.17

 -- William 'jawn-smith' Wilson <email address hidden>  Tue, 30 Nov 2021 14:00:08 -0600

Upload details

Uploaded by:
William Wilson
Uploaded to:
Jammy
Original maintainer:
Debian Go Packaging Team
Architectures:
any all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
victoriametrics_1.69.0+ds1.orig.tar.gz 5.6 MiB 7a0926f3fd8f51faf95b39b8fd9da74d03fd143384c3ba55107612094934c6fa
victoriametrics_1.69.0+ds1-1build1.debian.tar.xz 13.7 KiB 6028c0df6963007ca61234cac0d4e93768f376042b7d749408181ff83bcee09a
victoriametrics_1.69.0+ds1-1build1.dsc 3.4 KiB ad2543d73b4808e8f64ebb98028802eb3c7c2584bd7b02500e758b5cdb100bf0

View changes file

Binary packages built by this source

golang-github-victoriametrics-victoriametrics-dev: fast, cost-effective and scalable time series database (library)

 This package provides the library code for VictoriaMetrics.

victoria-metrics: fast, cost-effective and scalable time series database

 VictoriaMetrics is a fast, cost-effective and scalable time-series database.
 It can be used as long-term remote storage for Prometheus.
 .
 Prominent features:
  * Supports Prometheus querying API, so it can be used as Prometheus
    drop-in replacement in Grafana. VictoriaMetrics implements MetricsQL
    query language, which is inspired by PromQL.
  * Supports global query view. Multiple Prometheus instances may write
    data into VictoriaMetrics. Later this data may be used in a single query.
  * High performance and good scalability for both inserts and selects.
    Outperforms InfluxDB and TimescaleDB by up to 20x.
  * Uses 10x less RAM than InfluxDB when working with millions of unique time
    series (aka high cardinality).
  * Optimized for time series with high churn rate. Think about
    prometheus-operator metrics from frequent deployments in Kubernetes.
  * High data compression, so up to 70x more data points may be crammed into
    limited storage comparing to TimescaleDB.
  * Optimized for storage with high-latency IO and low IOPS (HDD and network
    storage in AWS, Google Cloud, Microsoft Azure, etc).
  * A single-node VictoriaMetrics may substitute moderately sized clusters
    built with competing solutions such as Thanos, M3DB, Cortex, InfluxDB or
    TimescaleDB.
  * Easy operation:
    - VictoriaMetrics consists of a single small executable without external
      dependencies.
    - All the configuration is done via explicit command-line flags with
      reasonable defaults.
    - All the data is stored in a single directory pointed by
      -storageDataPath flag.
    - Easy and fast backups from instant snapshots to S3 or GCS with
      vmbackup / vmrestore.
    - Data migration between VictoriaMetrics, Prometheus and InfluxDB with
      vmctl.
  * Storage is protectedfrom corruption on unclean shutdown (i.e. OOM,
    hardware reset or kill -9) thanks to the storage architecture.
  * Supports metrics' scraping, ingestion and backfilling (#backfilling)
    via the following protocols:
    - Metrics from Prometheus exporters such as node_exporter.
    - Prometheus remote write API
    - InfluxDB line protocol
    - Graphite plaintext protocol with tags if -graphiteListenAddr is set.
    - OpenTSDB put message if -opentsdbListenAddr is set.
    - HTTP OpenTSDB /api/put requests if -opentsdbHTTPListenAddr is set.
    - /api/v1/import.
  * Ideally works with big amounts of time series data from Kubernetes, IoT
    sensors, connected cars, industrial telemetry, financial data and
    various Enterprise workloads.
  * Has open source cluster version.

victoria-metrics-dbgsym: debug symbols for victoria-metrics