Foglight NMS-> Foglight 5 integration cartridge?

Similar Questions

• Foglight 4 integration Issos

  Hi experts:

  I know that foglight 4 was support. In my case, there is a large customer used Foglight 4 for a long time. So can not install 5 Foglight immediately.

  But unfortunately, the customer will have integration of foglight 4 to another system.

  We need to the docs on API or Foglight 4 docs.

  DB information managed (oacle DB2 SQL Server) and managed Middleware (weblogic, websphere MQ) is necessary.

  Such as:

  DB:

  used tablespace, Redo log space, CMS and so on

  Middleware:

  Wating JVM, JMS, JDBC, and so on

  We would like to know how integrating these Foglight 4 imforation.

  Where can I find documentation?

  Thank you very much!

  You can pull down the documentation foglight 4 from the site of Dell support as a starting point.

  David Mendoza

  Foglight Consultant

• Foglight and integration Sitescope

  Have anyone tried incorporating foglight sitescope?

  I would do it I push foglight alarm for use in sitescope. Is there any documentation for it?

  Thank you

  Research online it looks like Sitescope has a trap SNMP monitor, you are trying to send SNMP traps from Foglight

  http://en.community.Dell.com/TechCenter/performance-monitoring/Foglight-administrators/w/Admins-wiki/5567.event-driven-rules-SNMP-forward

  The article talks about general SNMP forward, but I hope it helps.

  Golan

• Foglight FMS server

  I tried to see how to get the FMS of Foglight Server as it doesn't seem to be a product, what I am hoping is that, if I can get the FMS of Foglight Server I can fill a gap where I can get my Foglight NMS alerts in my current environment of SCOM.  I don't want to give up that I bought a few months ago to go to another product that has the integration of SCOM.

  Any info that it's possible would be greatly appreciated.

  Thank you

  Hi Greg -.

  (FMS) Foglight Management Server is indeed point principal of aggregation and integration of the Foglight framework. You can start the process of obtaining an administration here Server trial download: http://www.quest.com/foglight or by registering at support.quest.com.

  A high level overview you will need to do is:

  1. to organize a trial of the Foglight Management Server (you may want to work with our sales or pre-sales teams to get this set up)

  2. Once you have a FMS running, you will integrate your Foglight NMS information into the FMS using Foglight NMS integration cartridge.

  3. in addition to the cartridge of NMS integration, you'll need an additional integration Foglight cartridge - cartridge allows you to integrate with a variety of third parties, including SCOM FMS systems. There is a video on the SCOM integration that you can find here:

  http://www.quest.com/TV/all-videos/959824273001/vFoglight---SCOM-integration/video/

  Note that the video was made with vFoglight (which is simply the FMS put in place with a cartridge of monitoring VMWare), but also long as you have the Foglight cartridge for installed integrations, the process must be the same.

  I hope this helps.

  Robert Statsinger

• SNMP Trap to order Action Script in Foglight rule

  Hello everyone,

  I need to make a rule that runs a script via the Action control when a SNMP Trap has arrived. I create this?

  The script is required for integration with my SMS server.

  Best regards

  There is a similar example in our documentation, see if that helps

  http://eDOCS.quest.com/Foglight/5611/doc/cartridge-integration/IntegrationCartridge/UnderstandingWorkflow.5.php#404739

  Golan

• Possible to integrate environmental Foglight existing with the purchase of a new vFoglight?

  We have used Foglight and JavaEE cartridges for years and are now looking to expand our use of Foglight to include vFoglight and cartridges of the database as well. I was looking around for more information on how to integrate our existing with the new monitoring vFoglight Foglight Management Server, because it seems to be a distinct type FMS console.

  I came across this old thread: http://en.community.dell.com/techcenter/virtualization/infrastructure/f/4826/t/19550426#10367

  Is it really as simple as updating the license file to get the vFoglight features in our existing FMS?

  Yes, you add the cartridges additional thanks to licensed and ready to start the deployment.

  Depending on the size of your environment, may want to be careful about the scalability of your current hardware, etc..

