JAIME SEBASTIAN BURBANO VILLAVICENCIO
05/13/2024, 7:56 AMdocker compose -f docker-compose.yaml up
Note: I have almost not changed the compose file at all, just commented the hotrop example.
Every some seconds, the following error appears in clickhouse
signoz-clickhouse | 2024.05.13 07:45:46.188830 [ 47 ] {} <Error> ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 32, I/O error: Broken pipe, Stack trace (when copying this message, always include the lines below):
signoz-clickhouse |
signoz-clickhouse | 0. Poco::Net::SocketImpl::error(int, String const&) @ 0x00000000153a1b5f in /usr/bin/clickhouse
signoz-clickhouse | 1. Poco::Net::SocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a2bbd in /usr/bin/clickhouse
signoz-clickhouse | 2. Poco::Net::StreamSocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a5296 in /usr/bin/clickhouse
signoz-clickhouse | 3. Poco::Net::HTTPSession::write(char const*, long) @ 0x00000000153908b3 in /usr/bin/clickhouse
signoz-clickhouse | 4. Poco::Net::HTTPHeaderIOS::~HTTPHeaderIOS() @ 0x000000001538bbdb in /usr/bin/clickhouse
signoz-clickhouse | 5. Poco::Net::HTTPHeaderOutputStream::~HTTPHeaderOutputStream() @ 0x000000001538bf1f in /usr/bin/clickhouse
signoz-clickhouse | 6. DB::HTTPServerResponse::send() @ 0x0000000012942988 in /usr/bin/clickhouse
signoz-clickhouse | 7. DB::HTTPServerConnection::sendErrorResponse(Poco::Net::HTTPServerSession&, Poco::Net::HTTPResponse::HTTPStatus) @ 0x000000001293ecda in /usr/bin/clickhouse
signoz-clickhouse | 8. DB::HTTPServerConnection::run() @ 0x000000001293e97b in /usr/bin/clickhouse
signoz-clickhouse | 9. Poco::Net::TCPServerConnection::start() @ 0x00000000153a5a72 in /usr/bin/clickhouse
signoz-clickhouse | 10. Poco::Net::TCPServerDispatcher::run() @ 0x00000000153a6871 in /usr/bin/clickhouse
signoz-clickhouse | 11. Poco::PooledThread::run() @ 0x000000001549f047 in /usr/bin/clickhouse
signoz-clickhouse | 12. Poco::ThreadImpl::runnableEntry(void*) @ 0x000000001549d67d in /usr/bin/clickhouse
signoz-clickhouse | 13. ? @ 0x0000721d932f8609
signoz-clickhouse | 14. ? @ 0x0000721d9321d353
signoz-clickhouse | (version 24.1.2.5 (official build))
My problem is that I can get trace information in clickhouse but cannot get any hostmetrics. I have a local collector running in a different machine, which I can assure it is collecting data each 10 seconds (as I can see it in the logger), but this data does not seem to reach clickhouse DB.
I have no idea if it is related to the error shown above. Any help or guidance is appreciated.nitya-signoz
05/13/2024, 10:35 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/13/2024, 11:32 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/13/2024, 11:32 AMnitya-signoz
05/13/2024, 11:34 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/13/2024, 11:36 AMnitya-signoz
05/13/2024, 11:45 AMdocker logs signoz-otel-collector -f
JAIME SEBASTIAN BURBANO VILLAVICENCIO
05/14/2024, 9:03 AMResource SchemaURL: <https://opentelemetry.io/schemas/1.9.0>
Resource attributes:
-> host.name: Str(UEcollector)
-> os.type: Str(linux)
ScopeMetrics #0
ScopeMetrics SchemaURL:
InstrumentationScope otelcol/hostmetricsreceiver/cpu 0.98.0
Metric #0
Descriptor:
-> Name: system.cpu.time
-> Description: Total seconds each logical CPU spent on each mode.
-> Unit: s
-> DataType: Sum
-> IsMonotonic: true
-> AggregationTemporality: Cumulative
NumberDataPoints #0
Data point attributes:
-> cpu: Str(cpu0)
-> state: Str(user)
StartTimestamp: 2024-05-07 11:29:56 +0000 UTC
Timestamp: 2024-05-14 09:00:13.646666601 +0000 UTC
Value: 2580.600000
JAIME SEBASTIAN BURBANO VILLAVICENCIO
05/14/2024, 9:10 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/14/2024, 9:11 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/14/2024, 9:14 AMJAIME SEBASTIAN BURBANO VILLAVICENCIO
05/14/2024, 9:19 AMnitya-signoz
05/14/2024, 10:27 AM