configureawait.props now provides the ConfigureAwait weaver through the Fody 6.9.3
WeaverConfiguration property and sets FodyGenerateXsd=false, so the per-project
FodyWeavers.xml files and every FodyWeavers.xsd are redundant.
- delete 450 FodyWeavers.xml and 438 FodyWeavers.xsd from the framework, modules,
services, gateways, tests and migrations projects and from the micro service template
- every removed FodyWeavers.xml was equivalent to the default supplied by configureawait.props
(439 x <ConfigureAwait ContinueOnCapturedContext="false" />, 20 x <ConfigureAwait />, whose
default is ContinueOnCapturedContext=false, and 2 of those with an XML declaration); no
Blazor / AspNetCore.Components project carried one and the template manifests do not list them
- the aio template keeps its 22 files: its own Directory.Packages.props pins Fody 6.8.0, which
does not support the WeaverConfiguration property
Serilog enrichers:
- AbpLoggingSerilogElasticsearchModule and AbpLoggingSerilogOpenObserveModule now depend on
AbpSerilogEnrichersApplicationModule and AbpSerilogEnrichersUniqueIdModule, so the providers
pull in the ApplicationName / UniqueId enrichers their queries rely on
- add the corresponding project references (and drop the unused LINGYUN.Linq.Dynamic.Queryable
reference from the Elasticsearch logging package, add Serilog.Sinks.OpenTelemetry to the
OpenObserve logging package)
Documentation:
- add aspnet-core/framework/logging/README.md: a directory level index covering all five logging
modules (core Logging, the Elasticsearch and OpenObserve ILoggingProvider implementations and
the two Serilog enrichers) with module references, configuration options and notes
- document the OpenObserve audit log store in aspnet-core/framework/auditing/README.md:
storage support, module reference, AuditLogging:OpenObserve options and the platform notes
(per-tenant streams, append-only/delete not supported, flattened nested arrays, stream creation)
- add the missing English README of LINGYUN.Abp.Logging.Serilog.OpenObserve (the Chinese one linked
to a file that did not exist) and document that the condition parser / SQL builder helpers moved
from LINGYUN.Abp.Logging.Serilog.OpenObserve.Utils to LINGYUN.Abp.OpenObserve.Utils
Add an OpenObserve implementation of the audit logging stores as an alternative to
Elasticsearch: audit logs, security logs, entity changes and actions go into separate
streams and are queried with OpenObserve SQL.
LINGYUN.Abp.AuditLogging.OpenObserve:
- AbpAuditLoggingOpenObserveOptions binds AuditLogging:OpenObserve; the child streams are
derived from AuditLogStream (GetEntityChangeStream/GetActionStream), no separate options
- OpenObserveAuditLogWriter / OpenObserveSecurityLogWriter replace IAuditLogWriter /
ISecurityLogWriter; OpenObserveAuditLogManager / OpenObserveSecurityLogManager replace
IAuditLogManager / ISecurityLogManager; OpenObserveEntityChangeStore replaces IEntityChangeStore
- entity changes and actions are flattened into their own streams; Actions.* conditions use a
two-step query (match auditlogid in the actions stream, then filter the main stream by id),
because OpenObserve cannot query nested arrays structurally
- multi-tenancy: stream names are per tenant (audit_log_{tenantId:N}) via
IOpenObserveStreamNameNormalizer; writes resolve the log's own tenant, queries the current one
- writes may override _timestamp with the log time (AuditLog.ExecutionTime /
SecurityLog.CreationTime), bounded by TimestampAllowedUptoHours since OpenObserve only accepts
data within ZO_INGEST_ALLOWED_UPTO (5 hours by default)
- entity change details and _timestamp are handled by OpenObserveEntityChangeConverter through
IAuditLoggingOpenObserveSerializer (ABP IJsonSerializer by default), so entities never use
JsonSerializer directly
- deletion is not supported by OpenObserve (append-only, no DELETE/UPDATE): DeleteAsync /
DeleteManyAsync throw the business exception AuditLoggingOpenObserve:010001
("当前日志设施不支持删除记录!" / "The current logging facility does not support deleting records!")
backed by a zh-Hans/en localization resource
- a stream that does not exist yet (nothing ingested) yields an empty result and logs a warning
instead of failing
Shared infrastructure:
- move Condition / ComparisonOp / ExpressionParser from LINGYUN.Abp.Logging.Serilog.OpenObserve
to LINGYUN.Abp.OpenObserve (the parser now also handles Any(member) expressions) and add
OpenObserveSqlBuilder for SQL condition building
Tests:
- LINGYUN.Abp.AuditLogging.OpenObserve.Tests runs the shared AuditLogManager_Tests suite (delete
hooks overridden to assert the not-supported exception) plus tests for the timestamp helper,
localization, entity change round-trip, multi-tenant isolation and the missing-stream warning;
test streams are unique per host instance and cleaned up on shutdown
- AuditLogManager_Tests gains virtual DeleteAsync / DeleteManyAsync hooks (default behaviour unchanged)
Introduce an extension point that lets modules enrich audit/security log entries
before they are queued or written, instead of having to replace the whole store.
- add IAuditLogInfoContributor / ISecurityLogInfoContributor together with
AuditLogInfoContributorContext / SecurityLogInfoContributorContext
(IServiceProviderAccessor + the log info being enriched)
- AbpAuditLoggingOptions gains AuditLogInfoContributors / SecurityLogInfoContributors;
AuditingStore and SecurityLogStore run them (guarded by Any()) inside a fresh
service scope before enqueueing or writing the log
- LINGYUN.Abp.AuditLogging.IP.Location now contributes the resolved IP location
through that extension point instead of replacing IAuditingStore / ISecurityLogStore:
remove IPLocationAuditingStore and IPLocationSecurityLogStore, add
IPLocationAuditLogInfoContributor / IPLocationSecurityLogInfoContributor and
IPLocationConstants, and have AbpAuditLoggingIPLocationModule register both contributors
- document AbpAuditLoggingIPLocationOptions (section AuditLogging:IPLocation,
environment variable AuditLogging__IPLocation__IsEnabled) and make its default
IsEnabled = false explicit
- EfCoreAuditLogManager.GetAsync uses FindAsync with a nullable mapping so that a
missing audit log returns null instead of throwing
Note: the IP location remark is now stored under the "IPLocation" extra property
(previously "Location").
- Retrieve the last sorting index by reversing the sorting order.
- Obtain the index mapping using pattern matching
- Add the extension for obtaining ES error messages
- Increase by Specification the query of audit logs.
- Optimize the query of ES audit logs. Use the "search_after" feature when the number of records exceeds 10,000.