• Tomcat tracked using Foglight 5.6.4

  Hi all

  We have a new requirement to monitor Tomcat applications. Searched the forums and support for the corresponding cartridge Tomcat but the Foglight sites 5.6.4 can't stand the cartridge it seems. In addition, we have an option to monitor using Java EE cartridge using the Deployment Manager agent Java. In this, we can define the configuration settings in the properties of the Agent and the monitor.

  Please let me know what version of Tomcat supports of foglight and concept of using node manager and without Node manager in servers and the level of compatibility with the Java EE officer and also the requirements for the monitoring of tomcat applications.

  Share links and knowledge in this regard.

  Thank you best regards &,.

  Guenoun.

  Hello

  Tomcat server is covered by the Java monitoring.

  Platforms supported are in the e-docs

  http://eDOCS.quest.com/

  then choosing the right version of Foglight

  

  Then choose the track the performance of Java applications and .NET applications

  

  And through the link of platforms supported in the (5th line line in the image above).

  It comes to the list of versions supported complete Tomcat for Foglight 5.6.4 of the java agent that makes bytecode instrumentation (direct link for tomact).

  http://eDOCS.quest.com/Foglight/564/doc/cartridge-app/JavaEECartridge-requirements/Supported_Application_Servers.013.6.php#444031

  Tomcat servers

  Server	Operating system	Architecture	JVM
  Tomcat 7.0. [6-25]	IBM AIX 5.3, 6.1, 7.1	PowerPC	IBM 1.6 JRockit 1.6 OpenJDK 1.6, 1.71 Oracle Java SE 1.6, 1.7
  	Novell SUSE Linux Enterprise Server 9, 10, 11	IA32, x 86-64
  	Oracle Enterprise Linux 5	IA32, x 86-64
  	Red Hat Enterprise Linux AS/ARE/WS 4, 5, 6	IA32, x 86-64
  	Oracle Solaris 8, 9, 10	SPARC
  	Oracle Solaris 10	x 86-64
  	Windows XP SP1 +, Server 2003, Server 2008	IA32, x 86-64
  	Windows Server 2008 R2	x 86-64
  Tomcat 6.0 [0-35]	IBM AIX 5.3, 6.1, 7.1	PowerPC	IBM, 1.5, 1.6 JRockit 1.5, 1.6 OpenJDK1 1.6, 1.7 Oracle Java 1.5, 1.6, 1.7 SE
  	Novell SUSE Linux Enterprise Server 9, 10, 11	IA32, x 86-64
  	Oracle Enterprise Linux 5	IA32, x 86-64
  	Red Hat Enterprise Linux AS/ARE/WS 4, 5	IA32, x 86-64
  	Oracle Solaris 8, 9, 10	SPARC
  	Oracle Solaris 10	x 86-64
  	Windows XP SP1 +, Server 2003, Server 2008	IA32, x 86-64
  	Windows Server 2008 R2	x 86-64
  Tomcat 5.5 [0-35]	IBM AIX 5.3, 6.1, 7.1	PowerPC	IBM, 1.5, 1.6 JRockit 1.5, 1.6 OpenJDK1 1.6 Oracle Java SE, 1.5, 1.6
  	Novell SUSE Linux Enterprise Server 9, 10, 11	IA32, x 86-64
  	Oracle Enterprise Linux 5	IA32, x 86-64
  	Red Hat Enterprise Linux AS/ARE/WS 4, 5	IA32, x 86-64
  	Oracle Solaris 8, 9, 10	SPARC
  	Oracle Solaris 10	x 86-64
  	Windows XP SP1 +, Server 2003, Server 2008	IA32, x 86-64

  Windows Server 2008 R2

  x 86-64

  There are more options for follow-up.

  On a supported JDK, you can use an agent X (running as generic agent Java java agent) which shows the information request, traces of application and information of JVM

  http://eDOCS.quest.com/Foglight/564/doc/cartridge-app/JavaEECartridge-requirements/Supported_Application_Servers.013.7.php#432033

  X-Agent application servers

  Server	Operating system	Architecture	IV.
  X Agent	HP - UX 11i v1	parisc	1.4.2, 1.5, 1.6 HP IBM 1.4.2, 1.5, 1.6 JRockit 1.4.2, 1.5, 1.6 OpenJDK 1.6, 1.71 Oracle Java SE 1.4.2, 1.5, 1.6, 1.7
  	HP - UX 11i v2	parisc, ia64
  	HP - UX 11i v3	IA64
  	IBM AIX 5.3, 6.1, 7.1	PowerPC
  	Novell SUSE Linux Enterprise Server 9, 10, 11	IA32, x 86-64
  	Oracle Enterprise Linux 5	IA32, x 86-64
  	Red Hat Enterprise Linux AS/ARE/WS 4, 5	IA32, x 86-64
  	Oracle Solaris 8, 9, 10	SPARC
  	Oracle Solaris 10	x 86-64
  	Windows XP SP1 +, Server 2003, Server 2008	IA32, x 86-64
  	Windows Server 2008 R2	x 86-64

  If you are using JDK 1.5.x or higher, you can use JMX agent to get data only JMX

  http://eDOCS.quest.com/Foglight/564/doc/cartridge-app/JMXCartridge/index.php

  As always, you can add followed with agents of the utility (webmon to monitor a web page, appmon to monitor a process, logfilter for monitor logs)ttp://en.community.dell.com/techcenter/performance-monitoring/foglight-administrators/w/admins-wiki/5646.monitoring-application-availability-using-foglight-utility-agents h

  I hope this helps.

  Golan Shem-Tov

