Intercepting request for centralized logging in spring microservices
I am trying to integrate Graylog (with RabbitMQ) for centralized collection of logs across different services, this includes HTTP request,response and custom logs of Rest Apis.
Is it good practice to use spring interceptors/controller advice for intercepting incoming requests/response for sending data to Graylog.
spring-boot microservices graylog2
asked Nov 20 '18 at 9:49
Prashant
304
add a comment |
I am trying to integrate Graylog (with RabbitMQ) for centralized collection of logs across different services, this includes HTTP request,response and custom logs of Rest Apis.
Is it good practice to use spring interceptors/controller advice for intercepting incoming requests/response for sending data to Graylog.
spring-boot microservices graylog2
asked Nov 20 '18 at 9:49
Prashant
304
add a comment |
I am trying to integrate Graylog (with RabbitMQ) for centralized collection of logs across different services, this includes HTTP request,response and custom logs of Rest Apis.
Is it good practice to use spring interceptors/controller advice for intercepting incoming requests/response for sending data to Graylog.
spring-boot microservices graylog2
asked Nov 20 '18 at 9:49
Prashant
304
I am trying to integrate Graylog (with RabbitMQ) for centralized collection of logs across different services, this includes HTTP request,response and custom logs of Rest Apis.
Is it good practice to use spring interceptors/controller advice for intercepting incoming requests/response for sending data to Graylog.
spring-boot microservices graylog2
spring-boot microservices graylog2
asked Nov 20 '18 at 9:49
Prashant
304
asked Nov 20 '18 at 9:49
Prashant
304
asked Nov 20 '18 at 9:49
Prashant
304
asked Nov 20 '18 at 9:49
Prashant
304
asked Nov 20 '18 at 9:49
Prashant
304
304
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I see no problem doing that as long as you know what you want to capture. If its url and method and response status than may be access log serves you better. If you actually want to capture the request body and headers and response body then yes.
But again question will come if you have an api gateway and if so does all the request goes through it? if so then perhaps you can intercept there. One place without individual services doing the same thing again and again.
You should look at your architecture and your requirements with the logging, then perhaps you can make a call. But yes there should be no harm in adding interceptors for logging if it boils down to it
answered Nov 20 '18 at 11:17
Anunay
1,000718
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390257%2fintercepting-request-for-centralized-logging-in-spring-microservices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I see no problem doing that as long as you know what you want to capture. If its url and method and response status than may be access log serves you better. If you actually want to capture the request body and headers and response body then yes.
But again question will come if you have an api gateway and if so does all the request goes through it? if so then perhaps you can intercept there. One place without individual services doing the same thing again and again.
You should look at your architecture and your requirements with the logging, then perhaps you can make a call. But yes there should be no harm in adding interceptors for logging if it boils down to it
answered Nov 20 '18 at 11:17
Anunay
1,000718
add a comment |
I see no problem doing that as long as you know what you want to capture. If its url and method and response status than may be access log serves you better. If you actually want to capture the request body and headers and response body then yes.
But again question will come if you have an api gateway and if so does all the request goes through it? if so then perhaps you can intercept there. One place without individual services doing the same thing again and again.
You should look at your architecture and your requirements with the logging, then perhaps you can make a call. But yes there should be no harm in adding interceptors for logging if it boils down to it
answered Nov 20 '18 at 11:17
Anunay
1,000718
add a comment |
I see no problem doing that as long as you know what you want to capture. If its url and method and response status than may be access log serves you better. If you actually want to capture the request body and headers and response body then yes.
But again question will come if you have an api gateway and if so does all the request goes through it? if so then perhaps you can intercept there. One place without individual services doing the same thing again and again.
You should look at your architecture and your requirements with the logging, then perhaps you can make a call. But yes there should be no harm in adding interceptors for logging if it boils down to it
answered Nov 20 '18 at 11:17
Anunay
1,000718
I see no problem doing that as long as you know what you want to capture. If its url and method and response status than may be access log serves you better. If you actually want to capture the request body and headers and response body then yes.
But again question will come if you have an api gateway and if so does all the request goes through it? if so then perhaps you can intercept there. One place without individual services doing the same thing again and again.
You should look at your architecture and your requirements with the logging, then perhaps you can make a call. But yes there should be no harm in adding interceptors for logging if it boils down to it
answered Nov 20 '18 at 11:17
Anunay
1,000718
answered Nov 20 '18 at 11:17
Anunay
1,000718
answered Nov 20 '18 at 11:17
Anunay
1,000718
answered Nov 20 '18 at 11:17
Anunay
1,000718
1,000718
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390257%2fintercepting-request-for-centralized-logging-in-spring-microservices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
