Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Content Distribution Journal Core 0.1.6
-
None
Description
Since SLING-8620, the a log entry like the following is logged for every processed package. The logs are filled with those statements for deployments using content distribution heavily.
{"file_path":"/var/log/aem/error.log","orig_time":"24.04.2020 15:59:37.096","level":"INFO","msg":"[sling-default-4-Registered Service.6633] org.apache.sling.distribution.journal.impl.publisher.DiscoveryService TopologyView changed from {\"states\":[{\"timestamp\":1587743965568,\"offset\":156580158,\"retries\":0,\"maxRetries\":-1,\"editable\":true,\"pubAgentName\":\"publish\",\"subAgentId\":\"cfd9ab72-34dc-400d-89e1-50bf890cde77-publishSubscriber\"}, {\"timestamp\":1587743966976,\"offset\":156580158,\"retries\":0,\"maxRetries\":-1,\"editable\":false,\"pubAgentName\":\"publish\",\"subAgentId\":\"7aa769b3-b822-489e-a436-1c6b9aca3c15-publishSubscriber\"}]} to {\"states\":[{\"timestamp\":1587743975568,\"offset\":156580160,\"retries\":0,\"maxRetries\":-1,\"editable\":true,\"pubAgentName\":\"publish\",\"subAgentId\":\"cfd9ab72-34dc-400d-89e1-50bf890cde77-publishSubscriber\"}, {\"timestamp\":1587743976977,\"offset\":156580160,\"retries\":0,\"maxRetries\":-1,\"editable\":false,\"pubAgentName\":\"publish\",\"subAgentId\":\"7aa769b3-b822-489e-a436-1c6b9aca3c15-publishSubscriber\"}]}","pod_name":"skyline-p95-aem-author-58555ff5f9-4fqd4","pod_uid":"cecfc7de-ca4d-49e4-9477-2a1e23153613","namespace":"ns-team-authorpersistence","aem_tenant":"ns-team-authorpersistence","aem_program_id":"0","aem_tier":"author","aem_envType":"dev","aem_envName":"dev42","aem_envId":"0","aem_service":"skyline-p95","aem_base_version":"6.5"}
Attachments
Issue Links
- relates to
-
SLING-8620 Journal Distribution discovery service should log topology changes at INFO level
- Closed