CSV File Naming Convention

CSV files generated by Legacy Orchestrator are named following a convention. The following example explains the naming convention.

Note: PM Collect types use local time zone naming convention and PM Agent types use Coordinated Universal Time (UTC) naming convention.

Example:

G274-0010_history_2024-04-22_15h00m00s_paa_all_60.csv.gz

Where:

• G274-0010: Unit’s serial number.
• history: Identifies a history file (the only type available).
• 2024-04-22: Date the file was regenerated (yyyy-mm-dd).
• 15h00m00s (CSV file of PM Collect): Time the file was generated (hh-mm-ss).
  • Note: 15h00m00sZ represents CSV file of PT Agent.
• paa: Type of data
  • PM Collect Data: flowmeter, paa, port, policy, regulator, sfp, shaper, soam_dmm, soam_pl, soam_sa, soam_sa_metrics, soam_slm, system_health, twamp.
  • PT Agent Data: TWAMP (stateful), 2xOneWay, Echo-ICMP, Echo-UDP, ETH-DM, ETH-LB, ETH-VS, TWAMP-SL (stateless).
• all: Indicates that ALL configured instances are included in the file for the requested periods. This is the only available option.
• 60: PM Collect and PT Agent types.
  • PM Collect Types (paa, flowmeter, port, etc.): "60" is the CSV Collection period (expressed in seconds).
  • PT Agent Types (TWAMP, 2xOneWay, Echo-ICMP, etc.): "60" is the CSV Producer period (expressed in seconds).
• csv.gz: File type: CSV (comma-separated values).