pm, Alan Christie
> wrote:
>
> Hi,
>
> OpenShift ansible tag: openshift-ansible-3.11.152-1
> Ansible: 2.7.13
>
> I’m trying to install metrics using NFS as the storage back-end and, although
> the NFS export and PVC is created, it’s not creating the unde
Hi,
OpenShift ansible tag: openshift-ansible-3.11.152-1
Ansible: 2.7.13
I’m trying to install metrics using NFS as the storage back-end and, although
the NFS export and PVC is created, it’s not creating the underlying PV,
preventing the hawular-cassandra pod from starting
On Aug 16, 2019, at 4:55 AM, Daniel Comnea wrote:
On Thu, Aug 15, 2019 at 7:46 PM Clayton Coleman wrote:
>
>
> On Aug 15, 2019, at 12:25 PM, Daniel Comnea wrote:
>
> Hi Clayton,
>
> Certainly some of the metrics should be preserved across reloads
On Thu, Aug 15, 2019 at 7:46 PM Clayton Coleman wrote:
>
>
> On Aug 15, 2019, at 12:25 PM, Daniel Comnea wrote:
>
> Hi Clayton,
>
> Certainly some of the metrics should be preserved across reloads, e.g.
> metrics like *haproxy_server_http_responses_total *should be p
On Aug 15, 2019, at 12:25 PM, Daniel Comnea wrote:
Hi Clayton,
Certainly some of the metrics should be preserved across reloads, e.g.
metrics like *haproxy_server_http_responses_total *should be preserved
across reload (though to an extent, Prometheus can handle resets correctly
with its native
Hi Clayton,
Certainly some of the metrics should be preserved across reloads, e.g.
metrics like *haproxy_server_http_responses_total *should be preserved
across reload (though to an extent, Prometheus can handle resets correctly
with its native support).
However, the metric
built.
>> Am i right to assume that the image [1] is is built as it's seen without
>> any other layer being added to include [2] ?
>> Also am i right to say the haproxy metrics [2] is part of the origin
>> package ?
>>
>>
>> A bit of background/ context:
Metrics memory use in the router should be proportional to number of
services, endpoints, and routes. I doubt it's leaking there and if it were
it'd be really slow since we don't restart the router monitor process
ever. Stats should definitely be preserved across reloads,
; any other layer being added to include [2] ?
> Also am i right to say the haproxy metrics [2] is part of the origin
> package ?
>
>
> A bit of background/ context:
>
> a while back on OKD 3.7 we had to swap the openshift 3.7.2 router image
> with 3.10 because we were
Hi,
Would appreciate if anyone can please confirm that my understanding is
correct w.r.t the way the router haproxy image [1] is built.
Am i right to assume that the image [1] is is built as it's seen without
any other layer being added to include [2] ?
Also am i right to say the haproxy me
Thank You. Not sure how I missed that.
On Fri, Feb 8, 2019 at 8:06 PM Clayton Coleman wrote:
>
> https://github.com/openshift/router/blob/master/pkg/router/metrics/haproxy/haproxy.go
>
> Is what converts haproxy stats from the stats socket to prometheus metrics
>
> On Feb 8
https://github.com/openshift/router/blob/master/pkg/router/metrics/haproxy/haproxy.go
Is what converts haproxy stats from the stats socket to prometheus metrics
On Feb 8, 2019, at 8:48 AM, Gowtham Sundara <
gowtham.sund...@rapyuta-robotics.com> wrote:
Hello,
May I know where the source co
Hello,
May I know where the source code for the openshift haproxy router metrics
prometheus binary is present? (edited)
I would like to know more about how the `haproxy_server_bytes_out_total` is
calculated.
--
Gowtham Sundara
Site Reliability Engineer
Rapyuta Robotics “empowering lives with
Hello,
This issue[1] is opened for weeks and CentOS users are still doing
(partial) workarounds to make it (partially) working in their environments.
I'd like to know who is responsible for building the metrics images and
send me an e-mail so we can fix this. I'm part of the CentOS Paa
It's possible this is a regression since a new overview was introduced in
3.6. Ideally, you should have valid certificates in a production
environment. If you're just wanting to test, you can visit the metrics URL
directly and accept the certificate. If you've done that and still do
Hi everyone,
Currently I'm using v3.6.1, but still meet this bug below
https://bugzilla.redhat.com/show_bug.cgi?id=1382728
please advise me how to fix it.
Thanks.
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/opensh
ture invisible
>>> Gartner Cool Vendor 2017
>>>
>>> 2017-09-28 10:19 GMT-03:00 Matthew Wringe :
>>>
>>>> Wait, there is another update that we need. That PR probably wont work
>>>> properly for you yet. I am investigating
>>>>
2017
>>
>> 2017-09-28 10:19 GMT-03:00 Matthew Wringe :
>>
>>> Wait, there is another update that we need. That PR probably wont work
>>> properly for you yet. I am investigating
>>>
>>> On Thu, Sep 28, 2017 at 9:06 AM, Matthew Wringe
>>>
Thu, Sep 28, 2017 at 9:06 AM, Matthew Wringe
>> wrote:
>>
>>> The PR is this: https://github.com/openshift/origin-metrics/pull/382
>>>
>>> It was a problem in one of our releases of Hawkular Metrics, but I
>>> didn't think it made it into the 3.6 release
I have this version of OSE here
[root@ose-master-01-bk /]# openshift version
openshift v3.5.5.31.36
kubernetes v1.5.2+43a9be4
etcd 3.1.0
I am looking for a file metrics-deployer.yaml
if I do a find on it I get many many of them, what one would i want to use,
what does the version numbers
I am using the directions here that state I need to enter in the FQDN of
the hawkular host
how can I find this value for hawkular host , or am I defining that
value here somehow ?
3.2.1. Deploying the Metrics Components
OpenShift Container Platform uses Hawkular Metrics as its metrics engine
. I am investigating
>
> On Thu, Sep 28, 2017 at 9:06 AM, Matthew Wringe
> wrote:
>
>> The PR is this: https://github.com/openshift/origin-metrics/pull/382
>>
>> It was a problem in one of our releases of Hawkular Metrics, but I didn't
>> think it made it into
Wait, there is another update that we need. That PR probably wont work
properly for you yet. I am investigating
On Thu, Sep 28, 2017 at 9:06 AM, Matthew Wringe wrote:
> The PR is this: https://github.com/openshift/origin-metrics/pull/382
>
> It was a problem in one of our releases of
The PR is this: https://github.com/openshift/origin-metrics/pull/382
It was a problem in one of our releases of Hawkular Metrics, but I didn't
think it made it into the 3.6 release (but it did).
On Thu, Sep 28, 2017 at 8:41 AM, Mateus Caruccio <
mateus.caruc...@getupcloud.com> wrot
om
>>>> .br.int.crt"}]
>>>> openshift_master_session_auth_secrets=['F71uoyI/Tkv/LiDH2PiF
>>>> KK1o76bLoH10+uE2a']
>>>> openshift_master_session_encryption_secrets=['bjDwQfiy4ksB/3
>>>> qph87BGulYb/GUho6K']
>>>&
aster_session_encryption_secrets=['bjDwQfiy4ksB/
>>> 3qph87BGulYb/GUho6K']
>>> openshift_master_audit_config={"enabled": true, "auditFilePath":
>>> "/var/log/openshift-audit/openshift-audit.log",
>>> "maximumFileRetentionDays": 30,
aximumFileSizeMegabytes": 500,
>> "maximumRetainedFiles": 10}
>>
>> openshift_ca_cert_expire_days=1825
>> openshift_node_cert_expire_days=730
>> openshift_master_cert_expire_days=730
>> etcd_ca_default_days=1825
>>
>> openshif
openshift_node_cert_expire_days=730
> openshift_master_cert_expire_days=730
> etcd_ca_default_days=1825
>
> openshift_hosted_router_create_certificate=false
> openshift_hosted_manage_router=true
> openshift_router_selector="role=infra"
> openshift_hosted_router_replicas=2
t_expire_days=730
openshift_master_cert_expire_days=730
etcd_ca_default_days=1825
openshift_hosted_router_create_certificate=false
openshift_hosted_manage_router=true
openshift_router_selector="role=infra"
openshift_hosted_router_replicas=2
openshift_hosted_router_certificate={"certfile&qu
We had an issue where it was not possible for normal users to view their
metrics (but cluster-admin users could). But I didn't think this made it
into any releases.
Would it be possible to attach the inventory file used?
On Thu, Sep 14, 2017 at 8:34 AM, Paul Weil wrote:
> Includ
Including some metrics folks. Matt/Jeff?
On Wed, Sep 13, 2017 at 9:44 PM, Mateus Caruccio <
mateus.caruc...@getupcloud.com> wrote:
> Answering my own question, that "namespace" field on audit log refers to
> the unamespaced resource "/oapi/v1/subjectaccessreviews
; $ oc version
>> oc v3.6.0+c4dd4cf
>> kubernetes v1.6.1+5115d708d7
>> features: Basic-Auth GSSAPI Kerberos SPNEGO
>>
>> Server
>> openshift v3.6.0+c4dd4cf
>> kubernetes v1.6.1+5115d708d7
>>
>>
>> $ oc -n openshift-infra get rc -o yaml | grep image:
correct
> (secrets, servicaccounts, token, etc)?
>
> $ oc version
> oc v3.6.0+c4dd4cf
> kubernetes v1.6.1+5115d708d7
> features: Basic-Auth GSSAPI Kerberos SPNEGO
>
> Server
> openshift v3.6.0+c4dd4cf
> kubernetes v1.6.1+5115d708d7
>
>
> $ oc -n o
erver
openshift v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
$ oc -n openshift-infra get rc -o yaml | grep image:
image: docker.io/openshift/origin-metrics-cassandra:v3.6.0
image: docker.io/openshift/origin-metrics-hawkular-metrics:v3.6.0
image: docker.io/openshift/origin-me
In general /metrics is just a snapshot at that point in time - starting
with 3.6, we'll be leveraging prometheus more to collect these metrics for
operators. If you are running an alpha / nightly OpenShift cluster on
3.6.0-alpha.2 or later, you can try out the new Prometheus example in
githu
Hi
What is the difference of running a dedicated Prometheus server Vs using
metrics exposed by oc get –raw metrics? If both are same in terms of accuracy,
available information, does it make sense to run again another Prometheus
server and pull cluster metrics?
Am trying to setup some metrics
Access issue fixed. I could see rich amount of information or metrics to
measure the cluster health.
However, am having difficult to interpretation or accuracy of the data.
For example: am getting below value for etcd. I don’t believe etcd db size is
0 in my prod cluster
# TYPE
I have a cluster admin but unable to see in browser. OC get working fine.
{"kind": "Status","apiVersion": "v1","metadata": {},"status":
"Failure","message": "User \"system:anonymous\" cannot \"
Awesome … is the same metrics exposed by Prometheus as well? Am seeing
Prometheus also exposing the same but less then oc get metrics. oc get metrics
is giving more info.
Also, how to get metrics of kubelet?
--
Srinivas Kotaru
From: "ccole...@redhat.com"
Date: Thursday, February 2
Resending to dev list.
On Thu, Feb 23, 2017 at 5:31 PM, Clayton Coleman
wrote:
> Yes, the apiserver, the controllers, and the nodes all expose metrics on
> their serving port. The controllers listen on localhost only today.
>
> You can view the api server metrics as a suitably pri
Does API server expose any metrics like https://apiserver/metrics or any other
form?
--
Srinivas Kotaru
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
I think the repo below is for OpenShift V2. The V3 tools repo is at
https://github.com/openshift/openshift-tools
and the Zabbix monitoring scripts are at
https://github.com/openshift/openshift-tools/tree/prod/scripts/monitoring
Tim
Erik Jacobs wrote:
Re-adding the list (bad reply-to)
Erik
Re-adding the list (bad reply-to)
Erik M Jacobs, RHCA
Principal Technical Marketing Manager, OpenShift
Red Hat, Inc.
Phone: 646.462.3745
Email: ejac...@redhat.com
AOL Instant Messenger: ejacobsatredhat
Twitter: @ErikonOpen
Freenode: thoraxe
On Wed, Feb 1, 2017 at 4:26 PM, Erik Jacobs wrote:
>
We want to measure the health of OpenShift cluster from all possible ways and
report status back to clients in a single simple page. I have few things in mind
Health of:
· API servers
· etcd servers
· nodes (kubectl??)
· SDN
· PV’s
· Routers s
Any comments?
--
Srinivas Kotaru
From:
mailto:dev-boun...@lists.openshift.redhat.com>>
on behalf of skotaru mailto:skot...@cisco.com>>
Date: Wednesday, July 13, 2016 at 7:01 PM
To: dev mailto:dev@lists.openshift.redhat.com>>
Subject: Accessing Metrics Using Hawkular Metrics
Can you fix below documentation? Date examples throwing below error
usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
[-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
No JSON object could be decoded
<https://github.com/openshift/origin-metrics/b
- Original Message -
> From: "David Dimas"
> To: dev@lists.openshift.redhat.com, "Matt Wringe"
> Sent: Friday, April 1, 2016 11:40:19 AM
> Subject: How to get a list of projects from origin-metrics
>
> Hello, How are you?
>
> The openshift AP
Hello, How are you?
The openshift API does provide us a Rest API that will allow us to get a
list of projects under a given user account.
https://docs.openshift.com/enterprise/3.0/rest_api/openshift_v1.html#v1-project
However, I am going to get this from origin-metrics.
Finally, I am going to
- Original Message -
> From: "David Dimas"
> To: dev@lists.openshift.redhat.com
> Sent: Thursday, March 10, 2016 5:46:41 AM
> Subject: Accessing all metrics for a Project
>
> I am running openshift vm.
> when I run this command on command prompt, I am gett
I am running openshift vm.
when I run this command on command prompt, I am getting JSON object.
# curl -k -X GET https://hawkular-metrics.example.com/hawkular/metrics/status
{"MetricsService":"STARTED","Implementation-Version":"0.12.0.Final"
But I
50 matches
Mail list logo
