DE4A Logs and error messages - Revision history

Javier.presa: /* Final participants DE/DO */ New errors added

2022-05-27T09:25:06Z

Final participants DE/DO: New errors added

Mpttfp eduardo.moreno: new error codes added

2022-05-18T10:57:59Z

new error codes added

Mpttfp eduardo.moreno: new error codes

2022-05-18T10:39:35Z

new error codes

Antonio.osuna at 15:37, 22 February 2022

2022-02-22T15:37:27Z

Antonio.osuna at 15:07, 22 February 2022

2022-02-22T15:07:28Z

Antonio.osuna at 12:34, 22 February 2022

2022-02-22T12:34:01Z

Martina.sestak: Added Authority Agent logs and error messages.

2022-02-14T14:54:07Z

Added Authority Agent logs and error messages.

Show changes

Antonio.osuna at 12:34, 7 February 2022

2022-02-07T12:34:46Z

Antonio.osuna at 09:04, 7 February 2022

2022-02-07T09:04:20Z

Javier.ferrero: Quality checks.

2022-02-04T12:29:59Z

Quality checks.

@@ Line 965: / Line 965: @@
 |16
 |40516
 |-
 |Business

@@ Line 384: / Line 384: @@
 |08
 |30008
 |}
@@ Line 941: / Line 973: @@
 |02
 |40602
 |}
 [[Category:Wip]]

@@ Line 933: / Line 933: @@
 |16
 |40516
 |}
 [[Category:Wip]]

@@ Line 5: / Line 5: @@
 Apart from the usual reasons of the logging and error handling, in the DE4A project, there are 3 main bullet points on which the definition of messages is based:
-* '''Kafka tracking''': messages sent to the [[Kafka]] server which can be previewed at: https://de4a.simplegob.com/package-tracker/#!detail
+* '''Kafka tracking''': messages sent to the [[Usage of third party specifications and components|Kafka]] server which can be previewed at: https://de4a.simplegob.com/package-tracker/#!detail
 * '''Metrics logs''': messages marked with a special tag inside the common log file or logged on a separated file, which will be used to analyze and raise some metrics about each system
 * '''Error convention''': standardise the error messages and codes
@@ Line 67: / Line 67: @@
 === Type ===
