BLOG

AppDynamics Utility New Release 

Facebook
LinkedIn
Twitter
Email

Type of Work

During development, the AppDynamics Utility has been updated for the user experience and new features that would help in the process of monitoring many organizations’ applications through AppDynamics.

With the utility, new features have been added based on the use cases of the client’s need to gather essential information from the AppDynamics’ agents. With these cases, we had to integrate AppDynamics’ API to get these data, going through their documentation. 

By following the documentation provided by AppDynamics, we were able to successfully develop new features. By making requests to certain API endpoints, we are able to retrieve and manipulate data into graphs, and tables, export and import dashboards/health rules, and downloadable files. With API needing parameters we developed a form page for users to input values which will be used to create these requests with the AppDynamics API.  

Some features were added that weren’t on AppDynamics’ official API documentation. With the help of the Developer Tools, we were able to extract API requests and duplicate the same functionality within the utility. By looking through the Network tab of the developer tool we were able to extract the right data and information needed to duplicate the request into the utility. Going through multiple requests, looking at the Headers, Payloads, Preview, and Response, and the documented APIs we were able to get a sense of how it functions as a whole. 

Here is the latest documentation: AppDynamics API Documentation 

Application Background

The AppDTools Utility not only has gotten new features but the whole frontend framework has been fully converted to React. With React, it has the potential to reuse components, flexibility, stability, rendering speed, performance, painlessness to create interactive UIs, etc. 

Originally the application was developed using EJS (Embedded JavaScript) a simple templating language that lets you generate HTML markup with plain JavaScript. The reasoning behind using EJS was that it was highly reviewed at the time for a simple-to-use front end for node.js. Braden and Richard, the first interns, made that choice due to their lack of experience with node.js at the time as well. 

Prior to working as interns at Optimiz, we spent our time working with React at Red River College Polytechnic through the Industry Project. Through this, we have built a working MVP application using React. From what we have experienced and dealt with working on the application we are applying them in building components, writing code, debugging issues, testing, and documentation.