pcp
[Top] [All Lists]

[question] PCP UI FrontEnd

To: "pcp@xxxxxxxxxxx" <pcp@xxxxxxxxxxx>
Subject: [question] PCP UI FrontEnd
From: Aurelien Gonnay <aurelien.gonnay@xxxxxxxxx>
Date: Mon, 27 Jul 2015 12:49:26 +0000
Accept-language: en-US, fr-FR
Cc: TED-DEV-CSP <TED-DEV-CSP@xxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
Thread-index: AdDIamDhgJgo6eXUSG27tcoSWenKBA==
Thread-topic: [question] PCP UI FrontEnd

Hi,

 

I’m currently collecting a bunch of metrics from several servers using PCP.

It has been so far a pretty convincing experience from a monitoring / collection of metrics point of view.

However, on the UI front, I’m having a rather frustrating experience.

When using graphite (either plain graphite or grafana) and I’m facing 2 issues:

1.       Metric name encoding: our servers are using ‘-‘ in their name, which do not play well with the metric name encoding.

2.       Performance of pmwebd graphite api: the api is fairly slow, namely to browse the instance domains in archives. (I’ll send a separate email to discuss more specifically the perf issue.)

 

Moreover pcp metric definition are more comprehensive than graphite can cope with, and I’m feeling like we are not making the most out of the collected metrics.

 

What solutions are used by seasoned PCP users to visualize realtime/historical metrics, for

1.       dashboards used on a daily basis,

2.       deep-dive solution to investigate / correlate events when a given production issue arises

 

Thanks in advance for your feedback,

 

Aurelien Gonnay

 

 ___________________________________

The integrity of this message cannot be guaranteed on the internet. Therefore EXANE cannot be considered responsible for the contents.
If you are not the intended recipient of this message, please delete it and notify the sender.

This message is provided for information purposes only and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
Although it may contain some elements from publications produced by Exane's research department, this message is not research.
Please consult our web site for important disclaimers and disclosures concerning Exane's research. (http://www.exane.com)
 ___________________________________
<Prev in Thread] Current Thread [Next in Thread>