Secondary agents Foglight 5 cartridge FSA

Hello

I am using the agent script generator to try to create a custom agent cartridge that has a secondary ASP, but seem to have problems.

After the deployment of the agent in Foglight, when I click on change the properties of the agent, the secondary ASP is mentioned here, according to the ma - strategie.xml, however when I click Edit I have the following error:

shareableData.fields is not defined

Also when my agent is running I don't seem to be able to reference the secondary ASP, for example:

#! / usr/bin/ksh
Set - vx

LIMIT = $MyList_rowCount
echo "LOG - LIMIT = $LIMIT\n.

The $LIMIT value is not being filled, and the log entry simply indicates

JOURNAL - LIMIT =

Someone at - it clues as to where I'm wrong?

Thank you

Paul

Bingo! I modified the build script to randomly generate the IDS for the secondary ASP and it worked.

Thanks for your time on this.

Tags: Dell Tech

Similar Questions

  • Properties of the Agent Foglight FMS 5.6.7

    Morning,

    As you can gather, I'm new to this software. I have another question related to installation. I am currently at the stage of the development of events and monitoring service in the Agent Properties screen

    How to set up IIS monitoring? I read that this is carried out using the cartridge of the Infrastructure, is this the case? I ask the same question about windows processes.

    If you are simply interested in monitoring the process and availability you can do with an agent of the utility called appmonitor which is part of the supervision of legacy OS (works on windows and unix)

    http://en.community.Dell.com/TechCenter/performance-monitoring/Foglight-administrators/w/Admins-wiki/5646.monitoring-application-availability-using-Foglight-utility-agents

    If you do not look for surveillance that include things like the IIS Web sites, etc. application pools the right agent is the agent of .NET.

    http://eDOCS.quest.com/Foglight/567/doc/wwhelp/wwhimpl/common/HTML/frameset.htm?href=cartridge-APM/dotNetCartridge-install/index.php

    Hope this helps

    Golan

  • Foglight cartridge for the monitoring of newspapers

    Hello

    I was looking for cartridge for the monitoring of newspapers for the FMS Version: 5.6.10 and I have not found, can anyone let me know if there is any cartridge in Foglight to monitor logs. My requirment is to check the exceptions/strings in log so that I can generate alerts on it.

    Thank you

    Shashank Soni.

    As mentioned Vlad, there's an agent called LogFilter, which can monitor log files

    http://eDOCS.quest.com/Foglight/5610/doc/wwhelp/wwhimpl/common/HTML/frameset.htm?context=cartridgeInf&file=OSCartridge/LogFilter.1.php&single=true

    It is a part of the BONES of the legacy that the cartridge is downloadable under the name

    "Cartridge Foglight for operating systems 5.5.4.

    https://support.software.Dell.com/download-install-detail/4973219?prodjid=1-7GCB8-91

    An example of use of the cartridge can be found in this article

    http://en.community.Dell.com/TechCenter/performance-monitoring/Foglight-administrators/w/Admins-wiki/5646.monitoring-application-availability-using-Foglight-utility-agents

    The cartridge requires a Foglight Manager Agent to be deployed on the computer where the log files.

    I hope this helps.

    Golan

  • PS_App could not be found in foglight monitor agent areas

    Hi all

    We have configured the monitor agent PS App for Peoplesoft-Windows machine monitoring. We gave the home path and the path of smoking in the properties of the Agent and the cartridge is 5.6.2.1 we use.

    the agent is unable to find the areas for the host, especially for Windows machines.

    Please suggest some troubleshooting steps to resolve this problem.

    Thank you best regards &,.

    Guenoun

    Gokuinath, I recommend put you foglight agent manager that is associated with the agent of PeopleSoft application in debug mode. With the debug mode, we can see in file of newspaper on what additional information the agent.

    The command below will activate the debug mode without having to restart a foglight agent manager:

    fglam.exe - set-global-debug-level 1

    You must disable and re-enable the peoplesoft application agent that you have worked.

    To do additional debugging, we see the files of fglam newspapers and the foglight peoplesoft agent logs

    David Mendoza

    Foglight Consultant

  • Foglight 5.6.2 Infrastructure Management cartridge - OS

    Of the CartridgeForInfrastructure_Guide.pdf p. 12

    "Monitoring of remote hosts.

    Unlike the previous generation of the system, agents of Infrastructure can be put in place to monitor

    the remote host. A single Agent Foglight handler can host many Infrastructure, remote agents

    monitoring of the different hosts. Agents of the Infrastructure can still be used locally in situations where

    remote control is not possible. »

    The above statement is the Guide and says '' a single Agent Foglight handler may accommodate many agents Infrastructure, remote monitoring of different guests. ''

    What is 'a lot' here? What is the host number that can be configured by fglam? How is it has no number given in the guide so that customer is aware of how to create and deploy the host by fglam.

    Thank you

    #AJ

    Hi AJ,.

    The number of hosts that can be remotely monitored by a FglAM is a moving target and tha response mainly depends on the resources (CPU, memory, network) which are available to the FglAM.

    Current best practices are to control a maximum of 256 hosts remotely with a FglAM.

    We tested FglAM with many more, but we see memory usage begins to increase nonlinear right here.

    Kind regards

    Brian Wheeldon

  • Monitoring Apache with a custom agent State

    Hi people,

    Foglight includes an ApacheSvr agent in the cartridge of the BONE that monitors Apache locally by analyzing the history of the Apache access.

    Some Quest engineers have collaborated on an agent based on a script that monitors the Apache remote by analyzing the output generated by the page Status of Apache.

    This information is available when apache httpd is compiled with the "mod_status" module and ExtendedStatus is now as described in: http://httpd.apache.org/docs/2.0/mod/mod_status.html

    When activated, the Apache /server-status page looks like http://www.apache.org/server-status

    The agent script runs under Unix. It collects, analysis and reports 21 measures focused on the Apache Foglight.

    If you are interested in this agent custom, especially if you have Apache status active on your site and would like to beta test the agent and providing feedback, please respond.

    Kind regards

    Brian Wheeldon

    I would like to help test!

  • Foglight for vFoglight

    Can someone explain to me what looks like a transition from Foglight to vFoglight?  Is this documented somewhere. Is this a new install, or we will be abel to keep existing history, etc...

    The past several versions of vFoglight are actually identical to Foglight + vFoglight cartridge.  Install the cartridge on the current version of Foglight vFoglight offers similar functionality to the installation of pre-packaged vFoglight.

    There should be no effect on the existing data collected from things like servers, databases, etc.

    Note that the cartridge vFoglight requires a separate license, is not surprising, and you should always consider your existing FMS capacity before adding further data collection process.

    The installation process is to obtain a license key, download of the cartridge on the support site and download it in your FMS.  Perhaps takes 10 min to be ready to connect to Virtual Center and begin collecting data.

    Note that, vFoglight brings together a lot of information.  Depending on the number and the size of your virtual centres, you could consider the deployment of 1 or several additional VMs of FGLAM just for the collection of data in Virtual Center.  Put the FGLAM on the Virtual Center Server directly is possible, but not best practices.

    In addition, you should review the configuration of the agent for any VMs who will now be collected through vFoglight cartridge and turn off CPU/memory/Network Infrastructure data collection as both cartridges could fill the same properties on host objects unnecessarily.

    Finally, you don't want to use the VMware-> VMware environment-> Administration tab for the deployment of new agents, which gives you the opportunity to collect up to 30 days of history existing Virtual Center when new agents are deployed, an option that is not available through the Administration-> Agents-> Agent status screen.  Once the story has been collected, then agents can be administered through the screen of the status of the Agent as other officers.

  • Deploy the fglam and agents using puppets?

    Hello

    I was wondering everyone deployed fglam or other agents through puppets?

    Any information you share will be great.

    Thanks in advance

    GS

    Hey, GSA,

    Sorry I'm more the Foglight person in my company I only get to see come to the forums to help out a colleague.

    Yes, we have entirely puppets running for our fglams and Wssf. It was boring, you're linux Debian or company founded? Quest unfortunately does not support standard deb/RPM, perferring an installer of owner. If you need make your own. I am happy to send you a copy of our 64 bit RPM. It's about 120 megs. Just throw it in your rest and you should be good to go. Ideally if you need to build your own to make sure that you can keep up-to-date with the latest agents and pieces of fglam.

    Discover this - http://blog.yo61.com/building-rpms-from-ruby-gems-with-fpm.html

    I recommend the staging of your cartridges in advance when you build the RPM. For us, it was worth the extra space in the RPM to compensate for the time that should be a cartridge via the script on the network. Using this method I have cartridge legacy/IC/Apache and customized all in place so I can save some deploy times. It is somewhat important in larger environments due to a problem known in Foglight on the deployment of wagons/creation and activation of agents the time it can take is VERY random.

    In our tests, we had 500 machines archive on a clean server FMS (5.6.4 at the time). Some would take 2-3 minutes to complete, some would take 20! PSO went to dev and they have never been able to understand why delays random when you start the agent script check in the back to the rear. But since you can't count on it fill inside your run time of the puppets you should reduce the time it takes.

    Don't forget that Foglight is not updated with the scale/config friendly management. They store a lot of config data in databases and use IDS in their configuration files that are made by ther FMS. Thus, it can be difficult to handle most things. You end up having to write a lot of execs once. Glad you sent a copy of our manifesto if you wish. I have just to sanatize it. I found it easier to do was run as a 'touch' inside a folder in the % fglam % of indiecate installation directory which have executed elements.

    One thing you might want to, is your vm.config scheduled start at the fglam. Then will happen. Otherwise you; He's eventually do custom made for your ID Agent Foglight who ends up being a nightmare. You can apply your logic of setting JVM at the time of installation. It won' just manageable tbe.

    You can create custom providers to exploit different groovy scripts, but honestly this isn't worth it unless you might be working for Quest PSO. Be sure to place a 'idea' to get Foglight more user-friendly automation, configuration management and scaling tools. If enough of us let them know that these scalabiltiy is a factor for us they could get it in next Foglight.

    Another thing to remember as you automate you must ensure your FMS travels and erase data from all machines on its own topology. In my first POC run, I forgot about it and after about a month, the FMS ran terrible everything by supporting only 5000 guests. After I cleaned the topology and reset, there great. Since then, I just rule the kickoff to 4 hours to clean up the obsolete data and it has worked great since I did that.

  • Inconsistent data collection in Foglight (FMS) 5.6.4

    Hello

    We use Foglight 5.6.4 for the monitoring of applications, hosts (physical and virtual). In this process, we deploy mulltiple agents using different cartridges to collect level Infrastructure settings.

    The problem we are facing is, we are unable to obtain data from the monitored hosts in a coherent way.

    (i.e.) if we are looking for (say data today ' hui), it shows data for all hosts, but if change us the interval and search data from the night before, we could not get the data for all hosts.

    Thus, customers seeking any specific day data are not able to get the data correctly because they generate reports with these data.

    Kindly ask you to bring a solution.

    Kind regards

    Guenoun

    Guenoun,

    The screenshots you posted show one or more instances of a portlet that displays the key indicators for the host groups in each level.

    The missing parameters are percentage of values associated with the memory, disk, CPU, and network.

    It's a custom portlet, so it is impossible to know what aspect of the metric is shown, but I would hazard a guess that it is the "current" value of the metric. In a daily time slot, this value represents the observation just before midnight, which is not particularly significant.

    If the portlet displays the value of 'the period/average', he would meaningfully represent average during the selected day. I would be more surprised to see the lack of value of 'the period/average '.

    One thing you can do is to open one of these parameters in the data browser with a time interval of several days and inspect the comments in the "history" list These observations represent a continuous value for this measure, or are there gaps?

    Another way you can do is drag and drop one of these settings on a dashboard custom diagram.

    Set the time range to seven days and see if there are gaps in the graph. You can export all comments in CSV or Excel to inspect their individually.

    To summarize:

    1. Your custom portlet is configured to display the "current/average" or the "period/average" of the metric?
    2. Is the history of observation for these ongoing metrics or are there gaps?

    Kind regards

    Brian Wheeldon

  • Telnet Monitoring port in Foglight

    Hi all

    At present I'm migrate all servers linux monitoring Nagios to Foglight and comparing Nagios check Foglight Infrastructure cartridge, I found that there is no verification of telnet port. Y at - it a cartridge that will take care of this type of surveillance or I need to write custom Foglight cartridge?

    Thank you

    Shashank Soni.

    Foglight doesn't do this out of the box, but it can be configured.  Check out these two positions: one and two.

    That said, I hope that you check that the telnet port is not open.  No one should use telnet these days, it isn't safe. Use ssh.

    Jeff

  • POUVEZ FOGLIGHT CONTROL OF EXTERNAL SMTP CONNECTIONS?

    Hello - I have recently been approaching with an interesting use case as we see if Foglight can monitor SMTP (port 25) connections out to the 3rd party that use e-mail as a way to send and receive information for a particular customer.  Is this possible?  In a perfect world, if the NetMonitor Agent can be configured for specific ports, it would be the work that we could simply enter our source and destination and the corresponding ports.

    Concerning

    Hi Daisy.

    Please see this thread - he speaks using script agents Foglight in ways that might help you:

    http://en.community.Dell.com/TechCenter/SharePoint-for-all/f/4782/t/19552136

    HTH

    Robert Statsinger

  • Foglight for the storage facility

    All,

    I have check the Foglight for cartridge storage, to install on my FMS I got the following errors. Any idea that is this all?

    Lack of dependencies for cartridge: StorageUI - 2.0.0 - 20120822_174255:StorageCollector - 2.0.0 (corresponds to: LAST) SanNasListener - 2.0.0 (corresponds to: LATEST)

    Lack of dependencies for cartridge: StorageCollector - 2.0.0 - 2.0.0 - 20120822 - 1742:DRP - 5.6.4 (corresponds to: LAST) virtual-VMware - 5.6.4 (corresponds to: LAST) virtual-VMware-dependencies - 5.6.4 (corresponds to: LATEST)

    Missing dependency for cartridge: SanNasListener - 2.0.0 - 20120822_174209:StorageCollector - 2.0.0 (matches: LAST)

    FYI my vmware cartridge was obsolete. Now works.

  • Foglight master with the Federated child vFoglight

    Hi people,

    If I have a master of Federation Foglight with cartridge of VMware, is it possible to have a federated vFoglight child as long as the requirements are met?

    Thank you.

    Kind regards

    Hollis

    Hi Hollis,

    We have tested this configuration in our lab and it worked as expected.

    Kind regards

    Darren

  • Monitoring hugepages

    Is it possible to monitor the hugepages on a Linux server? I found the KB 66451 article that mentions an enhancement request for this to the cartridge of the BONE (OS-1055), I guess that it was not in the cartridge of the Infrastructure.

    If it is not part of the output of the box cartridges is it possible to create a custom agent and associate the metrics to the host?

    Thank you

    Kris

    I checked with the support, it does not make the cartridge of the infrastructure.

    An agent script is probably the way forward, with Foglight any script that writes to standard output may be packaged as a script and data can be send to http://en.community.dell.com/techcenter/performance-monitoring/foglight-administrators/w/admins-wiki/5787.custom-agents-introduction-to-script-agents Foglight

    Hope this helps

    Golan

  • End user scenarios

    Hi all

    is it good idea while FogLight:

    End user scenarios

    I'm looking for documentation on this topic.

    Thank you.

    Guy,

    What do you mean by scenarios?

    End-user monitoring is done in 2 ways:

    1. an agent Foglight (Robot), who exercises the demand and performance and availability reports. You tell the agent which pages and flow of exercise and it does in different intervals of time and reports performance/availability to Foglight. I guess that these flows can be called scenarios, the information found in the synthetic track in edocs

    http://eDOCS.quest.com/Foglight/565/doc/wwhelp/wwhimpl/common/HTML/frameset.htm?href=cartridge-enduser/FTR/index.php

    http://eDOCS.quest.com/Foglight/565/doc/wwhelp/wwhimpl/common/HTML/frameset.htm?href=cartridge-enduser/SyntheticMonitor/index.php

    2 Foglight devices that are sniff web traffic, you connect the unit to a span port on a switch or a network tap and they sneeff you web traffic and sessionize them. You can then, among other things, define transactions (sequence of pages) or press filters (web request or response that is particularly interesting to watch) and see what the user has done on the site (replay in user session). I guees this can also be defined as scenarios but you have to have the appliances in place for that. The information is also available in the document to the end user of surveillance (FxM and FxV)

    FxM (sniffer web).

    http://eDOCS.quest.com/Foglight/558/Foglight_FxMCartridgeOverview_Video.html

    FxV (sessionizer/viewer)-

    http://eDOCS.quest.com/Foglight/558/Foglight_FxVCartridgeOverview_Video.html

    Golan

Maybe you are looking for