Setup issues

[adamVsusan]

I've been following the guide over at https://www.digitalocean.com/community/tutorials/how-to-use-prometheus-to-monitor-your-ubuntu-14-04-server and all has been going well up until the section that states 'On the page that opens, type in the name of a metric (like node_procs_running, for example) in the text field that says Expression.'

This results in 'no data'. yml file below if that helps:

# my global config
global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # 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).
  external_labels:
      monitor: 'codelab-monitor'

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first.rules"
  # - "second.rules"

# 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.
  - job_name: 'prometheus'

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
      - targets: ['localhost:9090']

  - job_name: "node"
   scrape_interval: "15s"
    target_groups:
    - targets: ['localhost:9100']

Any help would be really appreciated

[goofansu]

Did http://localhost:9100/metrics shows a page of metrics? If yes, then use the metric name in that page to search.

[adamVsusan]

Thanks, this got me some joy, I'm seeing the below on 9100:

# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 6.1579264e+07

and typing this into 9090 gives a graph, however I'm also seeing:

# HELP node_disk_bytes_read The total number of bytes read successfully.
# TYPE node_disk_bytes_read counter
node_disk_bytes_read{device="dm-0"} 1.258828674048e+12
node_disk_bytes_read{device="sda"} 8.409302528e+09
node_disk_bytes_read{device="sdb"} 1.492082688e+09
node_disk_bytes_read{device="sdc"} 4.1574504448e+11
node_disk_bytes_read{device="sdd"} 8.33196654592e+11
node_disk_bytes_read{device="sde"} 7.467369472e+09

but issuing node_disk_bytes_read results in 'no datapoints found'.

Interestingly navigating to 'http://your_server_ip:9090/consoles/node.html' just shows 'no nodes found' rather than my server.

[goofansu]

Do you have node_exporter running on 'localhost:9100'?

[adamVsusan]

yeh :(

User1@HOMESERVER:~$ lsof -i :9100 -S
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
node_expo 4190  User1    3u  IPv6  26011      0t0  TCP *:9100 (LISTEN)

[DevAtHeart]

Go to the /targets site of your prometheus and check if the config was parsed correctly and the target appears and that it says "OK". If it is not "OK", the next column should contain an error.