You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logging is kinda misleading and incorrect. I started jira sensor in a single sensor mode, and this is correctly reflected:
2025-03-12 20:34:28,486 INFO [-] Running in single sensor mode, using a single sensor partitioner...
2025-03-12 20:34:28,490 INFO [-] Setting up container to run 1 sensors.
2025-03-12 20:34:28,490 INFO [-] Sensors list - ['jira.JIRASensorForAPIv2'].
2025-03-12 20:34:28,490 INFO [-] (PID:1) SensorContainer started.
2025-03-12 20:34:28,492 INFO [-] Running sensor jira.JIRASensorForAPIv2
2025-03-12 20:34:28,550 INFO [-] Connected to amqp://admin:**@stackstorm-ha-1704186131-rabbitmq:5672//
2025-03-12 20:34:28,669 INFO [-] Sensor jira.JIRASensorForAPIv2 started
2025-03-12 20:34:30,153 INFO [-] Found config for sensor "JIRASensorForAPIv2"
2025-03-12 20:34:30,155 INFO [-] Watcher started
2025-03-12 20:34:30,155 INFO [-] Running sensor initialization code
but in the next poll it states:
2025-03-12 20:34:48,686 INFO [-] sensor jira.JIRASensorForAPIv2 is not assigned to this partition. Ignoring update.
Although the sensor runs correctly, the above log line is incorrect.
My config:
The logging is kinda misleading and incorrect. I started jira sensor in a single sensor mode, and this is correctly reflected:
but in the next poll it states:
Although the sensor runs correctly, the above log line is incorrect.
My config:
The text was updated successfully, but these errors were encountered: