会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 25. 发明授权
    • Business transaction context for call graph
    • 呼叫图的商业交易上下文
    • US09563485B2
    • 2017-02-07
    • US14530560
    • 2014-10-31
    • AppDynamics, Inc.
    • Christopher Brichford
    • G06F13/00G06F9/54G06F11/30
    • G06F9/54G06F11/30G06F11/3006G06F11/3495G06F2201/865G06F2201/87
    • An application which utilizes a single thread is monitored and context for the individual requests and business transactions operating on that platform are provided. A wrapper is placed is around an object that calls a request. The wrapper renames a request object. Request objects are renamed with a unique name when they are called. When a call stack is sampled, the sampler will retrieve the unique name. Performance data associated with the unique name may be correlated to a business transaction and particular request as metrics are subsequently analyzed. For subsequent reporting, such as call graph reporting, the report or call graph will have requests in the context of a particular business transaction and a particular request instance. This provides more context in reporting of an business application request for frameworks that utilize as single request for multiple threads.
    • 监视利用单个线程的应用程序,并提供在该平台上运行的各个请求和业务事务的上下文。 在调用请求的对象周围放置一个包装器。 包装器重命名请求对象。 请求对象在被调用时被重命名为唯一的名称。 当调用堆栈被采样时,采样器将检索唯一的名称。 与唯一名称相关联的性能数据可以与业务交易和特定请求相关联,因为随后分析度量。 对于后续报告,例如调用图报表,报表或调用图将在特定业务事务和特定请求实例的上下文中具有请求。 这提供了报告业务应用程序请求的更多上下文,该请求用作多个线程的单个请求。
    • 27. 发明授权
    • Network aware distributed business transaction anomaly detection
    • 网络感知分布式业务事务异常检测
    • US09531614B1
    • 2016-12-27
    • US14928982
    • 2015-10-30
    • AppDynamics, Inc.
    • Harish NatarajAjay ChandelPrakash KaligotlaNaveen Kondapalli
    • G06F15/16H04L12/26H04L29/08G06F12/00
    • H04L43/0876H04L29/08072H04L41/046H04L41/0631H04L41/22H04L43/062H04L43/08H04L43/087H04L43/0888H04L63/1408
    • A system monitors applications and network flows used during the business transaction to determine distributed business transaction anomalies caused at least in part by network performance issues. A network flow associated with a business transaction is monitored by a network agent. The network agent may capture packets, analyze the packets and other network data to determine one or more baselines, and dynamically compare subsequent network flow performance to those baselines to determine an anomaly. When an anomaly in a network flow is detected, this information may be provided to a user along with other data regarding a business transaction that is utilizing the network flow. Concurrently with the network agent monitoring, application agents may monitor one or more applications performing the business transaction. The present system reports performance data for a business transaction in terms of application performance and network performance, all in the context of a distributed business transaction.
    • 系统监视业务交易中使用的应用程序和网络流量,以确定至少部分由网络性能问题导致的分布式业务事务异常。 与业务事务关联的网络流由网络代理监视。 网络代理可以捕获分组,分析分组和其他网络数据以确定一个或多个基线,并且动态地将后续网络流性能与这些基线进行比较以确定异常。 当检测到网络流中的异常时,该信息可以与关于正在利用网络流的业务事务的其他数据一起提供给用户。 与网络代理监视同时,应用程序代理可以监视执行业务事务的一个或多个应用程序。 本系统在分布式业务交易的上下文中,根据应用程序性能和网络性能报告业务事务的性能数据。
    • 28. 发明申请
    • AUTOMATIC TASK TRACKING
    • 自动任务追踪
    • US20160323362A1
    • 2016-11-03
    • US14699776
    • 2015-04-29
    • AppDynamics Inc.
    • Vinay SrinivasaiahSanjay Nagaraj
    • H04L29/08H04L12/24
    • H04L41/046G06F9/46G06F11/00G06F11/3006G06F11/301G06F11/3495G06F2201/87G06F2201/875H04L41/5058H04L67/02
    • The present technology correlates tasks between multiple threads of an application. A payload consisting of a task object may be identified as part of a method. Identification of the task object may be performed using instrumentation or some other method. Once the task object is identified, the payload may be instrumented to track the task object or payload and correlate the task object with other executing threads. Instrumenting the payload may include determining the constructor of the task object and instrumenting the task object constructors to determine what creates the task object. Once the source of a task object or payload is determined, the current thread having the task object as a parameter and another thread which creates the task may be tied together as part of a business transaction.
    • 本技术将应用程序的多个线程之间的任务相关联。 由任务对象组成的有效负载可以被识别为方法的一部分。 可以使用仪器或其他方法来执行任务对象的识别。 一旦识别了任务对象,可以对有效载荷进行检测,以跟踪任务对象或有效载荷,并将任务对象与其他执行线程相关联。 测量有效载荷可能包括确定任务对象的构造函数,并对任务对象构造函数进行调整,以确定创建任务对象的内容。 一旦确定了任务对象或有效负载的源,具有任务对象作为参数的当前线程和创建任务的另一个线程可以作为业务事务的一部分被绑定在一起。
    • 29. 发明申请
    • DETECTION OF NODE.JS MEMORY LEAKS
    • 检测NODE.JS内存泄漏
    • US20160323160A1
    • 2016-11-03
    • US14699284
    • 2015-04-29
    • AppDynamics, Inc.
    • Dmitri MelikyanDavid Roth
    • H04L12/26G06F3/06
    • G06F3/067G06F11/073G06F11/0751G06F11/366H04L41/0233
    • A system detects memory leaks in Node.JS applications. The memory leaks are associated with lines of code rather than particular objects. Lines of code associated with a memory leak is identified by object allocation tracking. Object allocation for lines of code is tracked. A heap snapshot may be captured at the same time at which the object allocation occurs. The results of the object allocation are processed, including removal of objects cleaned up by garbage collection. Objects remaining in the object allocation results are then searched for the end heap snapshot. For objects found in the heap snapshot, the corresponding lines of code that generate the objects are reported to administrators the application.
    • 系统检测Node.JS应用程序中的内存泄漏。 内存泄漏与代码行相关联,而不是特定对象。 通过对象分配跟踪来识别与内存泄漏相关联的代码行。 跟踪代码行的对象分配。 可以在发生对象分配的同时捕获堆快照。 处理对象分配的结果,包括清除垃圾收集清理的对象。 然后搜索剩余在对象分配结果中的对象的结束堆快照。 对于在堆快照中找到的对象,生成对象的相应代码行将向应用程序报告给管理员。