AppD Archive

Extension Data Not showing up in Metric Browser

CommunityUser
Splunk Employee
Splunk Employee

Greetings Experts,

Here is my question, i have configured a monitong extension and placed it under directory: $APPDYNAMICS_HOME/monitors/subdirectory/ for the Machine Agent. Restarted the Machine Agent, but it is not coming up in the Metric Browser. Script runs perfectly when executed individually. Also, where i shoudl be checking it in the Metric Browser. In the Metric Browser tree there is no new branch created. and also i am not able to see it in Application Infrastructure Performance.

Also i would like to add the Configuration Complexity:
1 Application: 1 Tier: 4 Nodes

I am testing it for only 1 node so far but i am not able to see it in the Metric Browser.

Script:

=====================================

#!/bin/sh


STATUS=`/***PATH*****/opmn/bin/opmnctl status | grep HTTP_Server | cut -d \| -f 4 | xargs`

if [ "$STATUS" == "Alive" ]
then
        STATUS=1
else
        STATUS=0
fi

echo "name=Service|Cataegories|OHS_Service,value="$STATUS

=======================================

more monitor.xml

==============================

<monitor>
    <name>MyMonitors</name>
    <type>managed</type>
    <description>Monitor OHS Service </description>
    <monitor-configuration>
    </monitor-configuration>
    <monitor-run-task>
        <execution-style>continuous</execution-style>
        <name>Run</name>
        <type>executable</type>
        <task-arguments>
        </task-arguments>
        <executable-task>
            <type>file</type>
            <file>check_OHS_Service.sh</file>
        </executable-task>
    </monitor-run-task>
</monitor>

======================================================

Error Logs:

