kentik Product Updates logo
Back to Homepage Subscribe to Updates

Product Updates

Latest features, improvements, and product updates on Kentik's Network Observability platform.

Labels

  • All Posts
  • Improvement
  • Hybrid Cloud
  • Core
  • Service Provider
  • UI/UX
  • Synthetics
  • Insights & Alerting
  • DDoS
  • New feature
  • BGP Monitoring
  • MyKentik Portal
  • Agents & Binaries
  • Kentik Map
  • API
  • BETA
  • Flow
  • SNMP
  • NMS
  • AI

Jump to Month

  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • July 2021
  • June 2021
  • May 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • October 2020
  • September 2020
  • June 2020
  • February 2020
  • August 2019
  • June 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • September 2018
  • August 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • April 2016
CoreFlow
2 years ago

Flow Ingest: Support for Flow timestamps

Kentik now supports the collection of the NetFlow and IPFIX timestamp fields (starting kproxy v7.38.0). The additional 3 fields are available to be viewed in the Raw Flow Viewer:

  • Flow Start - Timestamp of the flow start
  • Flow End - Timestamp of the flow end
  • Duration - Calculated duration of the flow as Flow Start - Flow End

NetFlow v5 and v9

In the case of the NetFlow v5 and v9, Start and End Flow timestamps are calculated using System Uptime and Unix Seconds fields from the NetFlow header and the following fields from Flow records:

Field TypeValueLength (bytes)Description
LAST_SWITCHED214System uptime at which the last packet of this flow was switched
FIRST_SWITCHED224System uptime at which the first packet of this flow was switched

IPFIX

In the case of the IPFIX, the timestamps are determined in the following two ways:

  1. Using flowStartSysUpTime, flowEndSysUpTime and systemInitTimeMilliseconds fields:

    IDNameTypeDescriptionUnits
    21flowEndSysUpTimeunsigned32The relative timestamp of the last packet of this Flow. It indicates the number of milliseconds since the last (re-)initialization of the IPFIX Device (sysUpTime). sysUpTime can be calculated from systemInitTimeMilliseconds.milliseconds
    22flowStartSysUpTimeunsigned32The relative timestamp of the first packet of this Flow. It indicates the number of milliseconds since the last (re-)initialization of the IPFIX Device (sysUpTime). sysUpTime can be calculated from systemInitTimeMilliseconds.milliseconds

    Both fields in the description refer to the additional field which is equivalent to the SysUpTime:

    IDNameTypeDescriptionUnits
    160systemInitTimeMillisecondsdateTimeMillisecondsThe absolute timestamp of the last (re-)initialization of the IPFIX Device.milliseconds


  2. Using some of the IPFIX-specific fields for the flow start and flow end timestamps. Not all device’s IPFIX implementation used these fields, but if they are present, they are preferred and used:

    IDNameTypeDescriptionUnits
    150flowStartSecondsdateTimeSecondsThe absolute timestamp of the first packet of this Flow.seconds
    151flowEndSecondsdateTimeSecondsThe absolute timestamp of the last packet of this Flow.seconds
    152flowStartMillisecondsdateTimeMillisecondsThe absolute timestamp of the first packet of this Flow.milliseconds
    153flowEndMillisecondsdateTimeMillisecondsThe absolute timestamp of the last packet of this Flow.milliseconds
    154flowStartMicrosecondsdateTimeMicrosecondsThe absolute timestamp of the first packet of this Flow.microseconds
    155flowEndMicrosecondsdateTimeMicrosecondsThe absolute timestamp of the last packet of this Flow.microseconds
    156flowStartNanosecondsdateTimeNanosecondsThe absolute timestamp of the first packet of this Flow.nanoseconds
    157flowEndNanosecondsdateTimeNanosecondsThe absolute timestamp of the last packet of this Flow.nanoseconds
    158flowStartDeltaMicrosecondsunsigned32This is a relative timestamp only valid within the scope of a single IPFIX Message. It contains the negative time offset of the first observed packet of this Flow relative to the export time specified in the IPFIX Message Header.microseconds
    159flowEndDeltaMicrosecondsunsigned32This is a relative timestamp only valid within the scope of a single IPFIX Message. It contains the negative time offset of the last observed packet of this Flow relative to the export time specified in the IPFIX Message Header.microseconds

sFlow

sFlow is packet sampling technology, which means that there is no flow, hence no flow start or flow end time.

sFlow also does not contain any timestamp, so the behavior is the following:

  • Flow Start: save the time of arrival/processing of the sFlow packet
  • Flow End - same as Flow Start
  • Duration - 0

Raw Flow Viewer

In the Raw Flow Viewer, these additional flow timestamps need to be selected as Dimensions to be shown in the output, as shown below:


Avatar of authorDuĊĦan Pajin