Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote reader do not support regex filtering in label #3401

Closed
dmitriy-lukyanchikov opened this Issue Nov 2, 2017 · 7 comments

Comments

Projects
None yet
5 participants
@dmitriy-lukyanchikov
Copy link

dmitriy-lukyanchikov commented Nov 2, 2017

What did you do?

I run query like this
node_cpu_load{host_name=~".*"}

What did you expect to see?

metrics that stored on influxdb and prometheus local storage

What did you see instead? Under which circumstances?

Only metrics that stored locally inside Prometheus DB under its own retention policy

Environment

I run Prometheus with configured remote read and wright to influxdb 1.4

  • System information:

Ubuntu 16.04.03
Linux 4.4.0-93-generic x86_64

  • Prometheus version:

prometheus, version 1.8.0 (branch: HEAD, revision: 3569eef)
build user: root@bd4857492255
build date: 20171006-22:12:46
go version: go1.9.1

  • Prometheus configuration file:
# my global config
global:
  scrape_interval:     60s # By default, scrape targets every 15 seconds.
  evaluation_interval: 30s # By default, scrape targets every 15 seconds.
  scrape_timeout: 10s
  # scrape_timeout is set to the global default (10s).

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).

# Load and evaluate rules in this file every 'evaluation_interval' seconds.

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:

  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  # Auto-discovery via consul tags by Registrator
  - job_name: 'federate_lr_metrics_node'
    scrape_interval: 30s

    honor_labels: true
    metrics_path: '/federate'

    params:
      'match[]':
         - '{__name__="node_load1"}'

    static_configs:
      - targets:
        - 'some_server:9090'


# Remote write configuration (for Graphite, OpenTSDB, or InfluxDB).
remote_write:
  - url: "http://localhost:8086/api/v1/prom/write?db=lr_prom"
# Remote read configuration (for InfluxDB only at the moment).
remote_read:
  - url: "http://localhost:8086/api/v1/prom/read?db=lr_prom"


@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Nov 9, 2017

@dmitriy-lukyanchikov Thanks for the report. You are saying you are using InfluxDB 1.4, but I don't think that version exists yet? (at least at https://github.com/influxdata/influxdb/releases, it only goes up to 1.3.7).

Are you using a version of InfluxDB that already has a built-in Prometheus remote read/write endpoint, or using an adapter?

@dmitriy-lukyanchikov

This comment has been minimized.

Copy link
Author

dmitriy-lukyanchikov commented Nov 9, 2017

@juliusv Hello! That version not released yet but you can build a docker image using this repository https://github.com/influxdata/influxdata-docker/tree/master/influxdb/nightly or use official site and download version named nightly, also in the link that you provide there is already 1.4 version https://github.com/influxdata/influxdb/releases/tag/v1.4.0

This version of InfluxDB already has built-in Prometheus remote read/write endpoint

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Nov 9, 2017

@dmitriy-lukyanchikov interesting, https://github.com/influxdata/influxdb/releases/tag/v1.4.0 just gives me a 404, and that tag also does not show for me in the list.

But I guess just checking with nightly would be sufficient.

@dmitriy-lukyanchikov

This comment has been minimized.

Copy link
Author

dmitriy-lukyanchikov commented Nov 10, 2017

hm strange indeed the error, ok try to use docker it works perfect for me, it builds in a minute without any problem

@AlekSi

This comment has been minimized.

Copy link
Contributor

AlekSi commented Jan 1, 2018

Can it be reproduced with released InfluxDB 1.4.x?

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Feb 2, 2018

Looks like this was resolved, and it would be an issue in InfluxDB rather than Prometheus anyway.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.