kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/net-mgmt/zenpack-interfacegraphs/Makefile

23 lines
613 B
Makefile
Raw Normal View History

- Add New USES macro to handle support for Zenoss ports and Zenpacks: USES= zenoss -trim historical headers Convert net-mgmt/zenpack family to new framework PR: 176723 Approved by: maintainer timeout ( 14 days )
2013-03-20 07:28:43 +01:00
# Created by: Zenoss <zenoss@experts-exchange.com>
When troubleshooting network issues, it can be very useful to have all the interface graphs for a device on the same screen. This helps with spotting trends, or tracing where traffic is flowing through a switch or router. The only way to natively achieve this with Zenoss is to create a graph or multi-graph report for every network device manually, which can be a chore if you have more than a few network devices. This ZenPack provides a new link on the left side of a device detail view called "Interface Graphs" - this view shows the graphs for all of the network interfaces on the device in one place, allowing for fast spotting of issues or traffic flows. Both the interface name and the description (if any) are used to title the graphs to aid with identification. Note that with stacked switches, you can end up with a very large number of graphs on the page, so tuning this slightly via the configuration properties below could be a good idea in these situations. WWW: http://community.zenoss.org/docs/DOC-10226 PR: ports/157503 Submitted by: Zenoss <zenoss@experts-exchange.com>
2011-10-27 16:36:31 +02:00
# $FreeBSD$
PORTNAME= InterfaceGraphs
PORTVERSION= 1.0
CATEGORIES= net-mgmt
- Fix fetch error by updating MASTER_SITES and DISTFILE PR: ports/164107 Submitted by: Anthony Garcia <agarcia at experts-exchange.com> Approved by: crees,rene (mentors, implicit)
2012-01-14 02:21:16 +01:00
MASTER_SITES= https://github.com/zenoss/${ZPACKPREFIX}${PORTNAME}/tarball/master/
DISTNAME= zenoss-${ZPACKPREFIX}${PORTNAME}-${TAG}
When troubleshooting network issues, it can be very useful to have all the interface graphs for a device on the same screen. This helps with spotting trends, or tracing where traffic is flowing through a switch or router. The only way to natively achieve this with Zenoss is to create a graph or multi-graph report for every network device manually, which can be a chore if you have more than a few network devices. This ZenPack provides a new link on the left side of a device detail view called "Interface Graphs" - this view shows the graphs for all of the network interfaces on the device in one place, allowing for fast spotting of issues or traffic flows. Both the interface name and the description (if any) are used to title the graphs to aid with identification. Note that with stacked switches, you can end up with a very large number of graphs on the page, so tuning this slightly via the configuration properties below could be a good idea in these situations. WWW: http://community.zenoss.org/docs/DOC-10226 PR: ports/157503 Submitted by: Zenoss <zenoss@experts-exchange.com>
2011-10-27 16:36:31 +02:00
MAINTAINER= zenoss@experts-exchange.com
COMMENT= Provides a link that graphs all network interfaces for a device
- remove pkg-plist in favor of PLIST_FILES and PLIST_DIRS
2012-06-18 23:59:45 +02:00
PLIST_FILES= zenoss/ZenPack/${ZPACK}
PLIST_DIRS= zenoss/ZenPack
- Add New USES macro to handle support for Zenoss ports and Zenpacks: USES= zenoss -trim historical headers Convert net-mgmt/zenpack family to new framework PR: 176723 Approved by: maintainer timeout ( 14 days )
2013-03-20 07:28:43 +01:00
USES= zenoss
- remove pkg-plist in favor of PLIST_FILES and PLIST_DIRS
2012-06-18 23:59:45 +02:00
When troubleshooting network issues, it can be very useful to have all the interface graphs for a device on the same screen. This helps with spotting trends, or tracing where traffic is flowing through a switch or router. The only way to natively achieve this with Zenoss is to create a graph or multi-graph report for every network device manually, which can be a chore if you have more than a few network devices. This ZenPack provides a new link on the left side of a device detail view called "Interface Graphs" - this view shows the graphs for all of the network interfaces on the device in one place, allowing for fast spotting of issues or traffic flows. Both the interface name and the description (if any) are used to title the graphs to aid with identification. Note that with stacked switches, you can end up with a very large number of graphs on the page, so tuning this slightly via the configuration properties below could be a good idea in these situations. WWW: http://community.zenoss.org/docs/DOC-10226 PR: ports/157503 Submitted by: Zenoss <zenoss@experts-exchange.com>
2011-10-27 16:36:31 +02:00
ZPACKGROUP= community
ZPACKPREFIX= ZenPacks.community.
- Fix fetch error by updating MASTER_SITES and DISTFILE PR: ports/164107 Submitted by: Anthony Garcia <agarcia at experts-exchange.com> Approved by: crees,rene (mentors, implicit)
2012-01-14 02:21:16 +01:00
WRKSRC= ${WRKDIR}/zenoss-${ZPACKPREFIX}${PORTNAME}-${TAG}
TAG= 7ed2d7d
When troubleshooting network issues, it can be very useful to have all the interface graphs for a device on the same screen. This helps with spotting trends, or tracing where traffic is flowing through a switch or router. The only way to natively achieve this with Zenoss is to create a graph or multi-graph report for every network device manually, which can be a chore if you have more than a few network devices. This ZenPack provides a new link on the left side of a device detail view called "Interface Graphs" - this view shows the graphs for all of the network interfaces on the device in one place, allowing for fast spotting of issues or traffic flows. Both the interface name and the description (if any) are used to title the graphs to aid with identification. Note that with stacked switches, you can end up with a very large number of graphs on the page, so tuning this slightly via the configuration properties below could be a good idea in these situations. WWW: http://community.zenoss.org/docs/DOC-10226 PR: ports/157503 Submitted by: Zenoss <zenoss@experts-exchange.com>
2011-10-27 16:36:31 +02:00
- Add New USES macro to handle support for Zenoss ports and Zenpacks: USES= zenoss -trim historical headers Convert net-mgmt/zenpack family to new framework PR: 176723 Approved by: maintainer timeout ( 14 days )
2013-03-20 07:28:43 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink