Plugin Architecture v2.0 for Cacti v0.8.7b

Support for the Plugin Architecture

Moderators: Moderators, Developers

Post Reply
User avatar
Cacti Guru User
Posts: 2326
Joined: Fri Sep 19, 2003 8:36 am
Location: Sophia-Antipolis, France

Plugin Architecture v2.0 for Cacti v0.8.7b

#1 Post by fmangeant » Wed Feb 13, 2008 2:56 am

Posted by Jimmy on 02/12/08 13:11:32 at
Today with the release of Cacti v0.8.7b, I have released the latest Plugin Architecture. This version adds a few extra hooks and includes the newest architecture design with some crucial changes.

First, this version requires you to import a SQL file into your Cacti databse (pa.sql). This adds required tables and entries for the Plugin Architecture. This version is backwards compatible with the old PA and plugin, but opens the plugins to be able to move to the new architecture and API functions. Documents on how to migrate your plugins to the new plugin architecture will be available soon, but all your plugins should still work until then.
[color=green]HOWTOs[/color] :
[list][*][url=]Install and configure the Net-SNMP agent for Unix[/url]
[*][url=]Install and configure the Net-SNMP agent for Windows[/url]
[*][url=]Graph multiple servers using an SNMP proxy[/url][/list]
[color=green]Templates[/color] :
[list][*][url=]Multiple CPU usage for Linux[/url]
[*][url=]Memory & swap usage for Unix[/url][/list][/size]

Matt John
Posts: 1
Joined: Sat Feb 20, 2010 1:12 am

#2 Post by Matt John » Sat Feb 20, 2010 1:20 am

The host application provides services which the plug-in can use, including a way for plug-ins to register themselves with the host application and a protocol for the exchange of data with plug-ins. Plug-ins depend on the services provided by the host application and do not usually work by themselves. Conversely, the host application operates independently of the plug-ins, making it possible for end-users to add and update plug-ins dynamically without needing to make changes to the host application.

Open application programming interfaces (APIs) provide a standard interface, allowing third parties to create plug-ins that interact with the host application. A stable API allows third-party plug-ins to continue to function as the original version changes and to extend the life-cycle of obsolete applications. The Adobe Photoshop and After Effects plug-in APIs have become a standard[citation needed] and competing applications such as Corel Paint Shop Pro have adopted them to some extent. Other examples of such APIs include Audio Units and VST.

Games and productivity applications often use plug-in architectures which allow original and third-party publishers to add functionality.

The Microsoft Flight Simulator series has become well-known for its aircraft add-ons.

Outside software, a network switch may ship with an unoccupied but non-standard port to accommodate various optional physical-layer connectors.

Outside software again, manufacturers can use plug-ins to create vendor lock-in by limiting upgrade options solely to those available from or endorsed by the original manufacturer. IBM's Micro Channel Architecture, technically superior to Industry Standard Architecture as a way to add components to IBM PCs, largely failed to gain wide support due to the difficulty in getting certification for third-party devices.


Matt John

Post Reply