...
Test the OpenTelemetry Service by running some pipelines on the target Groundplexes, then check your monitoring tool for the runtime data.
Info |
---|
We recommend you use using the values in the YAML sample. Consult your CSM if you plan to change these values. |
...
Set up the OTEL Collector, using the steps in Step 1: Install the OpenTelemetry package.
If you already have the OTEL Collector set up, go to the next step.Either create an account in the New Relic application, or if you already have an account, continue with the next step.
Copy the API key from the Administration > API keys page in the New Relic UI.
Save the YAML file to the following location:
/etc/otelcol
Add the API key to the YAML file under
headers
:Apply changes to the YAML file and restart the Open Telemetry service.
...
Metric Name | Description |
---|---|
Java Heap Metrics | |
| Number of bytes used of the heap. |
| Number of bytes allocated for the heap. |
| Percentage of the heap being used ( |
| The maximum heap size. |
| Percentage of the max heap being used ( |
Java Non-Heap Metrics | |
| Number of bytes used of the off-heap. |
| Number of bytes allocated for the off-heap. |
| Percentage of the off-heap space being used ( |
| Number The number of bytes the JVM allowed to allocate off-heap space. |
| Percentage of the max off-heap being used ( |
CPU Usage Metrics | |
| Number of vCPUs available on the machine. |
| Last minute load average on the machine. |
| System CPU utilization as % of the total. |
| JCC Process CPU utilization as % of the total. |
Disk Usage Metrics | |
| Overall The overall amount of bytes available on the disk. |
| Amount of bytes used from the disk. |
| Percentage of bytes used from the disk. |
| Amount of bytes available on the disk. |
| Percentage of bytes available on the disk. |
Memory Usage Metrics | |
| Overall The overall amount of memory in bytes available on the machine. |
| The amount of memory in bytes available for allocation on the machine. |
| The amount of memory in bytes allocated on the machine. |
| Percentage of memory available for allocation on the machine. |
| Percentage of memory allocated on the machine. |
| The amount of bytes allocated for swap memory on the machine. |
| The amount of bytes available in the swap memory on the machine. |
| The amount of bytes being allocated in the swap memory on the machine, -1 if the swap is not enabled. |
| Percentages of total swap memory available on the machine, or -1 if swap is not enabled. |
| Percentage of total swap memory allocated on the machine, or -1 if swap is not enabled. |
| The amount of virtual memory that is guaranteed to be available to the running process in bytes. |
File Utilization Metrics | |
| Amount of used file descriptors in the system. |
| Amount of free file descriptors in the system. |
| Amount of available (configured) file descriptors in the system. |
| Percentage of used file descriptors in the system. |
| Percentage of free file descriptors in the system. |
Thread Utilization Metrics | |
| The current number of live threads including both daemon and non-daemon threads within JVM. |
Slots Utilization Metrics | |
| Amount of slots leased at the moment. NOTE: if the slots are leased and released in-between the scrapes, the change won’t be reflected in the values. |
| Amount of slots available (configured) on the node. |
| Amount of slots leased at the moment for the pipeline. NOTE: if the slots are leased and released in-between the scrapes, the change won’t be reflected in the values. |
Network IO Metrics | |
| Overall amount of bytes received through the interface. |
| Overall amount of bytes sent through the interface. |
| Overall amount of packets received though the interface. |
| Overall amount of packets sent through the interface. |
| Overall amount of input errors through the interface. |
| Overall amount of output errors through the interface. |
| Incoming/received dropped packets per interface. On Microsoft Windows, returns discarded incoming packets. |
Pipeline Activity Metrics | |
| The pipeline is being initiated and being prepared/started for execution. |
| The pipeline finished its execution. |
| The pipeline has been requested to get ready but has not actually started. This happens for some flows of the UI/Designer, for example, when opening a configuration dialog for the Snap. |
| The number of active pipelines at the moment |
Feedmaster Broker Metrics | |
| The amount of messages the consumer has read out of the queue (applies to Ultra Pipelines). |
| The amount of messages the producer has written into the queue (applies to Ultra Pipelines). |
Snaplex State Metrics | |
| 1 if node considers itself a leader, otherwise 0. |
| The number of neighbors visible to the node including itself. The node considers to be visible (active) from standing is considered visible and therefore active from stand point of the other node if the heartbeat is successful and the state is either |