[Bug]: version upgrade from 2.29.0 to 2.30.0 causing log flood. #849
Comments
|
Thanks for your report. We are taking a look |
|
Could you please share your package.json with me? Thank you |
|
|
Thanks for sharing. We are taking a look at the target libraries.
This log message is not an INFO log, it's a warning. Could you please double check your statement? |
|
Could you please share a code snippet how you are using ioredis and kafkajs when the warning appears? |
|
This seems like not an issue with ioredis and kafkajs because I encounter similar issue with a service using different dependencies. |
|
Ok thanks. It might be that there is an issue, but to trigger the warning, what are you doing in your code? Could you please share a snippet? |
|
I have setup instana port and host in env, and rest I initialize the instana as shown in the docs itself That is basically it. |
|
What is Can you please share an example application? My example app is: There are no warnings. There must be something in your application which triggers the warning. |
|
Thanks for the hint, I will try to replicate with a simple app and post. |
|
The behavior exist when I use index.js require("@instana/collector")();
const { Kafka } = require("kafkajs");
const { v4: uuidv4 } = require("uuid");
const express = require("express");
const app = express();
const kafka = new Kafka({
clientId: "my-kafka-producer",
brokers: ["localhost:9092"],
});
const producer = kafka.producer();
app.use(express.json());
app.post("/", async (req, res) => {
try {
await producer.connect();
await producer.send({
topic: "my-kafka-topic",
acks: 1,
compression: 0,
messages: [
{
value: JSON.stringify({
key: uuidv4(),
createdAt: Date.now().toString(),
}),
},
],
});
await producer.disconnect();
res.status(201).send("Message sent successfully");
} catch (error) {
console.error("Error producing message:", error);
res.status(500).send("Internal Server Error");
}
});
app.listen(3000, () => {
console.log("Server is running on port 3000");
});package.json {
"name": "nodejstest",
"author": "",
"scripts": {
"start": "node index.js"
},
"dependencies": {
"@instana/collector": "^2.30.0",
"express": "^4.18.2",
"kafkajs": "^2.2.4",
"uuid": "^9.0.0"
}
}docker-compose.yml version: "3"
services:
zookeeper:
image: wurstmeister/zookeeper
container_name: zookeeper
ports:
- "2181:2181"
kafka:
image: wurstmeister/kafka
container_name: kafka
ports:
- "9092:9092"
environment:
KAFKA_ADVERTISED_HOST_NAME: localhost
KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181 |
|
Thanks for sharing. Could you please share your log?
I think you are running into this warning because the Instana collector cannot connect to the Instana agent and is not fully initialized. And then the log is flooded when there is already traffic. |
|
Hi! We've released a potential fix in v2.30.1. Could you please check if the problem is resolved? Thank you |
|
@kirrg001 The new version has resolved our problem. I appreciate the prompt assistance. |
Problem Description
I upgrade from 2.29.0 to 2.30.0 and after that
is being logged as INFO a lot of time, which causes issues in service performance
Short, Self Contained Example
Usage
Node.js Version
^18.14.0
package.json
{ "name": "service", "version": "0.1.0", "private": true, "description": "", "main": "", "scripts": { "build": "tsc" }, "engines": { "node": "^18.14.0" }, "license": "UNLICENSED", "dependencies": { "@instana/collector": "^2.30.0" } }The text was updated successfully, but these errors were encountered: