profile
viewpoint
Ferran Rodenas frodenas Palo Alto, CA

cloudfoundry-community-attic/LEGACY-bosh-getting-started 95

LEGACY documentation - please go here...

frodenas/cf-console 52

CF-Console is an easy-to-use web-based interface for your Cloud Foundry instances.

frodenas/docker-mongodb 36

A Dockerfile that produces a Docker Image for MongoDB

bosh-prometheus/firehose_exporter 26

Cloud Foundry Firehose Prometheus exporter

cloudfoundry-community/stackdriver-tools 22

Stackdriver Nozzle for Cloud Foundry Loggregator, Host Monitoring Agents BOSH Release

bosh-prometheus/cf_exporter 21

Cloud Foundry Prometheus Exporter

cloudfoundry-attic/networking-release 14

CF-BOSH Release containing several jobs to configure VM networking

frodenas/cloudfoundry-client 14

This is a Ruby wrapper for the CloudFoundry API, the industry’s first open Platform as a Service (PaaS) offering.

frodenas/alertmanager-resource 13

Concourse Alertmanager resource

frodenas/docker-couchdb 11

A Dockerfile that produces a Docker Image for CouchDB

issue commentbosh-prometheus/firehose_exporter

Counter Event Labels Have Double Underscore 6.2.0

FYI, this issue appears to be present in 6.0.0 as well... I guess I just never noticed it before.

timlharrison

comment created time in 7 hours

issue openedbosh-prometheus/firehose_exporter

Counter Event Labels Have Double Underscore 6.2.0

I upgraded to 6.2.0 in my sandbox environment and found that with the recent change to counter events, my counter event label values have a double underscore between "counter_event" and the counter. I am seeing this on both _total and _delta counters. See example below:

firehose_counter_event__failed_scrapes_total{bosh_deployment="cf-xxxxxxxxxx",bosh_job_id="xxxxxxx",bosh_job_ip="xx.xx.xx.xx",bosh_job_name="diego_cell",environment="pcf",instance_id="xxxxxxxx",origin="",product="VMware Tanzu Application Service",scrape_source_id="syslog_agent",source_id="metrics-agent",system_domain="system.pcf.domain.local"} 0

This is on VMware TAS 2.10.9

created time in 14 hours

issue commentbosh-prometheus/cf_exporter

Bad credential error with 0.10 release

Submitted a pull request to bump the go-cfclient version to a version where the client secrets are urlencoded appropriately.

ywei2017

comment created time in 7 days

PR opened bosh-prometheus/cf_exporter

Fixes bosh-prometheus/cf_exporter#50

Updates go-cfclient to a version that supports the urlencoding of client ID and client secrets passed to UAA.

Ran go mod tidy to clean up dependencies.

+224 -93

0 comment

3 changed files

pr created time in 7 days

issue openedbosh-prometheus/prometheus-boshrelease

Write TCP FirehoseVM-IP: 9186 -> Prometheus-VMIP: 49486 write: broken pipe in firehose exporter logs

Getting Write TCP FirehoseVM-IP: 9186 -> Prometheus-VMIP: 49486 write: broken pipe in firehose exporter logs. Because of it CF-Metrics were not coming in Grafana UI. Please suggest on this

created time in 12 days

fork data-decode/docker-mongodb

A Dockerfile that produces a Docker Image for MongoDB

fork in 13 days

PR opened bosh-prometheus/firehose_exporter

Convert Tags to Labels

This supersedes pull request https://github.com/bosh-prometheus/firehose_exporter/pull/56 from another contributor. PR 56 did not handle delta counters and contained broken tests. I was not able to get a response from original contributor of PR 56 so this is a new PR that contains original changes plus above fixes.

+37 -16

0 comment

2 changed files

pr created time in 14 days

issue commentbosh-prometheus/cf_exporter

Bad credential error with 0.10 release

I was able to reproduce this consistently with a client generated in the following way:

client_secret=$(openssl rand -base64 14)

When openssl generates random values it appears to almost always include an equal sign The solution was to take what is in the stackexchange conversation and do the following:

client_secret=$(openssl rand -base64 32 | tr -d /=+ | cut -c -30)

This would ensure that the equal sign was not generated. Is there something that could be updated in the cf_exporter to handle a secret with an equal sign? I have tested locally with the binary and if the secret contains an equal sign it always fails to call the cf apis.

ywei2017

comment created time in 20 days

fork tjarratt/gcs-resource

Concourse resource for interacting with Google Cloud Storage

fork in 25 days

pull request commentbosh-prometheus/prometheus-boshrelease

Fix CF Dashboard Issues

The issue has been fixed and tested. The "sed" issue was more a style than functional, since it was backward compatible.

Thanks Yansheng

ywei2017

comment created time in a month

issue closedbosh-prometheus/prometheus-boshrelease

Why there are duplicated target for cf_exportor and firehose_exportor?

I am not familied with bosh release job so can you please advised why there are duplicated exportor in my deployment? seems others have same confusion. Take cf_exportor for example, there are two configuration part in prometheus.yml: one is in file service discovery: { file_sd_configs: [ { files: [ '/var/vcap/store/bosh_exporter/bosh_target_groups.json' ] } ], job_name: 'cf', relabel_configs: [ { action: 'keep', regex: 'cf_exporter', source_labels: [ '__meta_bosh_job_process_name' ] }, { regex: '(.*)', replacement: '${1}:9193', source_labels: [ '__address__' ], target_label: '__address__' } ], scrape_interval: '4m', scrape_timeout: '2m' } another likes hardcode: { job_name: 'cf_exporter', static_configs: [ { targets: [ 'localhost:9193' ] } ] }

closed time in a month

MatthewPJ

pull request commentbosh-prometheus/prometheus-boshrelease

Fix CF Dashboard Issues

Please hold on a little bit. I think I was overly aggressive in the sed replacement. I will do more testing and correct any issues.

ywei2017

comment created time in a month

PR opened bosh-prometheus/prometheus-boshrelease

Fix CF Dashboard Issues

At one time (not sure when), many of the CF dashboards no longer show any data (if they ever did). After investigation, I found it was due to the bosh_deployment name being "cf", instead of "cf-[0-9a-f]*". I updated the json files to fix the issue, and also backward compatible. The following is a list of issues and the result with the fix.

Apps:Latency   (no data) [fixed] Apps: Requests (no data) [fixed] Apps: System (incomplete data) [fixed] CF:Organization Memory Quotas (no data for "Organization's Memory Quota Consumption") [fixed] CF:Route Emitter (no data) [fixed] CF:Summary (no data for "Users") [fixed] Component Metrics (no data) [improved]

Thanks Yansheng

+347 -347

0 comment

29 changed files

pr created time in a month

pull request commentbosh-prometheus/firehose_exporter

Convert counter_events tags to Prometheus labels

@lodener Do you know the current status of this issue? I'm also running into the issue of missing direction on loggregator_doppler_dropped_total which makes it impossible to calculate dropped message percent since I can't tell ingress vs egress.

Attempting to use Log Transport Loss Rate calculation as outlined here: https://docs.pivotal.io/application-service/2-9/overview/monitoring/key-cap-scaling.html#firehose-loss-rate

lodener

comment created time in a month

fork raychorn/docker-postgresql

A Dockerfile that produces a Docker Image for PostgreSQL

fork in a month

startedfrodenas/docker-postgresql

started time in a month

issue closedbosh-prometheus/prometheus-boshrelease

Trying to externalize alertmanager smtp & route params

I have created a file under operators/monitor-smtp-use-vars.yml folder with the below contents

  • type: replace path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/receiver/name=default?/- value: group_by: [job] group_wait: 30s group_interval: 5m repeat_interval: 12h

while trying to deploy receiving the following errors

Using deployment 'prometheus' Evaluating manifest: Expected to find an array at path '/instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/receiver/name=default' but found 'string'

Exit code 1

closed time in a month

spkrsna

issue commentbosh-prometheus/prometheus-boshrelease

Trying to externalize alertmanager smtp & route params

Thanks! will check and let u know!

spkrsna

comment created time in a month

issue commentbosh-prometheus/prometheus-boshrelease

Grafana data retention

@Muruganfly03 did that help to improve the situation for you ?

Muruganfly03

comment created time in a month

issue commentbosh-prometheus/prometheus-boshrelease

Prometheus Auto Upgrade

@Muruganfly03 not sure which kind of automation you are using, but e.g. with concourse you can watch git repositories and if a new release version is created you can automatically trigger some task

https://concourse-ci.org https://github.com/concourse/github-release-resource

Muruganfly03

