Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Cockpit does not provide a way to configure SNMP
There should be a way to configure authorization for SNMP (v3 at least, but probably also v2), which should include user (and community if v2) password/account creation.
This should be a high level API which takes care to perform the necessary platform tasks (service restarts if needed).
Comment 2Fedora Admin XMLRPC Client
2016-10-20 12:10:37 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Peter left, reassigning to default bug subscriber (me).
"Configure SNMP" is way too generic here, as SNMP is just a protocol that has dozens (or more) possible applications (from performance monitoring to remote printer discovery). So this requires specifying some concrete use cases, which can then be designed and implemented.
Do you have some requirements there? You referred to the RHEL 6 documentation about performance monitoring, and this seems to cover the basics:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/sect-system_monitoring_tools-net-snmp-retrieving. However, cockpit already provides a lot of these (CPU, memory) through PCP, storage is covered on the "Storage" page (cockpit-storaged), and "listing of RPM database" doesn't appear to be (1) closely related to SNMP, and (2) rather unwieldy to consume; e. g. cockpit already has a "Software Updates" page which shows available updates (which is generally the much more interesting part that requires attention). You also mentioned "password/account creation", but if that's referring to standard Unix accounts, this is also already present in Cockpit.
Thanks!
P.S. Also, help from domain experts is greatly appreciated! This doesn't have to live in the cockpit git repo/packages, the idea is that such domain specific web UIs can and should be maintained by whoever also develops the corresponding service.
Hey Martin -
Basically what we're looking for is sane defaults.
It is not sufficient that these metrics are available in cockpit, since those cannot be easily consumed by external tooling.
SNMP maintains its own auth (community/public in v2, separate users with finer grained ACLs in v3)
We are not expecting cockpit to become a full blown SNMP consumer. What is desired is a way to configure v2/v3 authorization so MIBs can be walked by clients
Effectively similar to https://access.redhat.com/solutions/17815