API Options

Log properties logLocation: The absolute path of the log file. Leave this option blank to use the default location in the gem directory. logAge: Specify either the number of log files to keep or the frequency of rotation (daily, weekly, or monthly). logSize: Specify the maximum log file size (in bytes). debugLevel: Options include (in ascending order of severity) error, info, and debug. Netuitived Connection Properties Netuitived address and port information.

AWS SSM Install

Create Document for Install Script Open the AWS SSM Console. Select Shared Resources > Documents in the navigation pane. Click Create Document. Name the document install-metricly-agents Keep this window open and create a new browser tab. In the new tab, go to Metricly’s GitHub repo for AWS SSM. Copy the page body. In the AWS Console, replace the hello world page body content with the copied JSON. Click Create Document.

CloudWatch Agent

The CloudWatch Agent enables CloudWisdom to collect additional EC2 metrics, such as memory utilization, from AWS. Reports display cost vs. CPU utilization by default. We recommend installing the agent if you are interested in seeing cost vs. memory utilization. The CloudWatch Agent configuration below adds a single memory metric to all instances it is installed on. This incurs an additional charge of ~$0.30/instance/month to your CloudWatch bill. See AWS Cloudwatch pricing for more information.

Collected Metrics

Collected Fully Qualified Name (FQN) Description Statistic Units Min Max Sparse Data Strategy (SDS) BASE CORR UTIL *.calls The number of calls made to the method. sum count 0 none none yes no no *.errors The number of method calls that resulted in errors. sum count 0 none none yes no no *.time The amount of time spent executing the method totaled across all calls.


There are three ways to configure the Linux Agent default collectors: via the BaseCollector, as a combination of individual collectors, or with just the SimpleCollector. This guide outlines their differences and how to use each; however, we encourage you to try the new SimpleCollector. Using the Simple Collector netuitive-diamond/src/collectors/simple Compatibility: The Simple Collector should be used instead of the Base Collector and the Individual Collectors. Where the base or individual collectors include more data (which may be less useful or actionable), this SimpleCollector guarantees a cleaner streamlined experience.

Common Commands

These commands may vary depending on your distro. Linux Commands service netuitive-agent {stop|start|restart} /etc/init.d/netuitive-agent {stop|start|restart} initctl {stop|start|restart} netuitive-agent systemctl {stop|start|restart} netuitive-agent

Computed Metrics

Computed Fully Qualified Name (FQN) Description Statistic Units Min Max BASE CORR UTIL netuitive.jvm.heap.utilizationpercent Percentage of the allocated heap memory that is currently in use.Computation:(Heap Used / Heap Committed) * 100 average percent 0 100 yes yes yes netuitive.jvm.non-heap.utilizationpercent Percentage of the allocated non-heap memory that is currently in use.Computation:(Metaspace or PermGen Used + CodeCache Used / Metaspace or PermGen Committed + CodeCache Committed) * 100 average percent 0 100 yes yes yes netuitive.

Custom MBeans

The Java agent can collect metrics from custom mbeans. We have provided a sample spring boot application that creates 2 custom mbeans with test attributes here. Multiple Custom MBean Diagram For a Single Custom MBean Navigate to the zorka.properties file in your Java agent directory. Near the bottom of the file, set the attribute netuitive.api.custom.stats.mbean to the custom mbean you defined in your application #custom mbean to collect metrics from netuitive.