• Functions in the rules of Foglight

  Hello

  I tried to find the definitions of the custom functions used in the rules, but have failed so far. Can someone guide me in the right direction?

  For example: DBO - redo wait Contention
  Function used: DBWC_SingleInstanceOnlyRuleFilter (scope, "DBO - Redo Wait argument", "3", status);

  I need to understand that, in order to take advantage of the features within my rules as well as to better understand the existing rules.

  P.S. I'm aware of the use of the functions with WCF dashboards.

  Thanks in advance

  Hi Ashley.

  These types of features used in the Foglight rules are said to be "named scripts. They are different from the functions used in the WCF dashboards. They are often deployed in Foglight via a cartridge, especially when a rule provided by this cartridge uses the script. Once a named script is within Foglight, other rules may use it.

  You can't see the source code of a script within the Foglight user interface.  If you want to see the source for such a script, the best approach is to understand what Foglight cartridge, it was deployed in, then make a copy of the file of the cartridge and crack open the copy with WinZip or WinRAR - you will probably be able to locate the source of the script here in a XML political oversight.

  I hope this helps.

  Robert Statsinger

• Foglight for VMware - what alarm intercepts a low disk space?

  All,

  According to me, Miss me something here. Low disk space problems catches which alarms for virtual machines?

  Thank you

  -Daniel

  There are

  http://eDOCS.quest.com/Foglight/56/doc/cartridge/vFoglightCartridge/reference.59.3.php#582597

  Logical VMW Virtual Machine time lead estimated fill

  VMW Machine virtual logical drive use.

  

  Golan

