Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silence unneeded Azure SDK internal logging #21557

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

danotorrey
Copy link
Contributor

@danotorrey danotorrey commented Feb 6, 2025

https://github.com/Graylog2/graylog-plugin-enterprise/pull/9544 updates the Azure SDK, and some additional internal unneeded SDK log messages (for MessageFlux) are now surfacing during successful multi-Graylog node partition load balancing operations. This PR silences those, since we have our own partition change logging.

When starting up a second Graylog node and a partition is transitioned to that node:

2025-02-06 14:17:15,010 INFO : org.graylog.enterprise.integrations.azure.external.AzureLogsProcessor - Input [[Azure Event Hubs/Event Hubs/67a3eecc62e4bb171b9760dd]] is now receiving on partition [0].
2025-02-06 14:17:15,610 WARN : com.azure.core.amqp.implementation.MessageFlux - {"az.sdk.message":"Setting next mediator and waiting for activation.","messageFlux":"mf_b4fd2c_1738873035023","connectionId":"MF_bb77fc_1738873035024","linkName":"0_b3f8e7_1738873035023","entityPath":"secdev-test/ConsumerGroups/$default/Partitions/0"}
2025-02-06 14:17:15,677 WARN : com.azure.core.amqp.implementation.MessageFlux - {"az.sdk.message":"The mediator is active.","messageFlux":"mf_b4fd2c_1738873035023","connectionId":"MF_bb77fc_1738873035024","linkName":"0_b3f8e7_1738873035023","entityPath":"secdev-test/ConsumerGroups/$default/Partitions/0"}
2025-02-06 14:17:50,115 WARN : com.azure.core.amqp.implementation.MessageFlux - {"az.sdk.message":"Receiver emitted terminal error.","exception":"New receiver '8b249262-90f5-40a2-b06e-2f1bcd61d187' with higher epoch of '0' is created hence current receiver 'e81eb66c-2a7a-4ec6-bf67-1115a2d63b21' with epoch '0' is getting disconnected. If you are recreating the receiver, make sure a higher epoch is used. TrackingId:bd8e2e5200008b56001fba4967a518cb_G45_B1, SystemTracker:secdev:eventhub:secdev-test~16383|$default, Timestamp:2025-02-06T20:17:50, errorContext[NAMESPACE: secdev.servicebus.windows.net. ERROR CONTEXT: N/A, PATH: secdev-test/ConsumerGroups/$default/Partitions/0, REFERENCE_ID: 0_b3f8e7_1738873035023, LINK_CREDIT: 500]","messageFlux":"mf_b4fd2c_1738873035023","connectionId":"MF_bb77fc_1738873035024","linkName":"0_b3f8e7_1738873035023","entityPath":"secdev-test/ConsumerGroups/$default/Partitions/0"}
2025-02-06 14:17:50,134 WARN : com.azure.core.amqp.implementation.MessageFlux - {"az.sdk.message":"Terminal error signal from Upstream|Receiver arrived at MessageFlux.","exception":"New receiver '8b249262-90f5-40a2-b06e-2f1bcd61d187' with higher epoch of '0' is created hence current receiver 'e81eb66c-2a7a-4ec6-bf67-1115a2d63b21' with epoch '0' is getting disconnected. If you are recreating the receiver, make sure a higher epoch is used. TrackingId:bd8e2e5200008b56001fba4967a518cb_G45_B1, SystemTracker:secdev:eventhub:secdev-test~16383|$default, Timestamp:2025-02-06T20:17:50, errorContext[NAMESPACE: secdev.servicebus.windows.net. ERROR CONTEXT: N/A, PATH: secdev-test/ConsumerGroups/$default/Partitions/0, REFERENCE_ID: 0_b3f8e7_1738873035023, LINK_CREDIT: 500]","messageFlux":"mf_b4fd2c_1738873035023","connectionId":"MF_bb77fc_1738873035024","linkName":"0_b3f8e7_1738873035023","entityPath":"secdev-test/ConsumerGroups/$default/Partitions/0"}
2025-02-06 14:17:50,135 WARN : com.azure.core.amqp.implementation.MessageFlux - {"az.sdk.message":"MessageFlux reached a terminal error-state, signaling it downstream.","exception":"New receiver '8b249262-90f5-40a2-b06e-2f1bcd61d187' with higher epoch of '0' is created hence current receiver 'e81eb66c-2a7a-4ec6-bf67-1115a2d63b21' with epoch '0' is getting disconnected. If you are recreating the receiver, make sure a higher epoch is used. TrackingId:bd8e2e5200008b56001fba4967a518cb_G45_B1, SystemTracker:secdev:eventhub:secdev-test~16383|$default, Timestamp:2025-02-06T20:17:50, errorContext[NAMESPACE: secdev.servicebus.windows.net. ERROR CONTEXT: N/A, PATH: secdev-test/ConsumerGroups/$default/Partitions/0, REFERENCE_ID: 0_b3f8e7_1738873035023, LINK_CREDIT: 500]","messageFlux":"mf_b4fd2c_1738873035023","connectionId":"MF_bb77fc_1738873035024","linkName":"0_b3f8e7_1738873035023","entityPath":"secdev-test/ConsumerGroups/$default/Partitions/0"}
2025-02-06 14:17:50,138 INFO : org.graylog.enterprise.integrations.azure.external.AzureLogsProcessor - Input [[Azure Event Hubs/Event Hubs/67a3eecc62e4bb171b9760dd]] lost ownership of partition [0]. The partition ownership was likely taken by another Graylog node to help balance the receiving load.
2025-02-06 14:17:50,143 INFO : org.graylog.enterprise.integrations.azure.external.AzureLogsProcessor - Input [[Azure Event Hubs/Event Hubs/67a3eecc62e4bb171b9760dd]] has stopped receiving on partition [0].

/nocl logging change for dependency update

@danotorrey danotorrey requested a review from thll February 6, 2025 20:57
@thll thll merged commit 1849c0b into master Feb 7, 2025
8 checks passed
@thll thll deleted the nit/reduce-azure-info-logging branch February 7, 2025 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants