Server settings in log4net.config - Revision history

Ollvihe: /* Send logs, metrics and traces to OpenTelemetry */

2025-12-15T09:54:08Z

Send logs, metrics and traces to OpenTelemetry

← Older revision		Revision as of 09:54, 15 December 2025
Line 9:		Line 9:

	==Send logs, metrics and traces to OpenTelemetry==		==Send logs, metrics and traces to OpenTelemetry==

			QPR ProcessAnalyzer supports writing OpenTelemetry (https://opentelemetry.io/docs) logs, metrics and traces.

	=== Logs ===		=== Logs ===
	QPR ProcessAnalyzer can write logs using the OpenTelemetry ~~(https://opentelemetry.io/docs)~~ exporter into the provided endpoint. If an endpoint is not configured, logs are not exported.		QPR ProcessAnalyzer can write logs using the OpenTelemetry exporter into the provided endpoint. If an endpoint is not configured, logs are not exported.

	The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):		The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):
	* '''OTEL_EXPORTER_OTLP_ENDPOINT''' sends all signals to the same collector.		* '''OTEL_EXPORTER_OTLP_ENDPOINT''' sends all signals to the same collector.
	* '''OTEL_EXPORTER_OTLP_TRACES_ENDPOINT''' collector endpoint for traces.		* '''OTEL_EXPORTER_OTLP_TRACES_ENDPOINT''' collector endpoint for traces.
	* '''OTEL_EXPORTER_OTLP_METRICS_ENDPOINT''' collector ~~endopint~~ for metrics.		* '''OTEL_EXPORTER_OTLP_METRICS_ENDPOINT''' collector endpoint for metrics.
	* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.		* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.