comment created time in a month

issue closedbosh-prometheus/prometheus-boshrelease

Error while reading from the Firehose: websocket: close

Getting the below error in firehose vm time="2019-11-20T00:39:23Z" level=error msg="Error while reading from the Firehose: websocket: close 1006 (abnormal closure): unexpected EOF" source="firehose_nozzle.go:121" time="2019-11-20T09:49:03Z" level=info msg="Starting firehose_exporter (version=5.0.4, branch=master, revision=6f73b9dd4c8718f59ac0a5d1f03203d96fd5e7fe)" source="firehose_exporter.go:168" time="2019-11-20T09:49:03Z" level=info msg="Build context (go=go1.11.5, user=root@719955eac311, date=20190202-06:10:56)" source="firehose_exporter.go:169" time="2019-11-20T09:49:03Z" level=info msg="Listening on :9186" source="firehose_exporter.go:247" time="2019-11-20T09:49:03Z" level=info msg="Starting Firehose Nozzle..." source="firehose_nozzle.go:60" Please help out with what could be the issue..

closed time in a month

vasanth1806

issue commentbosh-prometheus/prometheus-boshrelease

Error while reading from the Firehose: websocket: close

Closed due to #401 being merged

vasanth1806

comment created time in a month

issue commentbosh-prometheus/prometheus-boshrelease

Apps: System dashboard show no data points in Grafana

@mnk628 Were you able to fix the issue?

mnk628

comment created time in a month

issue commentbosh-prometheus/prometheus-boshrelease

No data points from cf-exporter in Prometheus 25.0.0

@san4ever does the issue still persist?

san4ever

comment created time in a month

issue commentbosh-prometheus/prometheus-boshrelease

Why there are duplicated target for cf_exportor and firehose_exportor?

Hi @MatthewPJ

can you share any information which ops file you are applying when you deploy prometheus ? Like that it makes it easier to check on your question.

MatthewPJ

comment created time in a month

issue closedbosh-prometheus/prometheus-boshrelease

How can I jion in devlop and build prometheus boshrelease

How can I jion in devlop and build prometheus boshrelease

closed time in a month

leolzbing521

issue commentbosh-prometheus/prometheus-boshrelease

Trying to externalize alertmanager smtp & route params

@spkrsna For your initial try

type: replace
path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/receiver/name=default?/-
value:
group_by: [job]
group_wait: 30s
group_interval: 5m
repeat_interval: 12h

It looks to me like your indention is wrong. The whole part below value needs to be indented by two spaces, before the type you need to add a - and add indention to path and value as well, and the configuration you try to add should be below route, so I guess the ops file should look like the following:

- type: replace
  path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/group_by?
  value: [job]

- type: replace
  path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/group_wait?
  value: 30s

- type: replace
  path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/group_interval?
  value: 5m

- type: replace
  path: /instance_groups/name=alertmanager/jobs/name=alertmanager/properties/alertmanager/route/repeat_interval?
  value: 12h
spkrsna

comment created time in a month

issue closedbosh-prometheus/prometheus-boshrelease

Notice: Missing metric tags in cf-deployment v9.0.0

cf-deployment v9.0.0 which contains Loggregator Agent v3.9 with default deployment options to disable UDP listener on the loggregator agent (https://github.com/cloudfoundry/cf-deployment/blob/v9.0.0/cf-deployment.yml#L23-L24) is missing the DEPLOYMENT, JOB, INDEX, and IP tags for any metric still emitted via UDP.

The instances which contain jobs still using UDP are: api, router, and tcp-router, cell, and scheduler

It looks like this has been addressed in a later release of the Loggrator Agent but hasn't been pulled into the cf-deployment yet: https://github.com/cloudfoundry/loggregator-agent-release/commit/031c110aa0f04df9eb1544da7af783b44bf7100a

closed time in a month

jmprice

issue commentbosh-prometheus/prometheus-boshrelease

Notice: Missing metric tags in cf-deployment v9.0.0

Issue was fixed with cf-deployment version 10.0.0

jmprice

comment created time in a month

PR opened bosh-prometheus/prometheus-boshrelease

truncated metric names in bosh System Overview

Commit a2d769c (just before the v23 release) truncated two metrics in the BOSH / BOSH: System Overview dahsboard.

screenshots

+2 -2

0 comment

1 changed file

pr created time in 2 months

more