-It is mean to use just for the Connector log messages (metrics and [[Kafka]]).
+It is mean to use just for the Connector log messages (metrics and [[Usage of third party specifications and components|Kafka]]).
 {| class="wikitable"
 |+
@@ Line 387: / Line 387: @@
 === Log messages ===
-Messages meant to be sent to the [[Kafka]] server and also to be printed at the logging files of the Connector.
+Messages meant to be sent to the [[Usage of third party specifications and components|Kafka]] server and also to be printed at the logging files of the Connector.
 {| class="wikitable"
 |+

@@ Line 5: / Line 5: @@
 Apart from the usual reasons of the logging and error handling, in the DE4A project, there are 3 main bullet points on which the definition of messages is based:
-* '''Kafka tracking''': messages sent to the Kafka server which can be previewed at: <nowiki>https://de4a-dev-pt.egovlab.eu/#!detail</nowiki>
+* '''Kafka tracking''': messages sent to the [[Kafka]] server which can be previewed at: https://de4a.simplegob.com/package-tracker/#!detail
 * '''Metrics logs''': messages marked with a special tag inside the common log file or logged on a separated file, which will be used to analyze and raise some metrics about each system
 * '''Error convention''': standardise the error messages and codes
@@ Line 67: / Line 67: @@
 === Type ===
-It is mean to use just for the Connector log messages (metrics and Kafka).
+It is mean to use just for the Connector log messages (metrics and [[Kafka]]).
 {| class="wikitable"
 |+
@@ Line 387: / Line 387: @@
 === Log messages ===
-Messages meant to be sent to the Kafka server and also to be printed at the logging files of the Connector.
+Messages meant to be sent to the [[Kafka]] server and also to be printed at the logging files of the Connector.
 {| class="wikitable"
 |+

← Older revision		Revision as of 12:34, 22 February 2022
Line 934:		Line 934:
	\|40516		\|40516
	\|}		\|}
		+	[[Category:Wip]]

← Older revision		Revision as of 12:34, 7 February 2022
Line 1:		Line 1:
		+	In order to standardise the errors and logs handled by each component, some conventions have been taken, as log patterns, error codes definition or messages content.
		+
		+	The information on this page should be used by each partner who develops a DE4A component, also it should be maintained to have a proper messages reference and be aware which information will include.
		+
		+	Apart from the usual reasons of the logging and error handling, in the DE4A project, there are 3 main bullet points on which the definition of messages is based:
		+
		+	* '''Kafka tracking''': messages sent to the Kafka server which can be previewed at: <nowiki>https://de4a-dev-pt.egovlab.eu/#!detail</nowiki>
		+	* '''Metrics logs''': messages marked with a special tag inside the common log file or logged on a separated file, which will be used to analyze and raise some metrics about each system
		+	* '''Error convention''': standardise the error messages and codes
		+
	== Structure definition ==		== Structure definition ==
	This section will describe the hierarchy and model followed to build the different logs and messages. There are multiple patterns depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.		This section will describe the hierarchy and model followed to build the different logs and messages. There are multiple patterns depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.

← Older revision		Revision as of 09:04, 7 February 2022
Line 1:		Line 1:
−	~~== Overview ==~~
−	~~In order to standardise the errors and logs handled by each component, some conventions have been taken, as log patterns, error codes definition or messages content.~~
−
−	~~The information on this page should be used by each partner who develops a DE4A component, also it should be maintained to have a proper messages reference and be aware which information will include.~~
−
−	~~Apart from the usual reasons of the logging and error handling, in the DE4A project, there are 3 main bullet points on which the definition of messages is based:~~
−	* '''Kafka tracking''': messages sent to the Kafka server which can be previewed at: https://de4a-dev-pt.egovlab.eu/#!detail
−	* '''Metrics logs''': messages marked with a special tag inside the common log file or logged on a separated file, which will be used to analyze and raise some metrics about each system
−	* '''Error convention''': standardise the error messages and codes
−
	== Structure definition ==		== Structure definition ==
	This section will describe the hierarchy and model followed to build the different logs and messages. There are multiple patterns depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.		This section will describe the hierarchy and model followed to build the different logs and messages. There are multiple patterns depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.

@@ Line 1: / Line 1: @@
 == Overview ==
-In order to standarize the errors and logs handled by each component, some conventions have been taken, as log patterns, error codes definition or messages content.
+In order to standardise the errors and logs handled by each component, some conventions have been taken, as log patterns, error codes definition or messages content.
-The information on this page should be used by each partner who develop a DE4A component, also it should be maintained to have a proper messages reference and be aware which information will include.
+The information on this page should be used by each partner who develops a DE4A component, also it should be maintained to have a proper messages reference and be aware which information will include.
 * '''Kafka tracking''': messages sent to the Kafka server which can be previewed at: https://de4a-dev-pt.egovlab.eu/#!detail
 * '''Metrics logs''': messages marked with a special tag inside the common log file or logged on a separated file, which will be used to analyze and raise some metrics about each system
-* '''Error convenction''': standarize the error messages and codes
+* '''Error convention''': standardise the error messages and codes
 == Structure definition ==
-This section will describe the hierarchy and model followed to build the different logs and messages. There are multples pattern depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.
+This section will describe the hierarchy and model followed to build the different logs and messages. There are multiple patterns depending on the message nature, but the following tables will be a common reference to understand the rest of information collected in the page.
 === Layer ===
@@ Line 39: / Line 38: @@
 === Module ===
-A reference to each DE4A module possibly involved in an interaction. A "None" element has been included to represent the situation where a message occurs internally in a certain component
+A reference to each DE4A module possibly involved in an interaction. A "None" element has been included to represent the situation where a message occurs internally in a certain component.
 {| class="wikitable"
 |+
@@ Line 68: / Line 67: @@
 === Type ===
-It is mean to use just for the Connector log messages (metrics and Kafka)
+It is mean to use just for the Connector log messages (metrics and Kafka).
 {| class="wikitable"
 |+
@@ Line 85: / Line 84: @@
 === Error messages ===
-As part of the logging standardization, some error messages templates have been defined. Those messages will be thrown by each component with the corresponding parameterization.
+As part of the logging standardisation, some error messages templates have been defined. Those messages will be thrown by each component with the corresponding parameterisation.
 {| class="wikitable"
 |+
@@ Line 165: / Line 164: @@
 == Connector ==
-Specific messages for the component Connector. Each component around the Connector should be aware of the codes and content of this messages to act accordingly on each case
+Specific messages for the Connector. Each component around the Connector should be aware of the codes and content of these messages to act accordingly on each case.
 === Error messages ===
@@ Line 388: / Line 387: @@
 === Log messages ===
-Messages meant to be sent to the Kafka server and also to be printed at the logging files of the Connector
+Messages meant to be sent to the Kafka server and also to be printed at the logging files of the Connector.
 {| class="wikitable"
 |+
@@ Line 540: / Line 539: @@
 == Final participants DE/DO ==
-The proposal includes specific messages to the final participants which would be part of the metrics and statistics collection. Some basic messages have been defined to identify the possible situations at the Data Evaluator and Data Owner's
+The proposal includes specific messages to the final participants which would be part of the metrics and statistics collection. Some basic messages have been defined to identify the possible situations at the Data Evaluator and Data Owner's.
 === Error warning and local logs to collect ===