They will specify, which Data Sources defined by some Data Template should be displayed on the Graph. Please click Add as shown on the last image:. Now click Save to see the resulting image below. Next, we have to add a Legend in order for people viewing the Graph in the future to obtain numeric data about the Graph contents.
We will create a very simple one, though Graph Legends can be a very complex subject. To add the Graph Legend, simply press the Add button again and fill out the Graph Item as shown in the image below. You should note that for this second Graph Item , it remembered the previous Data Source. The polling script is loosely based off of the multi-protocol realtime volume statistics script that I created some time ago.
Download the updated template and script s here. These are especially useful for volumes that have multiple types of access happening. Because it is an indexed script query, you can select volumes to have each type of graph created for. This makes it easy to select the volumes that you want to see, for instance, NFS latency using the standard list of objects that Cacti provides.
After placing the na-cacti-volume-stats. Anyway, that irritation aside, make sure that the permissions to the file are tightened such that only the Cacti user can access it, which helps to mitigate the security risk. The second part of mitigation is to ensure that the user which connects and polls the NetApp has limited access.
That should get you started. If you have any issues with the script or templates, please let me know in the comments. You can monitor LUN statistics using a script very similar to this.
I will work on modifying the script and making some templates. Hopefully I can get it posted sometime soon! Andrew, I had a problem when I imported the cacti template, I had a lot of unmet dependencies.
I went through and tried to add the other templates that were referenced yet the same happened when I re imported. Is there something I am missing? The templates were exported from an 0. I am at VMworld this week, when I return I will re export the templates from the newest version of Cacti. If you have a list of the errors that may prove useful as well.
I went through and matched up all of the dependencies in the data queries, exported the template and reimported it and it looks like it is good to go. Greg: What was the procedure you used to match up the dependencies? Template works with this version too, or must i upgrade Cacti?
Auto Scale Enable auto scale for the graph. This option must be check to use the next two options. Auto Scale Options Choose whether you would like to use --alt-autoscale ignoring given limits , --alt-autoscale-max accepting a lower limit , --alt-autoscale-min accepting an upper limit. Logarithmic Scaling Choose if you want logarithmic y-axis scaling. But for logarithmic graphs, exponential notation is default.
Choose if you want logarithmic y-axis scaling and scientific units. Rigid Boundaries Mode From the RRDtool manual "Normally rrdgraph will automatically expand the lower and upper limit if the graph contains a value outside the valid range.
With this option you can disable this behavior". Auto Padding If you have ever created RRDtool based graphs manually, you may have realized how annoying it can be to get text to line up properly.
With this option Cacti will do its best to make the columns on your graph legend line up. This option works best when your graph legend has a consistent number of columns. Upper Limit The maximum value that will be displayed on the y-axis. This value is ignored is auto-scaling is turned on.
Lower Limit The minimum value that will be displayed on the y-axis. Base Value Whether you want to base the y-axis labels on or This field will typically be set to for memory and for traffic measurements. Unit Grid Value Sets the unit value for the y-axis --y-grid.
You should probably keep the unit short as to keep it readable. Valid values for this field are between and For example, you could use 3 to display everything in 'k' kilo or -6 to display everything in 'u' micro.
Vertical Label The text to print on the left edge of the graph. Usually is the units the data on the graph is measured in. Auto-scaling Options Explained Relative to Auto-scale Options, the RRDtool graph manual says: Limits [-u --upper-limit value] [-l --lower-limit value] [-r --rigid] By default the graph will be auto-scaling so that it will adjust the y-axis to the range of the data.
You can change this behavior by explicitly setting the limits. The displayed y-axis will then range at least from lower-limit to upper-limit. Auto-scaling will still permit those boundaries to be stretched unless the rigid option is set.
This option calculates the minimum and maximum y-axis from the actual minimum and maximum data values. Our example would display slightly less than " The maximum value, if not defined on the command line, will be 0. This option can be useful when graphing router traffic when the WAN line uses compression, and thus the throughput may be higher than the WAN line speed.
The minimum value, if not defined on the command line, will be 0. Keep in mind that not all graph items have a data source. Color Depending on the graph item type, you can select a color for the graph item.
This option is not available with RRDtool Graph Item Type This field is important because it defines what kind of graph item this is. Consolidation Function This tells RRDtool which consolidation function to use when representing this data on the graph. Check out the CDEF section of the manual for more information. Text Format You can enter text to be displayed on the legend here.
Hard Return Check this box to force graph items onto the next line. There are various fields that must be filled in for every graph item input: Table Description Optional This description will be displayed on the Graph edit page of any Graph using this Graph Template if specified. Field Type You must choose the field that you are going to associate with one or more Graph Item.
When the user specifies a value for the field, it will be applied to all of the items you select here. Applying Graph Templates to Graphs Applying a Graph Template to an existing Graph is a very simple process, though very uncommon in a modern Cacti install. Import Templates Assume, you're searching for a specific set of templates to monitor a special type of device.
Export Templates Now that you know how to import, you may want to know in which way to export as well. Copyright c The Cacti Group. The name of the Data Source that will be created by using this Template. Here is where you tell Cacti how it is supposed to fetch data for this Data Source.
Those graphs are available here:. As I get time which is rare I plan on adding additional graphs, when I do, I will post them here. I would like to get and graph ASIS information, WAFL stats, and space information raw, formatted, usable, allocated, overhead for the filer as a whole. If anyone has, or knows where to find, these graphs, please let me know! Shows a detailed breakdown of the different types of CIFS operations that occur.
These templates show NFS version 3 operations and latency for the server as a whole. After importing the template, when you create the graphs for your filer it will ask you for the username and password to connect via the SDK. They can be downloaded here. The FCP template and graphs work the same as the other protocols: drop the perl script in your scripts directory, make sure it knows where the SDK files are, and import the template.
First off, thanks for all of your work on this.
0コメント