file:/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/monitor.xml
[system-thread-0] 17 Jul 2016 06:09:39,800  INFO MonitorConfigReader - os name [linux] version [2.6.18-404.el5]
[system-thread-0] 17 Jul 2016 06:09:39,801  INFO NodeMonitorManager - Initializing managed monitor [OHSMonitor]
[system-thread-0] 17 Jul 2016 06:09:39,806  INFO ManagedMonitorDelegate - Initializing managed monitor [MyMonitors]
[system-thread-0] 17 Jul 2016 06:09:39,807  INFO ManagedMonitorDelegate - Executing managed monitor [MyMonitors], task name [Run]
[system-thread-0] 17 Jul 2016 06:09:39,807  INFO ManagedMonitorDelegate - Task [Run] for monitor [MyMonitors] is continuous
[system-thread-0] 17 Jul 2016 06:09:39,817  INFO ExecTask - Initializing process for exec task
[system-thread-0] 17 Jul 2016 06:09:39,817  INFO ExecTask - Running executable script on disk [check_OHS_Service.sh]
[system-thread-0] 17 Jul 2016 06:09:39,817  INFO ExecTask - Executing script [/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[system-thread-0] 17 Jul 2016 06:09:39,867  INFO ExecTask - No task arguments to add
[system-thread-0] 17 Jul 2016 06:09:39,868  INFO ExecTask - Initializing process builder with command list[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[system-thread-0] 17 Jul 2016 06:09:39,868  INFO ExecTask - Initializing process builder with enviornment variables {}
[system-thread-0] 17 Jul 2016 06:09:39,869  INFO ContinuousTaskMonitor - Continuous Task [MyMonitors] Started
[system-thread-0] 17 Jul 2016 06:09:39,869  INFO MonitorConfigReader - Reading monitor config

[system-thread-0] 17 Jul 2016 06:09:39,873  INFO SystemAgent - Set up agent monitor manager
[system-thread-0] 17 Jul 2016 06:09:39,874  INFO SystemAgent - Orchestration is disabled - disabling one-way agent transport. The agent will not be able to execute workflow tasks.
[system-thread-0] 17 Jul 2016 06:09:39,878  INFO SystemAgentConfigManager - Scheduling configuration refresh at an interval of 60 seconds
[system-thread-0] 17 Jul 2016 06:09:39,879  INFO SystemAgentConfigManager - Configuration refresh task interval is 60 seconds
[system-thread-0] 17 Jul 2016 06:09:39,880  INFO SystemAgent - Configuration manager successfully configured
[system-thread-0] 17 Jul 2016 06:09:39,881  INFO RunbookHandler - Runbook Operation Execution is : [enabled].
[system-thread-0] 17 Jul 2016 06:09:39,882  INFO SystemAgent - Started AppDynamics Machine Agent Successfully.
[Worker-1] 17 Jul 2016 06:09:39,889  INFO ExecTask - Running Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-1] 17 Jul 2016 06:09:40,020  INFO ExecTask - Forcing stop for Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-1] 17 Jul 2016 06:09:40,020  INFO MonitorStreamConsumer - Stopping monitored process
[Agent-Monitor-Scheduler-1] 17 Jul 2016 06:10:09,788  WARN ContinuousTaskMonitor - Continuous Task [MyMonitors] stopped, restarting..
[Agent-Monitor-Scheduler-1] 17 Jul 2016 06:10:09,788  INFO ContinuousTaskMonitor - Continuous Task [MyMonitors] Restarted
[Worker-6] 17 Jul 2016 06:10:09,788  INFO ExecTask - Initializing process for exec task
[Worker-6] 17 Jul 2016 06:10:09,789  INFO ExecTask - Running executable script on disk [check_OHS_Service.sh]
[Worker-6] 17 Jul 2016 06:10:09,789  INFO ExecTask - Executing script [/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[Worker-6] 17 Jul 2016 06:10:09,820  INFO ExecTask - No task arguments to add
[Worker-6] 17 Jul 2016 06:10:09,821  INFO ExecTask - Initializing process builder with command list[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[Worker-6] 17 Jul 2016 06:10:09,821  INFO ExecTask - Initializing process builder with enviornment variables {}
[Worker-6] 17 Jul 2016 06:10:09,821  INFO ExecTask - Running Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-6] 17 Jul 2016 06:10:09,997  INFO ExecTask - Forcing stop for Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-6] 17 Jul 2016 06:10:09,997  INFO MonitorStreamConsumer - Stopping monitored process
[extension-scheduler-pool-1] 17 Jul 2016 06:10:10,100  WARN ErrorStreamConsumer - ignoring error line:[event-type=MACHINE_AGENT_LOG, severity=WARN, message=bios_info gather returned empty string, skip parsing]
[Agent-Monitor-Scheduler-1] 17 Jul 2016 06:10:39,772  WARN ContinuousTaskMonitor - Continuous Task [MyMonitors] stopped, restarting..
[Agent-Monitor-Scheduler-1] 17 Jul 2016 06:10:39,772  INFO ContinuousTaskMonitor - Continuous Task [MyMonitors] Restarted
[Worker-3] 17 Jul 2016 06:10:39,772  INFO ExecTask - Initializing process for exec task
[Worker-3] 17 Jul 2016 06:10:39,772  INFO ExecTask - Running executable script on disk [check_OHS_Service.sh]
[Worker-3] 17 Jul 2016 06:10:39,773  INFO ExecTask - Executing script [/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[Worker-3] 17 Jul 2016 06:10:39,776  INFO ExecTask - No task arguments to add
[Worker-3] 17 Jul 2016 06:10:39,776  INFO ExecTask - Initializing process builder with command list[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]
[Worker-3] 17 Jul 2016 06:10:39,776  INFO ExecTask - Initializing process builder with enviornment variables {}
[Worker-3] 17 Jul 2016 06:10:39,776  INFO ExecTask - Running Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-3] 17 Jul 2016 06:10:39,905  INFO ExecTask - Forcing stop for Executable Command [[/cdts/cli/runtimes/appdynamics/machineAgent/machineAgent-4.2.1/monitors/OHSMonitor/check_OHS_Service.sh]]
[Worker-3] 17 Jul 2016 06:10:39,906  INFO MonitorStreamConsumer - Stopping monitored process
[extension-scheduler-pool-3] 17 Jul 2016 06:10:40,398  WARN ErrorStreamConsumer - ignoring error line:[event-type=MACHINE_AGENT_LOG, severity=WARN, message=bios_info gather returned empty string, skip parsing]

Thanks & Regards,

Varun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

You can find the extension metrics in the Node -->JMX tab--> mbean browser, Here you need to create  a new JMX configuration of the metric to view the it metrics brower.

Regards,

Vamshi

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hello Vamshi,

I believe that is in particular to JMX Metrics... I am just wondering what is the issue with what i am trying... looks to be a simple Metrics.

I tried few things:

echo "name=Server|Component:50|Individual Nodes|cli_cdetsqaweb1|Hardware Resources|Service|OHS_Service,value="$STATUS

Didn't worked, instead created 2 sets of Individual Nodes in the Metric browser, overwriting the needed existing hierarchy.

Now i am trying below config:

echo "name=Server|Component:50|Custom Metrics|Service|OHS_Service,value="$STATUS

Will let know on the results.

Thanks & Regards,

Varun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...