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

Logging checks added. #39

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

NehaThawani44
Copy link
Contributor

Kindly have a quick review of the logging checks added.

}
}
//Some unknown error has occurred, returning an internal error
logger.error("Internal Recipient Error ");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the exception to this log. Internal recipient errors need to be debugged, and a stack trace in the logs would greatly help here

DefaultSuccessMAP returnValue = new DefaultSuccessMAP(infrastructureComponent.getId(),
infrastructureComponent.getOutboundModelVersion(),
messageAndPayload.getMessage().getId(),
securityTokenProvider.getSecurityTokenAsDAT(),
responseSenderUri);
logger.info(" Id "+ messageAndPayload.getMessage().getId().toString());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two lines do not provide meaningful context. Imagine reading a line
"ID 123456" in the logs. That does not really help to understand what happened

if (msg.getAffectedResource() != null && messageAndPayload.getPayload().isPresent()) {

logger.info(issueAt.getYear()+":"+issueAt.getMonth()+ ":"+ issueAt.getDay()+":"+issueAt.getHour()+":"+ issueAt.getMinute());
logger.info("Component ID :"+ infrastructureComponent.getId());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be difficult to maintain. We will need to log a ton of messages, so it would be better to have one function to print log entries for a generic message. That makes the code re-usable for other messages than ResourceUpdateMessages

}
}
catch (RejectMessageException ignored)
{
logger.error("Message could not be processed.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block of error messages is incorrect. This will always occur when a new resource is registered and should not be logged as an error. Please note that the exception name "ignored" indicates that this exception does not matter and can be safely ignored.

@@ -112,6 +138,9 @@ public DefaultSuccessMAP handleValidated(ResourceMAP messageAndPayload) throws R
try {
//No Exception occurred. Send MessageProcessedNotificationMessage
DefaultSuccessMAP returnValue = new DefaultSuccessMAP(infrastructureComponent.getId(), infrastructureComponent.getOutboundModelVersion(), messageAndPayload.getMessage().getId(), securityTokenProvider.getSecurityTokenAsDAT(), responseSenderAgent);
logger.info("Component ID :"+ infrastructureComponent.getId().toString());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above: Rather log the incoming message via some central message-logger function. Then, here you can print a log that the registration was successful

}
//return the (rewritten) URI of the infrastructure component
logger.info("The rewritten URI of the " +infrastructureComponent+" " + infrastructureComponent.getId().toString());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line makes no sense. Logging "infrastructureComponent" will give you some Java object ID

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