Fly.io integration metrics

The official Datadog integration for monitoring Fly.io. It collects 133 metrics.

Official summary

Monitor your Fly.io apps and machines.

Metric types

  • gauge (value at a point in time): 94
  • count (occurrences in the interval): 39

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
fly_io.app.concurrencygauge-
fly_io.app.connect_time.bucketcountsecond
fly_io.app.connect_time.countcount-
fly_io.app.connect_time.sumcountsecond
fly_io.app.countCount of appsgauge-
fly_io.app.http_response_time.bucketcountsecond
fly_io.app.http_response_time.countcount-
fly_io.app.http_response_time.sumcountsecond
fly_io.app.http_responses.countgaugeresponse
fly_io.app.tcp_connects.countgauge-
fly_io.app.tcp_disconnects.countgauge-
fly_io.edge.data_ingaugebyte
fly_io.edge.data_outgaugebyte
fly_io.edge.http_response_time.bucketcountsecond
fly_io.edge.http_response_time.countcount-
fly_io.edge.http_response_time.sumcountsecond
fly_io.edge.http_responses.countgaugeresponse
fly_io.edge.tcp_connects.countgauge-
fly_io.edge.tcp_disconnects.countgauge-
fly_io.edge.tls_handshake_errorsgaugeerror
fly_io.edge.tls_handshake_time.bucketcountsecond
fly_io.edge.tls_handshake_time.countcount-
fly_io.edge.tls_handshake_time.sumcountsecond
fly_io.instance.cpu.countThe amount of time each CPU (cpu_id) has spent performing different kinds of work (mode) in centisecondscount-
fly_io.instance.disk.io_in_progressIncremented as requests are given to appropriate struct request_queue and decremented as they finish.gauge-
fly_io.instance.disk.reads_completed.countThis is the total number of reads completed successfully.count-
fly_io.instance.disk.reads_merged.countReads and writes which are adjacent to each other may be merged for efficiency. This field lets you know how often this was done.count-
fly_io.instance.disk.sectors_read.countThis is the total number of sectors read successfully.count-
fly_io.instance.disk.sectors_written.countThis is the total number of sectors written successfully.count-
fly_io.instance.disk.time_io.countCounts jiffies when at least one request was started or completed. If request runs more than 2 jiffies then some I/O time might be not accounted in case of concurrent requests.countmillisecond
fly_io.instance.disk.time_io_weighted.countIncremented at each I/O start, I/O completion, I/O merge, or read of these stats by the number of I/Os in progress (field 9) times the number of milliseconds spent doing I/O since the last update of this field.countmillisecond
fly_io.instance.disk.time_reading.countThis is the total number of milliseconds spent by all reads.countmillisecond
fly_io.instance.disk.time_writing.countThis is the total number of milliseconds spent by all writescountmillisecond
fly_io.instance.disk.writes_completed.countThis is the total number of writes completed successfully.count-
fly_io.instance.disk.writes_merged.countReads and writes which are adjacent to each other may be merged for efficiency. This field lets you know how often this was done.count-
fly_io.instance.filefd.allocatedNumber of allocated file descriptorsgauge-
fly_io.instance.filefd.maxNumber of maximum file descriptorsgauge-
fly_io.instance.filesystem.block_sizeFile system block size.gauge-
fly_io.instance.filesystem.blocksTotal number of blocks on file systemgauge-
fly_io.instance.filesystem.blocks_availTotal number of available blocks.gauge-
fly_io.instance.filesystem.blocks_freeTotal number of free blocks.gauge-
fly_io.instance.load.avgSystem load average measuring the number of processes in the system run queue, with samples representing averages over 1, 5, and 15 minutes.gaugeprocess
fly_io.instance.memory.activeMemory that has been used more recently and usually not reclaimed unless absolutely necessary.gaugebyte
fly_io.instance.memory.buffersRelatively temporary storage for raw disk blocksgaugebyte
fly_io.instance.memory.cachedIn-memory cache for files read from the disk (the pagecache) as well as tmpfs & shmem. Doesn't include SwapCached.gaugebyte
fly_io.instance.memory.dirtyMemory which is waiting to get written back to the diskgaugebyte
fly_io.instance.memory.inactiveMemory which has been less recently used. It is more eligible to be reclaimed for other purposesgaugebyte
fly_io.instance.memory.mem_availableAn estimate of how much memory is available for starting new applications, without swapping.gaugebyte
fly_io.instance.memory.mem_freeTotal free RAM.gaugebyte
fly_io.instance.memory.mem_totalTotal usable RAM (i.e. physical RAM minus a few reserved bits and the kernel binary code)gaugebyte
fly_io.instance.memory.pressure_fullMemory pressure for all processesgauge-
fly_io.instance.memory.pressure_someMemory pressure for at least one processgauge-
fly_io.instance.memory.shmemTotal memory used by shared memory (shmem) and tmpfsgaugebyte
fly_io.instance.memory.slabin-kernel data structures cachegaugebyte
fly_io.instance.memory.swap_cachedMemory that once was swapped out, is swapped back in but still also is in the swapfilegaugebyte
fly_io.instance.memory.swap_freeMemory which has been evicted from RAM, and is temporarily on the diskgaugebyte
fly_io.instance.memory.swap_totaltotal amount of swap space availablegaugebyte
fly_io.instance.memory.vmalloc_chunklargest contiguous block of vmalloc area which is freegaugebyte
fly_io.instance.memory.vmalloc_totaltotal size of vmalloc virtual address spacegaugebyte
fly_io.instance.memory.vmalloc_usedamount of vmalloc area which is usedgaugebyte
fly_io.instance.memory.writebackMemory which is actively being written back to the diskgaugebyte
fly_io.instance.net.recv_bytes.countNumber of good bytes received by the interface.countbyte
fly_io.instance.net.recv_compressed.countNumber of correctly received compressed packets.count-
fly_io.instance.net.recv_drop.countNumber of packets received but not processed, e.g. due to lack of resources or unsupported protocol.countpacket
fly_io.instance.net.recv_errs.countTotal number of bad packets received on this network device.countpacket
fly_io.instance.net.recv_fifo.countReceiver FIFO overflow event counter.count-
fly_io.instance.net.recv_frame.countReceiver frame alignment errors.count-
fly_io.instance.net.recv_multicast.countMulticast packets received.countpacket
fly_io.instance.net.recv_packets.countNumber of good packets received by the interface.countpacket
fly_io.instance.net.sent_bytes.countNumber of good transmitted bytes.countbyte
fly_io.instance.net.sent_carrier.countNumber of frame transmission errors due to loss of carrier during transmission.count-
fly_io.instance.net.sent_colls.countNumber of collisions during packet transmissions.count-
fly_io.instance.net.sent_compressed.countNumber of transmitted compressed packets.count-
fly_io.instance.net.sent_drop.countNumber of packets dropped on their way to transmission, e.g. due to lack of resources.countpacket
fly_io.instance.net.sent_errs.countTotal number of transmit problems.count-
fly_io.instance.net.sent_fifo.countSent FIFO overflow event counter.count-
fly_io.instance.net.sent_packets.countNumber of packets successfully transmitted.countpacket
fly_io.instance.upReports 1 if the VM is reporting correctlygauge-
fly_io.instance.volume.sizeVolume size in bytes.gaugebyte
fly_io.instance.volume.usedPercentage of volume used.gaugebyte
fly_io.machine.countCount of running machinesgauge-
fly_io.machine.cpus.countNumber of cpusgauge-
fly_io.machine.gpus.countNumber of gpusgauge-
fly_io.machine.memoryMemory of a machinegaugemegabyte
fly_io.machine.swap_sizeSwap space to reserve for the Fly Machinegaugemegabyte
fly_io.machines_api.upWhether the check can access the machines API or notgauge-
fly_io.pg.database.sizeDatabase sizegaugebyte
fly_io.pg.replication.lagReplication laggauge-
fly_io.pg_stat.activity.countnumber of connections in this stategauge-
fly_io.pg_stat.activity.max_tx_durationmax duration in seconds any active transaction has been runninggaugesecond
fly_io.pg_stat.archiver.archived_countNumber of WAL files that have been successfully archivedgauge-
fly_io.pg_stat.archiver.failed_countNumber of failed attempts for archiving WAL filesgauge-
fly_io.pg_stat.bgwriter.buffers_allocNumber of buffers allocatedgauge-
fly_io.pg_stat.bgwriter.buffers_backendNumber of buffers written directly by a backendgauge-
fly_io.pg_stat.bgwriter.buffers_backend_fsyncNumber of times a backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write)gauge-
fly_io.pg_stat.bgwriter.buffers_checkpointNumber of buffers written during checkpointsgauge-
fly_io.pg_stat.bgwriter.buffers_cleanNumber of buffers written by the background writergauge-
fly_io.pg_stat.bgwriter.checkpoint_sync_timeTotal amount of time that has been spent in the portion of checkpoint processing where files are synchronized to disk, in millisecondsgaugemillisecond
fly_io.pg_stat.bgwriter.checkpoint_write_timeTotal amount of time that has been spent in the portion of checkpoint processing where files are written to disk, in millisecondsgaugemillisecond
fly_io.pg_stat.bgwriter.checkpoints_reqNumber of requested checkpoints that have been performedgauge-
fly_io.pg_stat.bgwriter.checkpoints_timedNumber of scheduled checkpoints that have been performedgauge-
fly_io.pg_stat.bgwriter.maxwritten_cleanNumber of times the background writer stopped a cleaning scan because it had written too many buffersgauge-
fly_io.pg_stat.bgwriter.stats_resetTime at which these statistics were last resetgauge-
fly_io.pg_stat.database.blk_read_timeTime spent reading data file blocks by backends in this database, in millisecondsgaugemillisecond
fly_io.pg_stat.database.blk_write_timeTime spent writing data file blocks by backends in this database, in millisecondsgaugemillisecond
fly_io.pg_stat.database.blks_hitNumber of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache)gauge-
fly_io.pg_stat.database.blks_readNumber of disk blocks read in this databasegauge-
fly_io.pg_stat.database.conflictsNumber of queries canceled due to conflicts with recovery in this database. Conflicts occur only on standby serversgauge-
fly_io.pg_stat.database.conflicts_confl_bufferpinNumber of queries in this database that have been canceled due to pinned buffersgauge-
fly_io.pg_stat.database.conflicts_confl_deadlockNumber of queries in this database that have been canceled due to deadlocksgauge-
fly_io.pg_stat.database.conflicts_confl_lockNumber of queries in this database that have been canceled due to lock timeoutsgauge-
fly_io.pg_stat.database.conflicts_confl_snapshotNumber of queries in this database that have been canceled due to old snapshotsgauge-
fly_io.pg_stat.database.conflicts_confl_tablespaceNumber of queries in this database that have been canceled due to dropped tablespacesgauge-
fly_io.pg_stat.database.deadlocksNumber of deadlocks detected in this databasegauge-
fly_io.pg_stat.database.numbackendsNumber of backends currently connected to this database. This is the only column in this view that returns a value reflecting current state; all other columns return the accumulated values since the last reset.gauge-
fly_io.pg_stat.database.stats_resetTime at which these statistics were last resetgauge-
fly_io.pg_stat.database.tup_deletedNumber of rows deleted by queries in this databasegauge-
fly_io.pg_stat.database.tup_fetchedNumber of rows fetched by queries in this databasegauge-
fly_io.pg_stat.database.tup_insertedNumber of rows inserted by queries in this databasegauge-
fly_io.pg_stat.database.tup_returnedNumber of rows returned by queries in this databasegauge-
fly_io.pg_stat.database.tup_updatedNumber of rows updated by queries in this databasegauge-
fly_io.pg_stat.database.xact_commitNumber of transactions in this database that have been committedgauge-
fly_io.pg_stat.database.xact_rollbackNumber of transactions in this database that have been rolled backgauge-
fly_io.pg_stat.replication.pg_current_wal_lsn_bytesWAL position in bytesgaugebyte
fly_io.pg_stat.replication.pg_wal_lsn_diffLag in bytes between master and slavegaugebyte
fly_io.pg_stat.replication.reply_timeSend time of last reply message received from standby servergauge-
fly_io.volume.block_sizeThe size of each memory block in bytesgaugebyte
fly_io.volume.blocks.countThe total number of blocks in the volumegauge-
fly_io.volume.blocks_availThe number of blocks available for data in the volumegauge-
fly_io.volume.blocks_freeThe total number of blocks free for data and root user opsgauge-
fly_io.volume.createdWhether the volume has been created or notgauge-
fly_io.volume.encryptedWhether the volume is encrypted or notgauge-
fly_io.volume.sizeThe size of the volume in GBgaugegigabyte

Official documentation

Official documentation for the Fly.io integration

Metric names and descriptions are the official Datadog integration definitions (Copyright Datadog, Inc., BSD-3-Clause), reproduced unedited. The full license terms are on the About page.