Line 22:		Line 24:

	=== Metrics ===		=== Metrics ===
	QPR ProcessAnalyzer can write metrics using the OpenTelemetry ~~(https://opentelemetry.io/docs)~~ exporter into the provided endpoint.		QPR ProcessAnalyzer can write metrics using the OpenTelemetry exporter into the provided endpoint.

	There are the following standard metrics:		There are the following standard metrics:
Line 32:		Line 34:

	=== Traces ===		=== Traces ===
	QPR ProcessAnalyzer can write traces using the OpenTelemetry ~~(https://opentelemetry.io/docs)~~ exporter into the provided endpoint.		QPR ProcessAnalyzer can write traces using the OpenTelemetry exporter into the provided endpoint.

	There are the following standard traces:		There are the following standard traces:

Ollvihe: /* Logs */

2025-11-26T23:32:59Z

Logs

← Older revision		Revision as of 23:32, 26 November 2025
Line 11:		Line 11:

	=== Logs ===		=== Logs ===
	QPR ProcessAnalyzer can ~~write~~ write logs ~~and uses~~ the OpenTelemetry (https://opentelemetry.io/docs) exporter ~~to write them~~ into the provided endpoint. If an endpoint is not configured, logs are not exported.		QPR ProcessAnalyzer can write logs using the OpenTelemetry (https://opentelemetry.io/docs) exporter into the provided endpoint. If an endpoint is not configured, logs are not exported.

	The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):		The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):
Line 19:		Line 19:
	* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.		* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.

	QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using JSON format for structured logging (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).		QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using JSON format for structured logging (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).

	=== Metrics ===		=== Metrics ===

Ollvihe: /* Metrics */

2025-11-26T23:32:21Z

Metrics

← Older revision		Revision as of 23:32, 26 November 2025
Line 22:		Line 22:

	=== Metrics ===		=== Metrics ===
	QPR ProcessAnalyzer can ~~write~~ write metrics ~~and uses~~ the OpenTelemetry (https://opentelemetry.io/docs) exporter ~~to write them~~ into the provided endpoint.		QPR ProcessAnalyzer can write metrics using the OpenTelemetry (https://opentelemetry.io/docs) exporter into the provided endpoint.

	There are the following standard metrics ~~are written~~:		There are the following standard metrics:
	* '''_Microsoft.AspNetCore_''' to track QPR ProcessAnalyzer API calls.		* '''_Microsoft.AspNetCore_''' to track QPR ProcessAnalyzer API calls.
	* '''_Microsoft.EntityFrameworkCore_''' to track EntityFramework status.		* '''_Microsoft.EntityFrameworkCore_''' to track EntityFramework status.
	* '''_Microsoft.Data.SqlClient.EventSource_''' to track ~~SqlClient~~ status.		* '''_Microsoft.Data.SqlClient.EventSource_''' to track SQL Server client status.

	If an endpoint is not configured, metrics are not collected and exported.		If an endpoint is not configured, metrics are not collected and exported.

Ollvihe: /* Traces */

2025-11-26T23:31:24Z

Traces

← Older revision		Revision as of 23:31, 26 November 2025
Line 32:		Line 32:

	=== Traces ===		=== Traces ===
	QPR ProcessAnalyzer can write traces ~~and uses~~ the OpenTelemetry (https://opentelemetry.io/docs) exporter ~~to write them~~ into the provided endpoint.		QPR ProcessAnalyzer can write traces using the OpenTelemetry (https://opentelemetry.io/docs) exporter into the provided endpoint.

	There are the following standard traces ~~written~~:		There are the following standard traces:
	* '''_Microsoft.EntityFrameworkCore_''' to trace EntityFramework queries.		* '''_Microsoft.EntityFrameworkCore_''' to trace EntityFramework queries.
	* '''_Microsoft.AspNetCore_''' to trace QPR ProcessAnalyzer API calls.		* '''_Microsoft.AspNetCore_''' to trace QPR ProcessAnalyzer API calls.

	In addition, there are the following custom traces:		In addition, there are the following custom traces:
	* '''_QPR.ProcessAnalyzer.ExpressionQuery_''' to trace expression query evaluation.		* '''_QPR.ProcessAnalyzer.ExpressionQuery_''' to trace expression language query evaluation.
	* '''_QPR.ProcessAnalyzer.DatabaseOperation_''' to trace queries to external data source.		* '''_QPR.ProcessAnalyzer.DatabaseOperation_''' to trace queries to external data source.
	* '''_QPR.ProcessAnalyzer.ExpressionLanguage_''' to trace calls to expression language function and property calls.		* '''_QPR.ProcessAnalyzer.ExpressionLanguage_''' to trace calls to expression language function and property calls.

	If an endpoint is not configured, traces are not collected and exported.		If an endpoint is not configured, traces are not collected and exported.

Ollvihe: /* Send logs, metrics and traces to OpenTelemetry */

2025-11-26T23:30:08Z

Send logs, metrics and traces to OpenTelemetry

← Older revision		Revision as of 23:30, 26 November 2025
Line 19:		Line 19:
	* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.		* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.

	QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using ~~'''~~JSON format for structured logging~~'''~~ (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).		QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using JSON format for structured logging (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).

	=== Metrics ===		=== Metrics ===

Ollvihe: /* Send logs to OpenTelemetry */

2025-11-26T23:29:38Z

Send logs to OpenTelemetry

← Older revision		Revision as of 23:29, 26 November 2025
Line 8:		Line 8:
	* log4net > appender > '''lockingModel''': By default, the server log works in the ''ExclusiveLock'' mode, i.e. the log file is reserved by the QPR ProcessAnalyzer process for the entire time QPR ProcessAnalyzer is running. Thus it's not possible to edit or delete log files during that time.		* log4net > appender > '''lockingModel''': By default, the server log works in the ''ExclusiveLock'' mode, i.e. the log file is reserved by the QPR ProcessAnalyzer process for the entire time QPR ProcessAnalyzer is running. Thus it's not possible to edit or delete log files during that time.

	==Send logs to OpenTelemetry==		==Send logs, metrics and traces to OpenTelemetry==

	=== Logs ===		=== Logs ===

Ollvihe: /* OpenTelemetry in Snowflake Native App */

2025-11-26T23:29:10Z

OpenTelemetry in Snowflake Native App

← Older revision		Revision as of 23:29, 26 November 2025
Line 44:		Line 44:

	If an endpoint is not configured, traces are not collected and exported.		If an endpoint is not configured, traces are not collected and exported.

	~~=== OpenTelemetry in Snowflake Native App ===~~
	Writing logs is controlled by the '''LOG_LEVEL''' option for '''METADATA''' schema. If it is not set, than '''WARN''' level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-log-level) for details. To take new `LOG_LEVEL` into use service must be restarted.

	Application writes traces into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces). Writing traces controlled by `TRACE_LEVEL` option for `METADATA` schema. If it is not set, than `ALWAYS` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-trace-level) for details.

	To take new `TRACE_LEVEL` into use service must be restarted. Application writes metrics into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces).

	~~[Snowflake metrics](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#label-spcs-available-platform-metrics) that should be written:~~
	* '''_system_ to track CPU and memory usage.
	* '''_system_limits_''' to check CPU and memory limits for container.
	* '''_storage_''' to track storage volume used by SQL Server.

	Writing metrics controlled by `METRIC_LEVEL` option for `METADATA` schema. If it is not set, than `ALL` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-metric-level) for details. To take new `METRIC_LEVEL` into use service must be restarted

Ollvihe: /* Send logs to OpenTelemetry */

2025-11-26T23:27:13Z

Send logs to OpenTelemetry

← Older revision		Revision as of 23:27, 26 November 2025
Line 9:		Line 9:

	==Send logs to OpenTelemetry==		==Send logs to OpenTelemetry==
	~~=== Traces ===~~
	~~QPR ProcessAnalyzer can write traces and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint.~~

	~~There are~~ the ~~following standard traces written~~:		=== Logs ===
	* '''_Microsoft.~~EntityFrameworkCore_'''~~ to ~~trace EntityFramework queries~~.		QPR ProcessAnalyzer can write write logs and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint. If an endpoint is not configured, logs are not exported.
	* '''_Microsoft.AspNetCore_''' to trace QPR ProcessAnalyzer API calls.

	~~In addition, there~~ are ~~the following custom traces~~:		The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):
	* '''~~_QPR.ProcessAnalyzer.ExpressionQuery_~~''' to ~~trace expression query evaluation~~.		* '''OTEL_EXPORTER_OTLP_ENDPOINT''' sends all signals to the same collector.
	* '''~~_QPR~~.~~ProcessAnalyzer.DatabaseOperation_~~''' ~~to trace queries to external data source~~.		* '''OTEL_EXPORTER_OTLP_TRACES_ENDPOINT''' collector endpoint for traces.
	* '''~~_QPR.ProcessAnalyzer.ExpressionLanguage_~~''' ~~to trace calls to expression language function and property calls~~.		* '''OTEL_EXPORTER_OTLP_METRICS_ENDPOINT''' collector endopint for metrics.
			* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.

	~~If an endpoint is not configured~~, ~~traces~~ are ~~not collected and exported~~.		QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using '''JSON format for structured logging''' (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).

	=== Metrics ===		=== Metrics ===
Line 33:		Line 31:
	If an endpoint is not configured, metrics are not collected and exported.		If an endpoint is not configured, metrics are not collected and exported.

	=== ~~Logs~~ ===		=== Traces ===
	QPR ProcessAnalyzer can write ~~write logs~~ and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint. ~~If an endpoint is not configured, logs~~ are ~~not exported~~.		QPR ProcessAnalyzer can write traces and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint.

			There are the following standard traces written:
			* '''_Microsoft.EntityFrameworkCore_''' to trace EntityFramework queries.
			* '''_Microsoft.AspNetCore_''' to trace QPR ProcessAnalyzer API calls.

	~~The~~ following ~~environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter)~~:		In addition, there are the following custom traces:
	* '''~~OTEL_EXPORTER_OTLP_ENDPOINT~~''' ~~sends all signals~~ to ~~the same collector~~.		* '''_QPR.ProcessAnalyzer.ExpressionQuery_''' to trace expression query evaluation.
	* '''~~OTEL_EXPORTER_OTLP_TRACES_ENDPOINT~~''' ~~collector endpoint for traces~~.		* '''_QPR.ProcessAnalyzer.DatabaseOperation_''' to trace queries to external data source.
	* '''~~OTEL_EXPORTER_OTLP_METRICS_ENDPOINT''' collector endopint for metrics~~.		* '''_QPR.ProcessAnalyzer.ExpressionLanguage_''' to trace calls to expression language function and property calls.
	* '''~~OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs~~.

	~~QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR'''~~, and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using '''JSON format for structured logging''' (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).		If an endpoint is not configured, traces are not collected and exported.

	=== OpenTelemetry in Snowflake Native App ===		=== OpenTelemetry in Snowflake Native App ===