• WebLogic integration - using startWebLogic.sh

  Hello

  I need to get some servers from Weblogic instrumented in our test environment and need help to better understand the methods of automatic integration.

  We start our Weblogic - (Version 10.3 on Solaris) servers using 3 custom scripts under the DOMAIN_HOME - startManagedArx.sh, startManagedDDSServer.sh and startManagedIntDDServer.sh

  These scripts call DOMAIN_HOME/startWebLogic.sh

  When I run the FMS integration to point to the startWebLogic.sh and provide the field, he joined under DOMAIN_HOME/bin scripts. He also created 2 backups of the original startWebLogic.sh under DOMAIN_HOME/bin.

  I have to manually copy these scripts to integration in the real startWebLogic.sh used under the DOMAIN_HOME? If I do, is there any necessary changes to the configuration of FMS? Can someone guide me on how to proceed?

  Also in order to restore this configuration are there additional proceedings other than re reinstating the original script for startWebLogic.sh.

  Just to be safe.

  Have the startweblogic directly under DOMAIN_HOME scripts are probably not standard, a default installation has some startup scripts under

  DOMAIN_HOME\bin\. Corresponds to the script in DOMAIN_HOME\startweblogic.sh a copy of the script in DOMAIN_HOME\bin\?

  My problem with the manual copy is that it leaves this as process semi automatic (without papers with room for error), I guess if the scripts DOMAIN_HOME and DOMAIN_HOME\bin are the same you can do technically (copy the script), it means simply that if there is someone else who needs to do that they can miss this non-standard step (not knowing what you know and what) you did).

  In the interests of maintaining the structure of default installation it could have better for your startup scripts customized to actually use DOMAIN_HOME\bin\startweblogic.sh instead of DOMAIN_HOME\startweblogic.sh (while they follow the location of weblogic standard installation script). BUT if there was a specific decision which required changes and the startweblogic under DOMAIN_HOME and DOMAIN_HOME\bin are the same, you can try to copy the new script or changed from DOMAIN_HOME\bin to DOMAIN_HOME and see if it works.

  Here, there is another alternative which is keeping installation and standardized instructions and making integration manual http://edocs.quest.com/foglight/5610/doc/Cartridge-APM/JavaEECartridge-install/ManuallyIntegrating.5.php#424838

  This way you are creating a generic configuration and then adding the lines manually to the startweblogic you use.

  What is the advantage of this way?  He is always in standard and always documented, this way if someone should follow your work, they can always read the documentation and follow a path standard and documented to do things.

  As far as roll back configuration, this is the reason why we have these backups - you can just rename (and then later remove) new or modified startweblogic.sh and rename the backup/original to be startweblogic.sh.

  I hope this helps.

  Golan

• The utility cartridge replacement

  Hey guys,.

  The utility cartridge inherited agent were replaced again? Can someone provide a link?

  WebMonitor specifically and AppMonitor.

  Thank you!

  -Daniel

  The new WebMonitor 5.6.10 came out with the Foglight 5.6.10 battery. Two notes of interest: (1), we accidentally used the same name as the legacy OS (WebMonitor, reasonably enough) basket. This upsets the FMS, if both are installed together. So, do not try it. :) We'll be fixing that by changing the new his name in the next Rev (2) the new agent currently cannot monitor resources https through a proxy, that will be fixed in a future release.

  An AppMonitor as feature is in the plans for the next major release of Infrastructure, alongside new NetMonitor and LogMonitor (replaces LogFilter). At the moment I think that all we need to add to the HostAgents for a characteristic AppMonitor is the ability to specify the process interesting in a secondary list of ASP and a rule as the rule of the availability of the process of the BONE wagon inherited, by http://edocs.quest.com/foglight/5610/doc/Cartridge/OSCartridge-ref/Rules.04.php#430311. If you would wait or need something else an AppMonitor replacement, it would be a great time to let me know. :)

  Post edited by: Stuart Hodgins

• "root password" Message on stdout during fglam start / / cartridge NIC package questions on Linux OS

  Jin

  that means when I call 'fglam d' and I can read

  "root password:"subsequently on stdout? "

  This output appears after the message "daemon for AgentManager process began."

  Foglight agent manager has been installed and started with a normal user.

  I'm confused because the FMS applications displays the content of the agent on this host

  and I saw no errors during startup.

  --

  Concerning

  Bernhard

  According to http://edocs.quest.com/foglight/563/files/CartridgeForOperatingSystems_554_ReleaseNotes_Revision1.html#FDOC-3124, sudo is required to collect metrics to use NIC to some kernel Linux NIC drivers.

  Information on activation, the agents and the Launcher safe to use sudo is available at: http://edocs.quest.com/foglight/563/doc/Cartridge/OSCartridge/SysAgent.21.2.php#401691

  Kind regards

  Brian Wheeldon

