https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
a
@Prashant Shahi can you verify this?
✅ 1
@Srikanth Chekuri should we add 
httpcheck
receivers at otel-collector config or otel-collector-metrics config? https://signoz.io/docs/monitor-http-endpoints/#steps-to-monitor-the-health-of-the-http-endpoints
s
This should ideally go to otel-collector-metrics but it also works with otel-collector config if there is only one main collector.
a
moved it to otel-collector-metrics, still nothing showing up
s
Just to make sure we are on the same page, where are you verifying if this is working or not?
a
this does not work
I tried in both configuration files
s
How are you verifying?
a
I updated the otel-collector-metrics and restarted the containter
went to the interface, and nowthing shows up
s
went to the interface, and nowthing shows up
Which interface are you referring to?
You are looking at the wrong place. I am not sure if you understand the functionality of the monitoring HTTP endpoint. It checks whether the HTTP call to the endpoint returns success with the status code. It doesn’t create any traces. There will be a metric name with 
httpcheck_status
which you can verify in the dashboard panel and can set alerts on but the traces is different altogether.
a
I think I understand
it should query that endpoint every X seconds
where can I see the statistics of that?
s
By statistics if you mean the metric value (either 1 or 0), you go to dashboards -> create new dashboard -> add panel -> time series -> and type 
httpcheck_status
in the metric name text box.
a
its not showing there
p
works as expected
a
it does not work
p
@André Ferreira can you share how you have overridden the config?
a
yes
p
okay, looks good.
Have you restarted the container with the updated config?
a
yes
p
In case of Docker, often times config changes do not reflect when restarted directly.
Try stopping => removing the container, and start again.
a
what?
p
Copy code
docker stop clickhouse-setup-otel-collector-metrics-1
docker rm clickhouse-setup-otel-collector-metrics-1

./install.sh
I verified that it works in K8s. Let me check that in Docker as well.
a
restarted
lets lee
see
p
wait for the interval duration.. and retry creating metrics in dashboard
a
at least the option now shows up in the dropdown
but still no data
p
hover over the widget
a
this should be generating datapoints every 5 seconds on the 1st API and every 15 seconds on the second API
why are there so many?
this is super hard to read
how can I filter the statuses?
p
use where condition to filter URLs, and use Legends to format the labels.
a
does not work
grouping also does not work
p
grouping only works in aggregator function.. it does not work for 
NOOP
a
is this correct with NOOP?
also is it possible that the condition for testing an endpoint is an expected json response instead of just 200?
s
No, that’s not possible as of now.
60 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by