Mostly related to SNMP and mostly simple (I think):
1) Default Community String for All Sources
2) Ability to Use Default Community String for Any Data Source
3) Ability to Change Community easily if 1 & 2 are Not Available
- I think this all goes with the profiling for device types -
4) Ability to Name the RRD File Name and Interface by the HostName & Interface Number Instead of "traf" & Interface IP & Interface Number. This would help GREATLY.
5) Subdirs by Host!!!
Keep up the good work!
Larry
>> Some Simple One's I Think <<
Moderators: Developers, Moderators
Hi Larry.
I can easily see the need to change the default string from 'public' to whatever your company uses. Changing everything from one string to another string is a simple sql query - "UPDATE string_table SET string='blah' WHERE string = 'another_thing'".
The needs for changing the community string change drastically from network to network. My company's network uses localized strings right now and we'll be moving to SNMP v3 with usernames and passwords shortly. We plan on supporting SNMP v3 in the next revision, btw.
The solution that I'm leaning towards is to not manage that inside of Cacti at all. I think we've decided to put a generic 'external_id' field in the hosts table that could be set to that host's ID in your company's topology database, whatever that may be. The idea is that you can write whatever scripts you want to make changes to the Cacti data based on your topology because you've got a relationship between those two sets of data.
One thing that's very important is that Cacti keep a clear vision of its purpose. It's not a topology management tool, it's a graphing and reporting tool. I'm open to building in an interface to change SNMP auth info but it's got to be flexible enough to be useful to everybody.
Regarding your 4th point, do you feel that it's important to have human-readable filenames for the rrd files? There are reasons for it and against but I'd like to hear some opinions and reasons.
Your 5th point - yep. No question. Absolutely.
Rob.
I can easily see the need to change the default string from 'public' to whatever your company uses. Changing everything from one string to another string is a simple sql query - "UPDATE string_table SET string='blah' WHERE string = 'another_thing'".
The needs for changing the community string change drastically from network to network. My company's network uses localized strings right now and we'll be moving to SNMP v3 with usernames and passwords shortly. We plan on supporting SNMP v3 in the next revision, btw.
The solution that I'm leaning towards is to not manage that inside of Cacti at all. I think we've decided to put a generic 'external_id' field in the hosts table that could be set to that host's ID in your company's topology database, whatever that may be. The idea is that you can write whatever scripts you want to make changes to the Cacti data based on your topology because you've got a relationship between those two sets of data.
One thing that's very important is that Cacti keep a clear vision of its purpose. It's not a topology management tool, it's a graphing and reporting tool. I'm open to building in an interface to change SNMP auth info but it's got to be flexible enough to be useful to everybody.
Regarding your 4th point, do you feel that it's important to have human-readable filenames for the rrd files? There are reasons for it and against but I'd like to hear some opinions and reasons.
Your 5th point - yep. No question. Absolutely.
Rob.
Who is online
Users browsing this forum: No registered users and 2 guests