From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Change to collectd.conf and collect.custom
Date: Thu, 26 Jan 2023 14:34:31 +0000 [thread overview]
Message-ID: <71323DDC-AC2D-4590-8468-7C4A6EA17733@ipfire.org> (raw)
In-Reply-To: <23C86CDC-6C30-4940-B263-37E2EC06007E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4350 bytes --]
Hello Jon,
Hmm, but do you think they are essential for troubleshooting?
Cannot “htop” tell you exactly the same?
Best,
-Michael
> On 21 Jan 2023, at 17:26, jon <jon.murphy(a)ipfire.org> wrote:
>
> Hello!
>
>
>> On Jan 20, 2023, at 10:19 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>
>> Hello,
>>
>> Can I jump in and ask what you think the purpose of this graph is?
>
> For me it is mostly to troubleshoot. When I was experimenting with pmacct I would watch the Graphs.
>
> FYI - My Graphs are different since I was experiment with the RRD colors.
>
> <Screen Shot 2023-01-21 at 11.20.47 AM.png>
>
>>
>> I have no idea what they should tell me. Can we not get rid of them entirely?
>
> I’d like to keep them but it honestly does not matter…
>
>>
>> I believe the sole reason why those graphs exist is because collectd *can* collect this kind of data. But I have never looked at them and realised like “hey, this does not look right”…
>>
>> -Michael
>>
>>> On 17 Jan 2023, at 18:34, jon <jon.murphy(a)ipfire.org> wrote:
>>>
>>> Hello!
>>>
>>>> On Jan 17, 2023, at 7:50 AM, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>> good idea.
>>>> Why not put these 'addon' definitions into a file /etc/collectd.addons ?
>>>
>>> Ha! That was my first experiment!
>>>
>>> jon(a)deb11HPZ:~/dev/ipfire-2.x$ cat config/collectd/collectd.addon
>>> # Use this file to add add-on processes collectd
>>>
>>> <Plugin processes>
>>> Process "smbd"
>>> Process "nmbd"
>>> Process "squidguard"
>>> Process "qemu"
>>> Process "mpd"
>>> </Plugin>
>>> jon(a)deb11HPZ:~/dev/ipfire-2.x$
>>>
>>> I was worried it might cause confusion by adding one more include file.
>>>
>>>> One problem rermains. services.cgi displays all existent collectd RRDs. Therefore these should be deleted in case of uninstallation of a addon.
>>>
>>> I did see the delete issue but I am not sure how to clean-up the old RRDs.
>>>
>>> There is a cron to clean-up year old RRDs:
>>>
>>> [root(a)ipfire ~] # fcrontab -l | grep -i rrd
>>> 2023-01-17 11:58:14 INFO listing root's fcrontab
>>> # Cleanup the collectd RRD (graphs)
>>> %weekly * * /bin/find /var/log/rrd -mtime +365 -type f -name '*.rrd' -delete -o -type d -empty -delete
>>> [root(a)ipfire ~] #
>>>
>>> I can easily create
>>> /bin/find /var/log/rrd/collectd/localhost/processes* -mtime 1 -type f -name '*.rrd'
>>>
>>> But this type of clean-up seems too hacked...
>>>
>>>
>>>>
>>>> Regards,
>>>> Bernhard
>>>>
>>>> Am 17.01.2023 um 05:10 schrieb jon:
>>>>> All,
>>>>> I’d like to make a change to the `/etc/collectd.conf` to remove a few monitored processes. The items appear in the <Plugin processes> section of the config file. And the processes appear at the bottom of the https://ipfire.localdomain:444/cgi-bin/services.cgi WebGUI page.
>>>>> Why you ask? Mostly because smbd, nmbd, squidguard, qemu, or mpd are not used (at least by me!). And so the users of those items are not left out, I’d like to move those items to a `collect.custom`.
>>>>> So overall idea is the core processes would be in `collectd.conf` file. And the add-on processes will be in `collect.custom`.
>>>>> This is a snip of the plugin process section of the `collectd.conf` file:
>>>>> ```
>>>>> <Plugin processes> <Plugin processes>
>>>>> Process “sshd" to Process "sshd"
>>>>> Process “smbd" this Process "squid"
>>>>> Process “nmbd” ---> Process "charon"
>>>>> Process "squid" Process "openvpn"
>>>>> Process “squidguard" </Plugin>
>>>>> Process “charon"
>>>>> Process “openvpn"
>>>>> Process "qemu"
>>>>> Process "mpd"
>>>>> </Plugin>
>>>>> ```
>>>>> The items removed from the `collectd.conf` file would move to `collect.custom`.
>>>>> <Plugin processes>
>>>>> Process "smbd"
>>>>> Process "nmbd"
>>>>> Process "squidguard"
>>>>> Process "qemu"
>>>>> Process "mpd"
>>>>> </Plugin>
>>>>> But the problem is I don’t want to overwrite the `/etc/collectd.custom` file incase an admin has modified it for their own use.
>>>>> The big question
>>>>> ================
>>>>> So how do I change the `collectd.custom` file in `ipfire-2.x/config/collectd` AND not overwrite the admin’s `/etc/collectd.custom` file?
>>>
>>
>
next parent reply other threads:[~2023-01-26 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23C86CDC-6C30-4940-B263-37E2EC06007E@ipfire.org>
2023-01-26 14:34 ` Michael Tremer [this message]
2023-01-26 15:25 ` Bernhard Bitsch
[not found] <25DFEBB1-D081-4B3C-8F6B-8A12C93A5C59@ipfire.org>
2023-01-20 16:19 ` Michael Tremer
2023-01-17 4:10 jon
2023-01-17 13:50 ` Bernhard Bitsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71323DDC-AC2D-4590-8468-7C4A6EA17733@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox