# Golang + Request Attributes on request to Public Networks

**URL:** <https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626>\
**Category:** Open Q&A\
**Tags:** services-classic, network-monitoring, request-attributes\
**Created:** [September 22, 2022, 5:24pm UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626 "2022-09-22T17:24:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric\_miles](https://avatars.discourse-cdn.com/v4/letter/e/ecb155/32.png) [@eric\_miles](https://community.dynatrace.com/u/eric_miles)\
**Post date:** [September 22, 2022, 5:24pm UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/1 "2022-09-22T17:24:38Z")

</div>

We have Golang k8s services making requests to public networks and we’d like to expose some http request headers as Request Attributes on the public network service (they have been made top level services).&nbsp; This works for our Node k8s services, but not our Golang.&nbsp; Upon attempting to create the Request Attributes, there is a warning message “Only works for Java, DotNet, and NodeJS based technologies”.&nbsp; Anyone know what the reasoning is for this?&nbsp; Why not Golang or other technologies?

Is there a way to get around this so we can surface these values as Request Attributes?

 ![image.png](https://global.discourse-cdn.com/dynatrace/original/3X/8/a/8a9a413c5a7675260165a60efd351ce1d2230399.png)

---

<div class="post-metadata">

**Author:** ![\_Alexander](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/_alexander/32/23720_2.png) [@\_Alexander](https://community.dynatrace.com/u/_Alexander)\
**Post date:** [October 25, 2022, 10:09am UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/2 "2022-10-25T10:09:07Z")

</div>

Status: Accepted

[@eric\_miles](https://community.dynatrace.com/user/34815)&nbsp;we will add&nbsp;the&nbsp;ability to capture request/response headers on outgoing web requests and make them available via the request attribute source

---

<div class="post-metadata">

**Author:** ![eric\_miles](https://avatars.discourse-cdn.com/v4/letter/e/ecb155/32.png) [@eric\_miles](https://community.dynatrace.com/u/eric_miles)\
**Post date:** [October 26, 2022, 1:38pm UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/3 "2022-10-26T13:38:58Z")

</div>

That’s great news!&nbsp; Any idea of timetable for this inclusion?&nbsp; Weeks, month, multiple months?

---

<div class="post-metadata">

**Author:** ![\_Alexander](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/_alexander/32/23720_2.png) [@\_Alexander](https://community.dynatrace.com/u/_Alexander)\
**Post date:** [October 27, 2022, 1:19pm UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/4 "2022-10-27T13:19:29Z")

</div>

Hi&nbsp;[@eric\_miles](https://community.dynatrace.com/user/34815)&nbsp;, it will take rather multiple months. We will provide more feedback once we have a target release.

---

<div class="post-metadata">

**Author:** ![r\_weber](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/r_weber/32/24884_2.png) [@r\_weber](https://community.dynatrace.com/u/r_weber)\
**Post date:** [May 13, 2024, 3:54pm UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/5 "2024-05-13T15:54:48Z")

</div>

[@\_Alexander\_](https://community.dynatrace.com/user/4565)&nbsp;did this ever make it?

---

<div class="post-metadata">

**Author:** ![\_Alexander](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/_alexander/32/23720_2.png) [@\_Alexander](https://community.dynatrace.com/u/_Alexander)\
**Post date:** [May 24, 2024, 9:41am UTC](https://community.dynatrace.com/t/golang-request-attributes-on-request-to-public-networks/36626/6 "2024-05-24T09:41:11Z")

</div>

[@r\_weber](https://community.dynatrace.com/user/35901) unfortunately not as requested for with this question. With Grail and the new Dynatrace Platform, we will enable users to interact with telemetry data in a completely different way.&nbsp;In connection with this, the concept of request attributes is being reconsidered, but the final concept is not yet ready.
