department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Investigate F5 network layers between vets-api and BGS (Benefits Gateway Services) #45349

Open joeniquette opened 2 years ago

joeniquette commented 2 years ago

Description

F5 network layers with BGS seem to be an issue, can someone track this down Track down a contact for the BGS service to assist with network tracing (Joe N. and Zach)

Acceptance Criteria

How to configure this issue

zachclarity commented 2 years ago

https://dsva.slack.com/archives/CJYRZK2HH/p1661185087672539

oseasmoran73 commented 2 years ago

No control upstream via VA What tools/query can we use? Can we curl certain endpoints? TCP? Traceroute? Between vets-api / BGS?

Where does BGS lie? benefits gateway services

oseasmoran73 commented 2 years ago

https://depo-platform-documentation.scrollhelp.site/developer-docs/benefits-gateway-service

https://grafana.vfs.va.gov/d/000000032/forward-proxy?orgId=1

https://grafana.vfs.va.gov/d/sZP0EYh7z/bgs?orgId=1

oseasmoran73 commented 2 years ago

Compiled a list of questions and reached out to John (found in the document). Waiting to hear back if he is corerct POC

oseasmoran73 commented 2 years ago

https://github.com/department-of-veterans-affairs/vsp-infra-evss-bgs-split

https://dsva.pagerduty.com/service-directory/P5Q2OCZ/service-dependencies

Reached out to additional folks in addition to John to try and get more information

oseasmoran73 commented 2 years ago

Eric provided a different contact. Reached out to them and they forwarded the questions over to correct party

Given the amount of hoops and response time for this ticket, marking it as blocked until these parties respond

oseasmoran73 commented 2 years ago

I got a reply and looks like there is a splunk url given. I was not really able to make out the information. Will figure out with the team where to store that information and potentially how we can leverage it

little-oddball commented 1 year ago

@oseasmoran73 @npeterson54 Is this still an in-progress ticket or backlog?

oseasmoran73 commented 1 year ago

This is under blocked/has-dependency. I reached to a couple of folks and they responded with a splunk URL. It did not have much information relevant (to my knowledge) so was not sure how much more I can/is there do

little-oddball commented 1 year ago

This is under blocked/has-dependency. I reached to a couple of folks and they responded with a splunk URL. It did not have much information relevant (to my knowledge) so was not sure how much more I can/is there do

@oseasmoran73 - ok, have y'all discussed next steps? Does what has been received cover the AC? Does it need to be circled back to @ericboehs and @joeniquette?

oseasmoran73 commented 1 year ago

Revisited conversation with folks before blockage. Will be reviewing this ticket as its part of new Epic and what are next steps/refine again with current information on Monday 12/5

npeterson54 commented 1 year ago

Removing tech team 3 label from story as we will not be working on this