How to Integrate Script data with LAMA (Logging and Monitoring Mechanism)
This guide outlines the process for integrating data collected from scripts into LAMA using Applications Manager.
1. Create a Custom Monitor Type
Objective: Set up a custom monitor type to hold data collected from the script.
- Read more about Custom monitor type creation.
Define the monitor type, ensuring the attributes are numeric-based.
Attributes: The attributes should represent the data collected by your script. For example: Throughput, Total Time Taken etc.
Set the delimiter according to the structure of the script’s output. This ensures that the output can be parsed correctly into respective attributes.
Example:
If your script outputs data like Throughput:500|TotalTime:300, the delimiter would be set as |.
2. Add Script Monitors to the Custom Monitor Type
Add new monitors under the Custom Monitor Type (e.g., CustomTypeLAMA) that you created.
Specify the path to the output file generated by the script, which contains the data.
Set the polling interval to 1 minute, meaning the system will collect data every minute.
3. Configure LAMA for Custom Types Integration
Objective: Modify the LAMA configuration to recognize your custom monitor type and the attributes it collects.
Open the LamaConfiguration.xml file located in:
AppManagerHome/working/conf/LamaConfiguration.xml
Add a new segment under <Segments> for your custom monitor, ensuring that it maps correctly with LAMA's requirements.
Sample XML: Refer here
MonitorType: This is the name of the custom monitor created in Step 1.
Attribute values: These should correspond to the attributes set in the custom monitor type.
4. Reload Configuration
Objective: Apply the new configurations to LAMA.
Applications Manager Settings -> Add-on Settings (under Product Settings).
Reload the "LamaConfiguration.xml" using the reload option available in LAMA Integration Card
5. Add Monitors to the LAMA Monitor Group
Objective: Associate the monitors with the LAMA monitor group for data integration.
Add the newly created monitors to the Monitor Group specified in the configuration XML.
The applicationGroupName in the XML should match the group you are adding the monitors to. For example: applicationGroupName="LAMA_APP".
Once added to the group, the data will be collected and pushed to LAMA automatically.
New to ADSelfService Plus?
Related Articles
Script/Custom Monitors - Alarms configured for Table rows were missing
In the Applications manager , users have the ability to manage the table rows of a script or custom monitor type according to their specific requirements. This can be done by enabling the "Enable Script Row Deletion" option. For example, let's ...How to configure Output Settings for Script Monitor?
Below are the details on how to configure Script Monitor Output Settings and expected output format, Output Configuration: Expected Output File Format: In the output file, Scalar data should be separated by scalar delimiter, here name, cpu, javaHeap ...APM Insight monitor is UP, but monitor page doesn't show any data
Possible Causes The APM Insight monitor status corresponds to the respective agent folder pointed Java Application status i.e., as long as the Application server is running, the monitor status will be UP. 1. No Transactions Recorded: It is possible ...Script Monitor FAQs
Common queries, errors and troubleshooting: 1. To execute scripts other than .bat /.vbs in Windows and .sh / .bash in Linux: It is better to execute the script in the form of a command. Eg. To execute python script, you can use command py ...Monitoring HAProxy - Configuring the HAProxy Stats page
To effectively monitor an HAProxy instance, you can enable and access the HAProxy stats page, which provides real-time metrics about HAProxy's performance. Steps to Enable HAProxy Stats: Open the HAProxy Configuration File: The HAProxy configuration ...