Groundwork rrd file not created

The data you need can be collected with the above procedure. Once you are generating the debug info, you can analyze it yourself. There are several types of entries in the debug log, but the typical entry for processing performance data for a service on a host looks like this:.

New entry not added. Note that this can be parsed with the Status Text Regex in Configuration - Performance to extract perf data e. This is the command that, if typed at a command line and routed to a. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related 1. Hot Network Questions. Adjustment of other parameters is optional, and should be done only if necessary. Refer to the GDMA documentation for explanations of the parameters in this file that control the spooler. There is no special maintenance for this feature. However, keeping track of performance on the GroundWork server is a good idea. If things seem to be slow, it may be a good idea to consider adjusting the heartbeat frequency to a less frequent interval. If you do so, ensure that any freshness checks on the GroundWork server hosts and services are synchronized with this interval.

Freshness intervals for passive checks should always be kept longer than the update cycles to avoid false positive results. Quick Search. Figure: Polling Servers In this scenario, the polling servers are doing all the active checks, and are collecting performance data. It must be resolvable from the parent server.

DO NOT remove the following section as it is required for operation. The spooler is actually a separate method of sending results for the NSCA method. You probably do not want to use both methods to send results to the same server. You can also send results to one server with NSCA and another with the spooler.

It's up to you. Generally, though, if you use the spooler, you will be disabling the NSCA method. Highly recommended, for efficiency.

Everything before the pipe operator Nagios considers to be status text, and is inserted in the status field of the Nagios and Status user interface. Everything before the pipe operator is status text and everything after it is formatted performance data. It reads from the service-perfdata. For each service check result it finds there, it does a database lookup of the service name in the performanceconfig table in the Monarch database. This table indexed by service name contains the unique RRD create commands and RRD update commands appropriate for the data returned by that particular plugin.

Those RRDs are read by the CGI specified in the performanceconfig entry these can be customized and then presented for viewing in the Status application. There is also a graphical user interface on the performanceconfig table, so the operator can adjust RRD create and update strings, or even specify which CGI will be used to graph them.

These tables are used by the Performance application to locate the various RRDs in the system. Performance is able to read in the data from multiple RRDs and consolidate that data into a single graph. To increase debug logging, edit perfdata. This occurs automatically the next time Nagios is restarted which happens during a Commit , or you can force it manually with the following command:.

Figure: Performance process data flow. You may create these in any manner you like, but ensure that the RRD Create Command entry is of the following form:. Use the following steps to ensure that the performance handler is working as expected. To debug a performance handler problem, look at the log results for your Service entry. Check the following steps:. Definitions in the performance configuration database may be exported to transfer to another system or for backup purposes.

To export the entire performance configuration database, select the Export All button at the top of the Performance Configuration utility page. To export a specific performance configuration entry, select the Export button for that entry. This is an XML file describing each field entry. A sample file is shown below. To import an exported file, execute the following script which will read the exported XML file and insert the entry into the performance configuration database.

Quick Search.