Splunk Observability Cloud

cat not send data/metric form Apache http server to Splunk Observability Cloud

CaryLinW
Explorer

Hi, All

   I got the problem when try to  send data(metric) form Apache http server to Splunk Observability Cloud 

My OS : Centos7 and I have got the Metric of CPU/ Memory 

My Apache Version : Apache/2.4.6 and  server stats is working (http://localhost:8080/server-status?auto)

I have referenced the follow document  and update the config file /etc/otle/collector/agent_config.yaml

but I did not get any metrics about Apache !!

https://docs.splunk.com/observability/en/gdi/opentelemetry/components/apache-receiver.html

https://docs.splunk.com/observability/en/gdi/monitors-hosts/apache-httpserver.html

Anybody kindly do me a favor to fix it

thanks in adeavne

#observability

 

 

Labels (1)
0 Karma
1 Solution

CaryLinW
Explorer

receivers:
#Apache Cary
apache:
endpoint: "http://localhost:80/server-status?auto"
collection_interval: 10s
#Apache Cary

 

service:
telemetry:
metrics:
address: "${SPLUNK_LISTEN_INTERFACE}:8888"
extensions: [health_check, http_forwarder, zpages, smartagent]
pipelines:
traces:
receivers: [jaeger, otlp, zipkin]
processors:
- memory_limiter
- batch
- resourcedetection
#- resource/add_environment
exporters: [sapm, signalfx]
# Use instead when sending to gateway
#exporters: [otlp, signalfx]
metrics:
##Apache Cary receivers: [hostmetrics, otlp, signalfx]
receivers: [hostmetrics, otlp, signalfx, apache]
processors: [memory_limiter, batch, resourcedetection]
exporters: [signalfx]
# Use instead when sending to gateway
#exporters: [otlp]

View solution in original post

0 Karma

bishida
Splunk Employee
Splunk Employee

Hi,

Here are a couple of ideas for quick checks:
1. Did you restart the collector after changing agent_config.yaml?
2. Did you add the new apache receiver to the metrics pipeline?
3. Did you check for apache.* metrics using the metric finder? Or check for data in the apache built-in dashboard?

0 Karma

CaryLinW
Explorer

Hi,

thanks for your replying

1. Did you restart the collector after changing agent_config.yaml? 

ans : YES , I have restarted collector after changing agent_config.yaml?

2. Did you add the new apache receiver to the metrics pipeline?

I think I have added it ,as the doument


3. Did you check for apache.* metrics using the metric finder? Or check for data in the apache built-in dashboard?

I have checked  for apache.* metrics , but no anything

0 Karma

bishida
Splunk Employee
Splunk Employee

Hi,

Can you share the part of your yaml where you define the apache receiver and also share the part that contains your service pipeline? 

0 Karma

CaryLinW
Explorer

receivers:
#Apache Cary
apache:
endpoint: "http://localhost:80/server-status?auto"
collection_interval: 10s
#Apache Cary

 

service:
telemetry:
metrics:
address: "${SPLUNK_LISTEN_INTERFACE}:8888"
extensions: [health_check, http_forwarder, zpages, smartagent]
pipelines:
traces:
receivers: [jaeger, otlp, zipkin]
processors:
- memory_limiter
- batch
- resourcedetection
#- resource/add_environment
exporters: [sapm, signalfx]
# Use instead when sending to gateway
#exporters: [otlp, signalfx]
metrics:
##Apache Cary receivers: [hostmetrics, otlp, signalfx]
receivers: [hostmetrics, otlp, signalfx, apache]
processors: [memory_limiter, batch, resourcedetection]
exporters: [signalfx]
# Use instead when sending to gateway
#exporters: [otlp]

0 Karma

CaryLinW
Explorer

hi

  I thank the problem is fixed

thanks  for your supporting

 

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to February Tech Talks, Office Hours, and Webinars!

💌 Keep the new year’s momentum going with our February lineup of Community Office Hours, Tech Talks, ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Incident Response: Reduce Incident Recurrence with Automated Ticket Creation

Culture extends beyond work experience and coffee roast preferences on software engineering teams. Team ...