Ollvihe: /* Send logs to OpenTelemetry */

2025-11-25T09:48:05Z

Send logs to OpenTelemetry

← Older revision		Revision as of 09:48, 25 November 2025
Line 9:		Line 9:

	==Send logs to OpenTelemetry==		==Send logs to OpenTelemetry==
	~~Application writes~~ traces and uses [OpenTelemetry](https://opentelemetry.io/docs/) exporter to write them into provided endpoint		=== Traces ===
	* Standard traces:		QPR ProcessAnalyzer can write traces and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint.
	** _Microsoft.EntityFrameworkCore_ - to trace EntityFramework queries
	** _Microsoft.AspNetCore_ - to trace ProcessAnalyzer API calls		There are the following standard traces written:
	* ProcessAnalyzer traces:		* '''_Microsoft.EntityFrameworkCore_''' to trace EntityFramework queries.
	** _QPR.ProcessAnalyzer.ExpressionQuery_ - to trace expression query evaluation		* '''_Microsoft.AspNetCore_''' to trace QPR ProcessAnalyzer API calls.
	** _QPR.ProcessAnalyzer.DatabaseOperation_ - to trace queries to external data source
	** _QPR.ProcessAnalyzer.ExpressionLanguage_ - to trace calls to ~~Expression Language functions~~ and ~~properties~~		In addition, there are the following custom traces:
	* If endpoint is not configured ~~then~~ traces are not collected and exported.		* '''_QPR.ProcessAnalyzer.ExpressionQuery_''' to trace expression query evaluation.
	* Application writes metrics and uses [OpenTelemetry](https://opentelemetry.io/docs/) exporter to write them into provided endpoint		* '''_QPR.ProcessAnalyzer.DatabaseOperation_''' to trace queries to external data source.
	* Standard metrics ~~that should be~~ written:		* '''_QPR.ProcessAnalyzer.ExpressionLanguage_''' to trace calls to expression language function and property calls.
	** _Microsoft.AspNetCore_ - to track ProcessAnalyzer API calls
	** _Microsoft.EntityFrameworkCore_ - to track EntityFramework status		If an endpoint is not configured, traces are not collected and exported.
	** _Microsoft.Data.SqlClient.EventSource_ - to track SqlClient status
	* If endpoint is not configured ~~then~~ metrics are not collected and exported.		=== Metrics ===
	* Application writes logs and uses [OpenTelemetry](https://opentelemetry.io/docs/) exporter to write them into provided endpoint		QPR ProcessAnalyzer can write write metrics and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint.
	** If endpoint is not configured ~~then~~ logs are not exported.
	* Environment variables to control collecting and exporting telemetry data using [OpenTelemetry Protocol Exporter](https://opentelemetry.io/docs/specs/otel/protocol/exporter/)		There are the following standard metrics are written:
	** `OTEL_EXPORTER_OTLP_ENDPOINT~~` -~~ sends all signals to the same collector		* '''_Microsoft.AspNetCore_''' to track QPR ProcessAnalyzer API calls.
	** `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT~~` -~~ collector endpoint for traces		* '''_Microsoft.EntityFrameworkCore_''' to track EntityFramework status.
	** `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT~~` -~~ collector endopint for metrics		* '''_Microsoft.Data.SqlClient.EventSource_''' to track SqlClient status.
	** `OTEL_EXPORTER_OTLP_LOGS_ENDPOINT~~` -~~ collector endpoint for logs
	* Application writes logs with level `WARN` by default		If an endpoint is not configured, metrics are not collected and exported.
	** Logs are written into container's stdout stream using [JSON format for structured logging](https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json)
	** Logs with level `WARN`, `ERROR`, `FATAL` additionally written into snowflake events table utilizing event's severity		=== Logs ===
	** Writing logs controlled by `LOG_LEVEL` option for `METADATA` schema. If it is not set, than `WARN` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-log-level) for details.		QPR ProcessAnalyzer can write write logs and uses the OpenTelemetry (https://opentelemetry.io/docs) exporter to write them into the provided endpoint. If an endpoint is not configured, logs are not exported.
	** To take new `LOG_LEVEL` into use service must be restarted
	* Application writes traces into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces) ~~(#2504281133008#)~~		The following environment variables are used to control collecting and exporting telemetry data using OpenTelemetry Protocol Exporter (https://opentelemetry.io/docs/specs/otel/protocol/exporter):
	** Writing traces controlled by `TRACE_LEVEL` option for `METADATA` schema. If it is not set, than `ALWAYS` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-trace-level) for details.		* '''OTEL_EXPORTER_OTLP_ENDPOINT''' sends all signals to the same collector.
	* To take new `TRACE_LEVEL` into use service must be restarted		* '''OTEL_EXPORTER_OTLP_TRACES_ENDPOINT''' collector endpoint for traces.
	** Application writes metrics into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces) ~~(#2504281133008#)~~		* '''OTEL_EXPORTER_OTLP_METRICS_ENDPOINT''' collector endopint for metrics.
	* [Snowflake metrics](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#label-spcs-available-platform-metrics) that should be written:		* '''OTEL_EXPORTER_OTLP_LOGS_ENDPOINT''' collector endpoint for logs.
	** _system_ - to track CPU and memory usage
	** _system_limits_ - to check CPU and memory limits for container		QPR ProcessAnalyzer writes logs with level '''WARN''' by default. Logs with level '''WARN''', '''ERROR''', and '''FATAL''' additionally written into Snowflake events table utilizing event's severity. Logs are written into container's stdout stream using '''JSON format for structured logging''' (https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json).
	** _storage_ - to track storage volume used by ~~SqlServer~~
	* Writing metrics controlled by `METRIC_LEVEL` option for `METADATA` schema. If it is not set, than `ALL` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-metric-level) for details.		=== OpenTelemetry in Snowflake Native App ===
	** To take new `METRIC_LEVEL` into use service must be restarted		Writing logs is controlled by the '''LOG_LEVEL''' option for '''METADATA''' schema. If it is not set, than '''WARN''' level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-log-level) for details. To take new `LOG_LEVEL` into use service must be restarted.

			Application writes traces into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces). Writing traces controlled by `TRACE_LEVEL` option for `METADATA` schema. If it is not set, than `ALWAYS` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-trace-level) for details.

			To take new `TRACE_LEVEL` into use service must be restarted. Application writes metrics into [endpoint, provided by Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#publishing-otlp-application-metrics-and-traces).

			[Snowflake metrics](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/monitoring-services#label-spcs-available-platform-metrics) that should be written:
			* '''_system_ to track CPU and memory usage.
			* '''_system_limits_''' to check CPU and memory limits for container.
			* '''_storage_''' to track storage volume used by SQL Server.

			Writing metrics controlled by `METRIC_LEVEL` option for `METADATA` schema. If it is not set, than `ALL` level used. See [Snowflake documentation](https://docs.snowflake.com/en/sql-reference/parameters#label-metric-level) for details. To take new `METRIC_LEVEL` into use service must be restarted

Ollvihe: /* Send logs to OpenTelemetry */

2025-11-25T09:16:17Z

Send logs to OpenTelemetry

← Older revision		Revision as of 09:16, 25 November 2025
Line 24:		Line 24:
	** _Microsoft.Data.SqlClient.EventSource_ - to track SqlClient status		** _Microsoft.Data.SqlClient.EventSource_ - to track SqlClient status
	* If endpoint is not configured then metrics are not collected and exported.		* If endpoint is not configured then metrics are not collected and exported.
			* Application writes logs and uses [OpenTelemetry](https://opentelemetry.io/docs/) exporter to write them into provided endpoint
			** If endpoint is not configured then logs are not exported.
	* Environment variables to control collecting and exporting telemetry data using [OpenTelemetry Protocol Exporter](https://opentelemetry.io/docs/specs/otel/protocol/exporter/)		* Environment variables to control collecting and exporting telemetry data using [OpenTelemetry Protocol Exporter](https://opentelemetry.io/docs/specs/otel/protocol/exporter/)
	** `OTEL_EXPORTER_OTLP_ENDPOINT` - sends all signals to the same collector		** `OTEL_EXPORTER_OTLP_ENDPOINT` - sends all signals to the same collector
	** `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` - collector endpoint for traces		** `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` - collector endpoint for traces
	** `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` - collector endopint for metrics		** `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` - collector endopint for metrics
			** `OTEL_EXPORTER_OTLP_LOGS_ENDPOINT` - collector endpoint for logs
	* Application writes logs with level `WARN` by default		* Application writes logs with level `WARN` by default
	** Logs are written into container's stdout stream using [JSON format for structured logging](https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json)		** Logs are written into container's stdout stream using [JSON format for structured logging](https://learn.microsoft.com/en-us/dotnet/core/extensions/console-log-formatter#json)