| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PMDA Metrics Limit |
| From: | Marko Myllynen <myllynen@xxxxxxxxxx> |
| Date: | Wed, 9 Mar 2016 15:43:39 +0200 |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <2036692062.28640709.1457387057371.JavaMail.zimbra@xxxxxxxxxx> |
| Organization: | Red Hat |
| References: | <56DD8CE8.9020202@xxxxxxxxxx> <2036692062.28640709.1457387057371.JavaMail.zimbra@xxxxxxxxxx> |
| Reply-to: | Marko Myllynen <myllynen@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
Hi, On 2016-03-07 23:44, Nathan Scott wrote: > ----- Original Message ----- >> [...] >> It would seem that the limitation still exists for PMDAs, see the below >> test PMDA - it works as expected if the innermost loop is removed from >> generate_metrics() (676 metrics added) but if the innermost loop is in >> place, then only 1024 metrics are added even though there are over 17k >> metrics in the hash: >> [...] >> $pmda->add_metric(pmda_pmid(0, $i++), > > You're not using the cluster space (the 0 above) - only item ($i above), > which is limiting the number of metrics you can have artificially here. Confirmed, by putting max 1024 metrics per cluster space all the ~17k metrics can be added for the PMDA. This makes me wonder shouldn't the user get some sort of warning about the situation, now data is silently discarded in a non-obvious manner? Thanks, -- Marko Myllynen |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates - add global derived metrics config directory and pmchart 'Iostat' view, Mark Goodwin |
|---|---|
| Next by Date: | Re: [PATCH] initial pass at fixing zbxpcp.so for Zabbix v3, Marko Myllynen |
| Previous by Thread: | Re: [pcp] PMDA Metrics Limit, Nathan Scott |
| Next by Thread: | Re: [pcp] PMDA Metrics Limit, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |