Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Avoid reliance on the tool to monitor itself.

  • Observe reduced Total Cost of Ownership (TCO) to manage the monitoring, alerts, and notification system in one place.

  • Manage the history by the retention of the data for audits.

The SnapLogic® Third-party Observability feature offers the capability to integrate pipeline runtime logs with your third-party monitoring tools. This feature enables your IT organization to track, troubleshoot, analyze, and optimize your integrations in production environments.

...

Metric Name

Description

Java Heap <etricsMetrics

plexnode.java.heap.used.bytes

Number of bytes used of the heap.

plexnode.java.heap.total.bytes

Number of bytes allocated for the heap.

plexnode.java.heap.used.pct

Percentage of the heap being used (used / total * 100%).

plexnode.java.heap.max.bytes

The maximum heap size.

plexnode.java.heap.used.of.max.pct

Percentage of the max heap being used (used / max * 100%). This is the same as what the product dashboard reflects.

Java Non-Heap Metrics

plexnode.java.nonheap.used.bytes

Number of bytes used of the off-heap.

plexnode.java.nonheap.total.bytes

Number of bytes allocated for the off-heap.

plexnode.java.nonheap.used.pct

Percentage of the off heap being used (used / total * 100%).

plexnode.java.nonheap.max.bytes

Number of bytes the JVM allowed to allocate off heap.

plexnode.java.nonheap.used.of.max.pct

Percentage of the max off heap being used (used / max * 100%).

CPU Usage Metrics

plexnode.cpu.vcpus.count

Number of vCPUs available on the machine.

plexnode.cpu.load.1min.average

Last minute load average on the machine.

plexnode.cpu.load.pct

System CPU utilization as % of total.

plexnode.cpu.process.load.pct

JCC Process CPU utilization as % of total.

Disk Usage Metrics

plexnode.disk.total.bytes

Overall amount of bytes available on the disk.

plexnode.disk.used.bytes

Amount of bytes used from the disk.

plexnode.disk.used.pct

Percentage of bytes used from the disk.

plexnode.disk.usable.bytes

Amount of bytes available on the disk.

plexnode.disk.usable.pct

Percentage of bytes available on the disk.

Memory Usage Metrics

plexnode.mem.physical.total.bytes

Overall amount of memory in bytes available on the machine.

plexnode.mem.physical.free.bytes

The amount of memory in bytes available for allocation on the machine.

plexnode.mem.physical.used.bytes

The amount of memory in bytes allocated on the machine.

plexnode.mem.physical.free.pct

Percentage of memory available for allocation on the machine.

plexnode.mem.physical.used.pct

Percentage of memory allocated on the machine.

plexnode.mem.swap.total.bytes

The amount of bytes allocated for swap memory on the machine.

plexnode.mem.swap.free.bytes

The amount of bytes available in the swap memory on the machine.

plexnode.mem.swap.used.bytes

The amount of bytes being allocated in the swap memory on the machine, -1 if the swap is not enabled.

plexnode.mem.swap.free.pct

Percentages of total swap memory available on the machine, or -1 if swap is not enabled.

plexnode.mem.swap.used.pct

Percentage of total swap memory allocated on the machine, or -1 if swap is not enabled.

plexnode.mem.virtual.committed.bytes

The amount of virtual memory that is guaranteed to be available to the running process in bytes.

File Utilization Metrics

plexnode.file.descriptor.used.count

Amount of used file descriptors in the system.

plexnode.file.descriptor.free.count

Amount of free file descriptors in the system.

plexnode.file.descriptor.max

Amount of available (configured) file descriptors in the system.

plexnode.file.descriptor.used.pct

Percentage of used file descriptors in the system.

plexnode.file.descriptor.free.pct

Percentage of free file descriptors in the system.

Thread Utilization Metrics

plexnode.thread.jvm.count

The current number of live threads including both daemon and non-daemon threads within JVM.

Slots Utilization Metrics

plexnode.slots.leased

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.

plexnode.slots.max

Amount of slots available (configured) on the node.

plexnode.slots.leased.meter

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

plexnode.net.received.bytes

Overall amount of bytes received through the interface.

plexnode.net.sent.bytes

Overall amount of bytes sent through the interface.

plexnode.net.received.packets

Overall amount of packets received though the interface.

plexnode.net.sent.packets

Overall amount of packets sent through the interface.

plexnode.net.in.errors

Overall amount of input errors through the interface.

plexnode.net.out.error

Overall amount of output errors through the interface.

plexnode.net.in.drops

Incoming/received dropped packets per interface. On Microsoft Windows, returns discarded incoming packets.

Pipeline Activity Metrics

plexnode.pipelines.intiated.meter

The pipeline is being initiated and being prepared/started for execution.

plexnode.pipelines.finished.meter

The pipeline finished its execution.

plexnode.pipelines.requested.meter

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.

plexnode.pipelines.active.total

The number of active pipelines at the moment

Feedmaster Broker Metrics

plexnode.feedmaster.destination.enqueued

The amount of messages the consumer has read out of the queue (applies to Ultra Pipelines).

plexnode.feedmaster.destination.dequeued

The amount of messages the producer has written into the queue (applies to Ultra Pipelines).

Snaplex State Metrics

plexnode.state.leader

1 if node considers itself a leader, otherwise 0.

plexnode.state.neighbors.active

The number of neighbors visible to the node including itself. The node considers to be visible (active) from standing point of the other node if the heartbeat is successful and the state is either RUNNING or COOLDOWN.