About Bryan_James

Bryan_James · ‎04-22-2024

Hi @Eduardo.Rosa ! I don't think this is supported as of the moment. I'm using v24.3.1-1511 of Controller and it doesn't seem to have an option for Patch HTTP method. However you can share improvements and ideas with this specific item on our idea exchange.

Bryan_James · ‎01-30-2023

Hi Everyone! Recently, we are opting to standardize our monitoring solution. Upon our initial research and development, OpenTelemetry has been the newly established standard for monitoring and observability. Our target is to migrate and be enabled on using OpenTelemetry as part of our policies and standard for monitoring. We are aware that there is a product called "Splunk Observability Cloud" which onboards OTLP and any supported platforms to a unified observability stack. For the AIOps, I believe this is still within Splunk Enterprise. While previously we have explored the possible movement to cloud, currently, we are still using Splunk Enterprise. We would like to know if there are any ways we can forward log events to OpenTelemetry, then to Splunk Enterprise. I know this might add overhead as adding another leg (OpenTelmetry) can add additional workload), but this is critical for us to standardize our current monitoring. Here's some items we want to explore: Here's something we have researched before: Splunk Ingest Actions - I think this is only available for Heavy Forwarder. The documentations however, wasn't able to detail out if OTEL endpoint is supported. Splunk Transforms and Outputs (Heavy Forwarder) - On our initial testing, we weren't able to capture data on OTEL Collector. I don't think there exist a configuration for Universal Forwarder to OTEL Collector. May I kindly ask for inputs or any insights what are possible solutions for this? Thank you very much in advanced!

Bryan_James · ‎11-23-2020

Hi Everyone! Recently, I was browsing on AppDynamics docs regarding the auto-remediation scripts. I was amazed at how this works, and decided to read more about custom actions. Then a question came in to my mind. On our organization, there is a server dedicated for Ansible components. Ansible is really net tool to automate tasks such as rolling restarts, deletion, and provisioning, all in one playbook. I was thinking if there would be a way to trigger an ansible playbook rather than a single remediation script? I think this would be possible IF there is an ansible installed on the monitored server. However, the Ansible components are stored on a separate component. I'm thinking that a workaround would be to trigger an auto-remediation script on monitored server, which then runs the playbook command. This method, however, will be more tedious as there are more points involved to trigger a single playbook. Are there any out-of-the-box way / techniques / workarounds to execute a playbook from the policy Controller config?

Bryan_James · ‎07-03-2020

Hi Everyone! For those who come (and will come) across with this question, here are the 2 things I found: 1. Inside the jar file (pretty-much like a compiled archive), you check the manifest file (MANIFEST.MF) inside /META-INF folder. Inside the manifest file contains the Machine Agent Version. Personally I do not recommend this as this is prone to editing might mangle the packaging of the JAR file and might cause the machine agent to fail. However, if you do not remove or update files inside the jar, there should be no problem. 2. Probably this is the easiest way to check Java agent, however, this involves running an executable (JAR) rather than opening a file. On the root directory of machine agent, I tried running the following command: java -jar machineagent.jar Which then produced the following results: Using Java Version [1.8.0_201] for Agent Using Agent Version [Machine Agent v20.6.0-2676 GA compatible with 4.4.1.0 Build Date 2020-06-23 08:07:30] The second one is probably the safest way however, it involves running the agent itself. If you are tight on resources, you can press Ctrl + C right after the version shows. I also found the analytics agent version for Machine agent. Under /monitors/analytics-agent, it is possible to see the version of the analytics agent through the version text files. For those who have found an alternative way of checking the machine agent version, all of your inputs are welcome and can help other teams with their analysis. Thank you!

Bryan_James · ‎07-03-2020

Hi @Ryan.Paredez ! Thank you for your reply! I have checked the link you gave and found out the following: conf: Common configuration files. The configuration files in this directory are used by an agent if a more specific version of the configuration file does not exist in the version-specific conf directory, ver<version_number>/conf. javaagent.jar: The common JAR file used to bootstrap the Java Agent. To enable the agent, pass the fully qualified location of this file as the --javaagent argument value to the JVM at startup. readme.txt: Instructions and notes for installing the Java Agent. utils: Binary files for utilities shared across versions of the agent. ver<version_number>: The javaagent.jar file, configuration files, and other resources specific for this version of the Java Agent. This directory is named to reflect the Java Agent version number, such as ver4.4.0.5. Among other things, the directory contains: conf: The configuration files used by this version of the Java agent, including controller-info.xml, app-agent-config.xml, and more. These settings in these files take precedence over the configuration file in the <agent_home>/conf directory. external-services: Dynamically loaded modules that extend the agent, such as the Analytics Data Sources dynamic service. javaagent.jar: A version-specific JAR file that serves as the Java agent binary. Do not use this Java agent JAR when configuring instrumenting directly. Use javaagent.jar in the root directory instead. lib: Libraries that support the operation of this version of the Java agent. logs: Log files written by the agent. sdk: Samples, APIs, and Javadoc for extending the capabilities of the AppDynamics Java Agent. utils: Binary files for utilities that are specific to this version of the agent. So to answer my previous questions: 1. What's the difference between the top-level javaagent.jar and the one inside the version folder? The top-level javaagent.jar "bootstraps" the one inside the version folder. 2. Thinking of the long term, there might be times that we need to update the java agent on the target host. When updating the java agent, we might need to update environment variables, config files, and other critical metrics. With this, is there a possible way to point to the java agent using a standard (non-changing) directory? It might be possible to just point to the javaagent.jar on root directory. To further validate my understanding, by term "bootstraps", does it mean it calls the java agent inside the version folder? Also on this statement: "The configuration files in this directory are used by an agent if a more specific version of the configuration file does not exist in the version-specific conf directory"; going back to my question number 2. I can still point to the root javaagent.jar, then use the configuration folder on the root directory?

Bryan_James · ‎07-02-2020

Hi everyone! Recently, I'm trying to standardize our instrumentation process. I was checking the folder directory of AppDynamics Java Agent and found out that there are two javaagent.jar. One on the root directory, and another one inside the version folder. What's the difference between the top-level javaagent.jar and the one inside the version folder? Thinking of the long term, there might be times that we need to update the java agent on the target host. When updating the java agent, we might need to update environment variables, config files, and other critical metrics. With this, is there a possible way to point to the java agent using a standard (non-changing) directory?

Bryan_James · ‎07-02-2020

Recently, I am planning to standardize our process on agent installation of AppDynamics. The current process would be to extract the zip file to a specific folder (/opt/appdynamics for Machine Agent). Once the Machine Agents are reported running, we can view the machine agent version on our Controller. Thinking of the long term, there might be times when we need to update the agents deployed on the target hosts. Are there any ways to check the version of the machine agent deployed on the server? I'm thinking of a text file they can open to see the current version of the machine agent deployed.

Bryan_James · ‎03-11-2020

Hi Everyone! I currently want to achieve the following: I want to get a data processed on transaction (an example would be employee ID) from a business transaction. I'm not quite sure if "Analytics" module is involved at this point. For example, the business transaction was made through HTTP, and the call has a field named employeeID with value of 112233. How can I breakdown the transaction and search for employeeID? With the goal achieved above, how do I use it to query on ADQL analytics? I've been trying to figure out data collections. It's still quite unclear to me however, I understand that I need the class and method name to implement a data collector. How about the data that has been passed through HTTP? Is there any way to "dissect" the HTTP call?

Bryan_James · ‎01-30-2019

Good Day! Recently, we have frequent errors regarding "Agent Metric Registration Limit Reached". I searched the kbs and Google for possible answers and came up with this. We are trying to get much information regarding this error so that we can better plan on our next steps. With this, we have few questions and I hope you could help us with these: On the first paragraph of the solution, it has been said that: "Mostly seen when users try to register Custom Metrics with incorrect configurations.". Does this mean that there is a possibility we are seeing this error because of misconfiguration and not just because of exhausting all 5000 metric limit? Is there any way to know the total number of metrics (both custom and standard) on a specific Tier and/or Application? There are other users of our AppDynamics we don't have any contact with. I would like to ask if there's any way we could find the custom metric with incorrect config so we can solve it on our own? On the link given above, it has been said that increasing maximum metric size will yield to higher CPU utilization. Upon checking on our end, CPU and memory utilization of our controller is still low. May I know how big the increase will be? Are there any rule of thumbs to follow when increasing metric limit registration size? Unfortunately, our events service memory utilization is approaching high. May I ask if changing metric limit registration size will affect events service utilization? Aside from memory and cpu, can Filesystem utilization of the main controller (or other services) increase? I hope you could help us with these. Thank you very much!

Bryan_James · ‎11-14-2018

Good Day! I have some questions regarding on how AppDynamics calculate / measures health and metrics. 1. How does AppDynamics measure the health of a Tier? Does it have a (hidden) health rule? What conditions should be met to qualify that a tier is in a critical or warning condition? 2. How does AppDynamics measure the health of a Node? Does it have a (hidden) health rule? What conditions should be met to qualify that a tier is in a critical or warning condition? 3. How does AppDynamics compute for dynamic baseline? 4. On Application Dashboard, sometimes, after setting the baseline to whatever date, the inside circle of the tier icons sometimes turn green. What does this mean? I hope you can help me with this. Thank you very much!

Posts	12
Solutions	2
Karma Given	9
Karma Received	11
Member Since	‎08-18-2021

Online Status	Offline
Date Last Visited	‎04-09-2023 04:43 AM

Is it possible to forward log events from Splunk F...

Firing an Ansible Playbook as Auto-Remediation Scr...

Java Agent JAR Location

Knowing Agent Versions on Application Side

Getting Data from Transactions and Querying the Re...

Agent Metric Registration Limit Reached

AppDynamics Metrics Measurement

Re: PATCH request method