Oleksii Sholik

This issue hasn't been fixed. None of the metrics we export to Honeycomb have `source_id` attribute.

The problem is that the otel_metric_exporter lib does not read stack_id or source_id from the measurement metadata. It takes `stack_id` from the resource config which is passed to it at...

@thruflo given the small subset of SQL we support in shape where clauses, I believe it is more helpful to talk about what _is_ supported, first and foremost. I have...

@msfstef Main reason is decoupling. Our primary use case for telemetry is in Electric Cloud. So if we're going to make any changes to the telemetry code, it'll be informed...

Could you clarify about the "span for the connection process"? Is it about tracing the connection initialisation, i.e. from the moment Electric opens a connection to Postgres and up until...

@magnetised Feel free to assign this to me when these different consumer statuses are implemented.

> the connection resolver treats it as a hostname and tries to connect over ipv6. Does this only happen when `ELECTRIC_DATABASE_USE_IPV6` is set to `true`?

What does the browser console show when one of those errors is logged on the server? The client seems to be closing its end of the connection prematurely.

@balegas Why `OTEL_DEBUG=1` and not `OTEL_DEBUG=true`? We've been using boolean values for configuration flags so far. Even though it's not spelled out in the issue description, I remember @KyleAMathews saying...

> We'll need to add the db_id to the start of logs. This would also be a good time to add a JSON log option for easier parsing. Another option...