• Service monitoring on virtual machines in windows

  Hi people,

  We recently bought VFoglight and also NMS.how (with what I bought) if I monitor the status of windows services? -i.e. can I follow specific (or all automatic) services and warning of the they change order?  Is this doen via the infra cartridge as it would be easier than having to alos use a NMS agent on each server.

  All advice appreciated!

  Thanks in advance.

  Hey Davie,

  If you see this - http://edocs.quest.com/foglight/563/doc/Cartridge/InfrastructureCartridge/UsingTheCartridge.02.4.php

  You can see the agent properties different (accessible from the Administration-> the State of the Agent). Click on your WindowsAgent agents in the list and change the properties.

  The drop-down menu to "Collect measures of Service" has a few options for all, no or specified.

  The rule of "HostServiceRestart", generates an email if a monitored service is stopped and an agent is configured to restart. It is disabled by default.

  The rule "HostServices" generates an alarm and sends an email if a host service changes its status. If it changes to run anything else, it generates a warning alert.

  Hope that helps,

  -Darren

• Java EE is not enabled so that Websphere monitoring

  Hi all

  I got the following error while monitoring the monitoring of websphere. I gave everything but all the properties correctly by restarting webpshere startup scripts I am facing the below

  error:

  Attached the agent logs in your home reference and java path.

  

  

  Please help me in this regard.

  -Shiva

  Additional accessories:

  • Agent logs.log.zip
  • 
    JavaEE not enabled.jpg

  Shiva,

  To save time if it still does not recommend a case of pension to open as soon as possible so that they can work with you in your local time zone and a webex.

  To the extent where the script what you see that it resembles this AI a websphere integration is done for Caroline.

  We always work with 5.8.1 cartridge or have you you switch to 5.9.x?

  5.8.1 you can see the options in question

  http://eDOCS.quest.com/Foglight/565/doc/cartridge-app/JavaEECartridge-install/ConfigAppServers_JavaEE.018.3.php#416350

  The text that will show you almost looks like someone made integration agent node with 5.9.x, if that was the case that integration with a regular startup script should put text right running. There are also manual integration information that specifies the flags that are used

  http://eDOCS.quest.com/Foglight/5610/doc/cartridge-APM/JavaEECartridge-install/ManuallyIntegrating.6.php#425173

  Golan

• Java instrumentation - Weblogic

  Hello

  I just need some advice on the approach I should take for the Instrumentation of Java script below.

  We have 2 Weblogic Server JVM - 1.4 and 1.6 on the same machine which must be instrumented.

  Can I do a single deployment manager Java allows you to manage the integration of both these servers/JVM to the FMS? Or do I need to have a FglAM separated for each of these Gages?

  Thank you

  Ashley Lewis

  Hello

  You must first verify that you are on a supported platform, please check your OS/WLS/JDK combination against our list of supported http://edocs.quest.com/foglight/565/doc/Cartridge-App/JavaEECartridge-requirements/Supported_Application_Servers.013.3.php#414449 platform

  The reason why I am what I would point out is that you said JDK 1.4, are not supported by the Java JDK 1.4.0/1.4.1 agent, we support JDK 1.4.2 or more. In some cases, when people say that 1.4 they mean in reality 1.4.2 but for instrumentation, it makes a big difference as there are has some interfaces that are there of JDK 1.4.2.

  Technically, you can use the Java Deployment Manager even if there is no specific changes to the instrumentation.config to the title of the agent-override, since you will have 2 "bootstrap" jar (files .jar that correspond to your virtual machine JAVA under the "bootstrap" directory), it should work correctly as each server will start with his own "bootstrap jar file.

  If there was evolution instrumentation.config in respect of the agent override, which requires you to monitor these servers in a completely different configuration of the solution is to create another agent of JavaEEDeploymentManager which is in a different directory. To do this, you need to change the deployment of the agent manager javaeedeployment directory 2nd with the difference that JavaEE (for example set to JavaEE142). In this case, you will have your first officer manager of Javaeedeployment in a directory of JavaEE and the second in another directory (JavaEE142 for example) and it will allow you to monitor these 2 servers with completely different configurations.

  In any case you need not fglam another reason, a fglam is sufficient and technically once the agent manager javaeedeployment is created and activated once, you can close it down to save the OS resources until your next deployment/upgrade.

  Hope this helps

  Golan