# Has error making http request: Get "http://npipe/state": been fixed yet for Elastic Agent 7.10.2?

**URL:** <https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722>\
**Category:** Beats\
**Tags:** elastic-agent\
**Created:** [March 9, 2021, 4:27pm UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722 "2021-03-09T16:27:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dvo](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@dvo](https://discuss.elastic.co/u/dvo)\
**Post date:** [March 9, 2021, 4:27pm UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/1 "2021-03-09T16:27:52Z")

</div>

I'm testing a single Windows agent, and Kibana is littered with these errors, and it looks bad to the potential customer. I've got to get it cleaned up.

_error making http request: Get "[http://npipe/state](http://npipe/state)": open \default-filebeat: The system cannot find the file specified._

I saw someone asked a question about this in December, and it was identified as a bug. Is there a fix yet?

Thank you!

This is my current policy:

id: 2963c470-7162-11eb-b02b-ab5e9f3e32c6  
revision: 9  
outputs:  
default:  
type: elasticsearch  
hosts:  
- '[https://34.121.222.170:9200](https://34.121.222.170:9200)'  
agent:  
monitoring:  
enabled: true  
use\_output: default  
logs: true  
metrics: true  
inputs:

- id: 7d4080d0-72d2-11eb-a8fc-114b4161e7c0  
name: windows-1  
revision: 4  
type: windows/metrics  
use\_output: default  
meta:  
package:  
name: windows  
version: 0.2.11  
data\_stream:  
namespace: default  
streams:
  - id: windows/metrics-windows.perfmon  
data\_stream:  
dataset: windows.perfmon  
type: metrics  
period: 5m  
perfmon.ignore\_non\_existent\_counters: true  
metricsets:
    - perfmon  
perfmon.queries:
    - instance:
      - '\*'  
counters:
      - name: '% Processor Time'  
field: cpu\_perc  
format: float
      - name: Working Set  
object: Process  
perfmon.group\_measurements\_by\_instance: false

  - id: windows/metrics-windows.service  
data\_stream:  
dataset: windows.service  
type: metrics  
period: 5m  
metricsets:
    - service  
fleet:  
kibana:  
protocol: https  
hosts:

  - '34.121.222.170:5601'

---

<div class="post-metadata">

**Author:** ![MarianaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marianad/32/42687_2.png) [@MarianaD](https://discuss.elastic.co/u/MarianaD)\
**Post date:** [March 9, 2021, 6:28pm UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/2 "2021-03-09T18:28:47Z")

</div>

hi @dvo , I think you mean [[Ingest Management] Monitoring metrics using npipe does not work · Issue #22957 · elastic/beats (github.com)](https://github.com/elastic/beats/issues/22957).  
This fix seems to have made it to 7.11. Have you tried this version?

---

<div class="post-metadata">

**Author:** ![dvo](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@dvo](https://discuss.elastic.co/u/dvo)\
**Post date:** [March 10, 2021, 4:22am UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/3 "2021-03-10T04:22:31Z")

</div>

Yes, that's what I found on git as well. So there's no fix for 7.10.X agents---it requires upgrading the whole smash to 7.11 to fix? I say this b/c unless something has changed in the last 2 weeks, 7.11 Elastic Agents won't register w/7.10.2 backend.

Please tell me there's a workaround for this that can be applied to just the agent!

Thanks for your time Mariana

---

<div class="post-metadata">

**Author:** ![MarianaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marianad/32/42687_2.png) [@MarianaD](https://discuss.elastic.co/u/MarianaD)\
**Post date:** [March 10, 2021, 11:34am UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/4 "2021-03-10T11:34:14Z")

</div>

hi @dvo , I see in the initial discuss ticket, my colleague suggests disabling metrics monitoring using `agent.monitoring.metrics` in order to clear the errors, have you tried that?  
It's most likely not possible to enroll newer agents to older stack.

---

<div class="post-metadata">

**Author:** ![dvo](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@dvo](https://discuss.elastic.co/u/dvo)\
**Post date:** [March 10, 2021, 2:25pm UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/5 "2021-03-10T14:25:05Z")

</div>

Hi, yes I did, but does that disable metric colkection, or just the monitoring of collecting the metrics? Either way, the syntax for doing that in the config would have been helpful. I'd be willing to try it if I knew what to type.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 7, 2021, 4:25pm UTC](https://discuss.elastic.co/t/has-error-making-http-request-get-http-npipe-state-been-fixed-yet-for-elastic-agent-7-10-2/266722/6 "2021-04-07T16:25:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
