{"id":5532,"date":"2021-07-27T10:52:51","date_gmt":"2021-07-27T08:52:51","guid":{"rendered":"https:\/\/spicasolutions.pl\/?page_id=5532"},"modified":"2024-03-12T14:07:16","modified_gmt":"2024-03-12T13:07:16","slug":"oneagent-ruby-monitoring","status":"publish","type":"page","link":"https:\/\/spicasolutions.pl\/en\/oneagent-ruby-monitoring\/","title":{"rendered":"Dynatrace OneAgent Ruby Monitoring"},"content":{"rendered":"
\n
\n\t

\"oneagentTransfer your best experiences of latest generation monitoring to your Ruby on rails based apps. You don't have to give up the convenience with which Dynatrace is deployed to a monitored system. Benefit from continuous analysis of your system by Davis AI.<\/p>\n

We are proud to present our own agent, which is distributed in the form of a GEM package. No additional configuration is required to function. Simple installation using a package manager separates you from collecting detailed information about each individual transaction passing through your system.<\/p>\n

 <\/p>\n

\"oneagent<\/p>\n

Dynatrace is famous for showing transactions that pass through the entire monitored environment. Now applications written in Ruby will become a part of this chain.<\/p>\n

 <\/p>\n

\"oneagentGain access to transactions from the moment they appear in your application, through controllers, generating views, communicating Redis, web requests, to the database. This is the same level of data that is available in OneAgent for Java, .NET, PHP, GoLang or NodeJS.<\/p>\n

\n<\/div>\n<\/div><\/div><\/div><\/div><\/div><\/div>

\n
\n\t

\"oneagent<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Get the ability to instrument critical pieces of code on your own without having to modify your application. Our agent allows you to indicate the Modules, Classes and Methods to be instrumented.<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div><\/div>

\n
\n\t

\"oneagentDoes your app perform background activities using Sidekiq? For us, it's not a problem.\u00a0 All your jobs will be visible on PurePath. You won't miss any information anymore.<\/p>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>

\n
\n\t

Something went wrong? You will get information about the exception as with any other agent in Dynatrace!<\/p>\n

 <\/p>\n

\"oneagent<\/p>\n

In addition to the visibility of transactions, it is critical from the point of view of system analysis to collect metrics that indicate to us the proper behavior of the application process. That's why our agent can collect several metrics available inside the application.<\/p>\n

 <\/p>\n

Full list of collected metrics:\"oneagent<\/strong><\/p>\n

    \n
  • onesdk.ruby_compact_count.gauge<\/li>\n
  • onesdk.ruby_count.gauge<\/li>\n
  • onesdk.ruby_major_gc_count.gauge<\/li>\n
  • onesdk.ruby_minor_gc_count.gauge<\/li>\n
  • onesdk.ruby_thread_count.gauge<\/li>\n
  • onesdk.ruby_heap_allocatable_pages<\/li>\n
  • onesdk.ruby_heap_allocated_pages<\/li>\n
  • onesdk.ruby_heap_available_slots<\/li>\n
  • onesdk.ruby_heap_eden_pages<\/li>\n
  • onesdk.ruby_heap_final_slots<\/li>\n
  • onesdk.ruby_heap_free_slots<\/li>\n
  • onesdk.ruby_heap_live_slots<\/li>\n
  • onesdk.ruby_heap_marked_slots<\/li>\n
  • onesdk.ruby_heap_sorted_length<\/li>\n
  • onesdk.ruby_heap_tomb_pages<\/li>\n
  • onesdk.ruby_malloc_increase_bytes<\/li>\n
  • onesdk.ruby_malloc_increase_bytes_limit<\/li>\n
  • onesdk.ruby_old_objects<\/li>\n
  • onesdk.ruby_old_objects_limit<\/li>\n
  • onesdk.ruby_oldmalloc_increase_bytes<\/li>\n
  • onesdk.ruby_oldmalloc_increase_bytes_limit<\/li>\n
  • onesdk.ruby_remembered_wb_unprotected_objects<\/li>\n
  • onesdk.ruby_remembered_wb_unprotected_objects_limit<\/li>\n
  • onesdk.ruby_total_allocated_objects<\/li>\n
  • onesdk.ruby_total_allocated_pages<\/li>\n
  • onesdk.ruby_total_allocated_pages<\/li>\n
  • onesdk.ruby_total_freed_objects<\/li>\n
  • onesdk.ruby_total_freed_pages<\/li>\n
  • onesdk.ruby_total_gc_time<\/li>\n
  • onesdk.ruby_total_gc_time<\/li>\n<\/ul>\n

     <\/p>\n

    Full list of supported technologies:<\/strong><\/p>\n

      \n
    • Ruby on Rails 1.9 +<\/li>\n
    • Instrumentation of controllers<\/li>\n
    • Instrumentation of generating views<\/li>\n
    • External communication (WebRequests) with transaction tagging<\/li>\n
    • Communication with the database and its detection<\/li>\n
    • Capturing headers ( Request and Response)<\/li>\n
    • Communication with Redis<\/li>\n
    • Sidekiq Instrumentation<\/li>\n
    • Ability to instrument code from optional agent configuration<\/li>\n
    • Early Access support for Kafka and RabbitMQ requests tracing<\/strong><\/li>\n
    • Collecting thread metrics and Garbage Collector work in Ruby<\/li>\n<\/ul>\n

       <\/p>\n