Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
route77
Explorer
Jump to solution

Skyline Jumbo Hotfix Take

Hello Community,

I'm trying to monitor Jumbo Hotfix Takes on multiple GW. I'm creating a new dashboard parsing data from Skyline. What i've noticed is that CP provides FW Build No e.g 997000046 that corresponds to each installed take (Take 99) in this case. However for all other values i need to manually map each FW build with the take e,g.:

996000055 Take 130
 
996000077 Take 170
 
996000062 Take 139
 
996000065 Take 150
 
996000070 Take 156
 
997000012 Take 26
 
997000024 Take 53
 
997000030 Take 65
 
997000037 Take 84
 
997000039 Take 89
 
997000043 Take 92
 
997000045 Take 98
 
997000046 Take 99
 
997000049 Take 105
 
996000033 Take 87


First of all i would like to confirm that this is the proper way to do this and, secondly if there is any other way to parse this data from CP.

0 Kudos
1 Solution

Accepted Solutions
David_Evans
Collaborator

I am able to pull the jumbo with this query.


deployment_package_info{environment="$d_environment", host_name="$d_hostname"}

I convert the field Build to a number, change the name to Jumbo,   sort on it and I get a list that looks like this.     I do get some garbage in there sometimes at some jumbo versions... like jumbo 950.....   I've never dug into why because the "real" numbers are in there.

 

Screenshot 2025-07-24 080228.png

View solution in original post

(1)
4 Replies
Sven_Glock
Advisor

When using Skyline this is the actual way it goes. I already asked  per RFE for improvement and as far as I remember it is part of the roadmap

0 Kudos
(1)
David_Evans
Collaborator

I am able to pull the jumbo with this query.


deployment_package_info{environment="$d_environment", host_name="$d_hostname"}

I convert the field Build to a number, change the name to Jumbo,   sort on it and I get a list that looks like this.     I do get some garbage in there sometimes at some jumbo versions... like jumbo 950.....   I've never dug into why because the "real" numbers are in there.

 

Screenshot 2025-07-24 080228.png

(1)
route77
Explorer

Thanks David, This suits more with my concept. I can also combine it with major versions and hardware_model

0 Kudos
route77
Explorer

Thanks David! This suits my queries much better and is easier to combine it with major versions and hardware_model.

0 Kudos
Upcoming Events

    CheckMates Events