Skip to content

F5 Journeys Migration Utility - migrate or upgrade BIG-IP into new F5 platforms

active 2023-08-172026-02-18 (UTC)

Complete coverage26,630 / 26,630 hourly files (100%) · 2 absent upstream2023-08-152026-08-28 (UTC)
Events
199
Pushes
8
Pull requests
0
Issues
69
Stars
29
Forks
5

Activity over time

Daily event counts in the loaded window

Line chart, 917 days from 2023-08-17 to 2026-02-18. Pushes: 8 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 69 total, peak 16 in a day. Comments: 81 total, peak 20 in a day. Stars: 29 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue#134azahajkiewicz2026-02-11 17:35
    [BUG]journey sees my virtuals servers as no compliant with AS3
  • Issue#122azahajkiewicz2026-02-11 17:33
    BIG problem with migrating config form BIG IP 5200 to new r5000 series
  • Issue comment#122azahajkiewicz2026-02-11 17:33
    BIG problem with migrating config form BIG IP 5200 to new r5000 series
  • Issue#114azahajkiewicz2026-02-11 17:10
    [FEAT] Update JOURNEYS to offer updated rSeries tenant version support (through v15.1.9)
  • Issue#153Mansoormohammed892025-11-26 17:48
    [BUG] Configuration loading failed | Errno 128
  • Issue comment#143marcofilippetti2025-11-26 11:55
    [BUG] Please provide support for TMOS 17.5 and F5OS 1.8.0
  • Issue comment#138rmaliszewskif52025-11-12 20:57
    [BUG] Error in Journeys 4.2.0 - s.detail[Object.keys(...)[0]].join is not a function
  • Issue#150rmaliszewskif52025-10-24 09:36
    [BUG] 4.2.1 postgres 18 issue
  • Issue#150natebarkei2025-10-23 20:17
    [BUG] 4.2.1 postgres 18 issue
  • Issue#150natebarkei2025-10-23 20:17
    [BUG] 4.2.1 postgres 18 issue
  • Issue#150natebarkei2025-10-23 20:17
    [BUG] 4.2.1 postgres 18 issue
  • Issue#148nandiblumix2025-07-23 10:57
    [BUG] Is there any requirement for bigip_parser for parsing the UCS using Journeys Tool ?
  • Issue comment#146JustinStear2025-06-05 01:37
    [BUG]Images From Bundle fail by default via install.sh
  • Issue comment#142azahajkiewicz2025-06-03 12:22
    [BUG] storage issue, unable to load the config after upload the ucs into journeys tool
  • Issue#142azahajkiewicz2025-06-03 12:22
    [BUG] storage issue, unable to load the config after upload the ucs into journeys tool
  • Issue comment#145azahajkiewicz2025-06-03 12:13
    [FEAT]Allow to erase local account password from ucs
  • Issue#145SamCouvent2025-06-03 09:17
    [FEAT]Allow to erase local account password from ucs
  • Issue#144author-keita2025-05-26 06:51
    [FEAT]Integrate iSeries to rSeries with dividing Route Domain
  • Issue#143jackf2422025-05-14 19:22
    [BUG] Please provide support for TMOS 17.5 and F5OS 1.8.0
  • Issue#142kvlnarasimharao2025-03-25 21:01
    [BUG] storage issue, unable to load the config after upload the ucs into journeys tool
  • Issue#141sidiov2025-01-24 21:47
    [BUG]APM local user database does not bring over users
  • Issue#140shujali2024-11-06 12:47
    Deployment guide to deploy Journeys on Kubernetes or Openshift
  • Issue#140shujali2024-10-31 20:38
    Deployment guide to deploy Journeys on Kubernetes or Openshift
  • Issue comment#139azahajkiewicz2024-10-28 18:38
    Journeys deploy fails to get the defaults_from for clientssl profiles
  • Issue comment#139sdaynjax2024-10-28 18:09
    Journeys deploy fails to get the defaults_from for clientssl profiles

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 29 stars here means stars gained during the window, not the repo's star count.