Hi,
I see some closed cases related to this issue:
- Need help specifying log path for MSSQL
- MSSQL servers logs extracted to loki Grafana dashboard with space in between character’s
Which I’m having a hard time to understand, as this is still not fixed though I was promised it would be fixed in Alloy v1.12.1. it still the same no matter which encoding is used, I get the same useless spaced characters as shown on the link above.
In addition, where I generate an output from SQL by wrong login, where the Alloy Live Debugging output is like this:
```
[IN]: timestamp: 2026-01-27T08:52:09.7433607-08:00, entry: 2026-01-27 08:52:07.91 Logon Error: 18456, Severity: 14, State: 8.
�, labels: {_log_type=“mssql_error”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”}, structured_metadata: {}
[IN]: timestamp: 2026-01-27T08:52:09.7433607-08:00, entry: 2026-01-27 08:52:07.91 Logon Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: ]
�, labels: {_log_type=“mssql_error”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”}, structured_metadata: {}
[OUT]: timestamp: 2026-01-27T08:52:07.91-08:00, entry: 2026-01-27 08:52:07.91 Logon Error: 18456, Severity: 14, State: 8.
�, labels: {tenant_id=“cust_app”, component=“Logon”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”, level=“error”, service_name=“database/mssql/error”}, structured_metadata: {“message”:“Error: 18456, Severity: 14, State: 8.\r�”}
[IN]: timestamp: 2026-01-27T08:52:10.7434033-08:00, entry: 2026-01-27 08:52:09.98 Logon Error: 18456, Severity: 14, State: 8.
�, labels: {_log_type=“mssql_error”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”}, structured_metadata: {}
[IN]: timestamp: 2026-01-27T08:52:10.7434033-08:00, entry: 2026-01-27 08:52:09.98 Logon Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: ]
�, labels: {_log_type=“mssql_error”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”}, structured_metadata: {}
[OUT]: timestamp: 2026-01-27T08:52:07.91-08:00, entry: 2026-01-27 08:52:07.91 Logon Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: ]
�, labels: {tenant_id=“cust_app”, component=“Logon”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”, level=“error”, service_name=“database/mssql/error”}, structured_metadata: {“message”:“Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: \u003clocal machine\u003e]\r�”}
[OUT]: timestamp: 2026-01-27T08:52:09.98-08:00, entry: 2026-01-27 08:52:09.98 Logon Error: 18456, Severity: 14, State: 8.
�, labels: {tenant_id=“cust_app”, component=“Logon”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”, level=“error”, service_name=“database/mssql/error”}, structured_metadata: {“message”:“Error: 18456, Severity: 14, State: 8.\r�”}
[OUT]: timestamp: 2026-01-27T08:52:09.98-08:00, entry: 2026-01-27 08:52:09.98 Logon Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: ]
�, labels: {tenant_id=“cust_app”, component=“Logon”, filename=“C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG”, level=“error”, service_name=“database/mssql/error”}, structured_metadata: {“message”:“Login failed for user ‘alloy’. Reason: Password did not match that for the login provided. [CLIENT: \u003clocal machine\u003e]\r�”}
```
Grafana can’t even show the logs, but throughs the error:
So I’d be really happy to know where the solution is, and why the above cases has been closed, when this obviously has not been fixed yet?