Label f5_virtual_server_destination is using Name when it should use Address
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- python
- Domain
- observability-sre
Research direction
Run the two tmsh commands in the reproduction steps, creating the named virtual address before the virtual server. Trace how the f5_virtual_server_info metric sets f5_virtual_server_destination, including the AS3 virtual_address case. Done means the label uses /Common/192.168.254.254:80 rather than /Common/myCoolAddress:80.
Written by the indexing model from the issue text.
Description
f5_virtual_server_info metric label f5_virtual_server_destination is using Name when it should use Address
To Reproduce
Create a virtual address object before creating a virtual server with that IP address which has a name other than the IP address:
tmsh create ltm virtual-address myCoolAddress address 192.168.254.254
tmsh create ltm virtual myCoolVirtual destination 192.168.254.254:80
Expected behavior
f5_virtual_server_info metric label f5_virtual_server_destination should contain an IP address:
f5_virtual_server_info{...f5_virtual_server_destination="/Common/192.168.254.254:80"...}
Current Behavior
f5_virtual_server_info metric label f5_virtual_server_destination contains the name of the virtual address, not the IP:
f5_virtual_server_info{...f5_virtual_server_destination="/Common/myCoolAddress:80"...}
This manifests when AS3 is creating a virtual server using a virtual_address class (often used to specify dynamic routing advertisement) but it can be replicated outside AS3 with those two commands above.
- Dominant language
- Python
- Stars
- 106
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
All issues in f5devcentral/application-study-tool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100