Paulin Todev

> Adding a staleness marker just makes the series stop. This is what happens for every other metric that uses Prometheus' timestamp, when it goes away. Yes, but unlike non-timestamped...

#5972 was merged, but we will need to raise a new PR for this, since #5972 [intentionally](https://github.com/grafana/agent/pull/5972#discussion_r1441980155) did not expose a `track_timestamps_staleness` config entry.

Yes, @bboreham added it in #6317. So far on the main branch, `track_timestamps_staleness` is set to `false` by default. I'll close this issue and if there is a need we...

Hi, @djcode! I opened a [PR](https://github.com/grafana/alloy/pull/942) to add this feature to Alloy. Thank you for contributing it. The Alloy PR is exactly the same as yours. I am going to...

The main benefit of `otelcol.receiver` is that it minimises the amount of sub folders. The website isn't great with displaying deeply nested subfolders in the left navigation pane. I'm ok...

@yurishkuro Unfortunately, I found it difficult to find a clean solution using protobuf. Using [Pkl](https://pkl-lang.org/index.html) seems more promising to me, because it contains a lot of the features we need...

The schema could be useful for generating code and docs both in the main Collector repo, and in its distributions. For example: 1. Creating an alternative `config.go` in an OTel...

Hi, @theletterf! In order for you to generate docs, I suppose you need information such as: * Whether a given config argument is optional or mandatory. * What the default...

Thanks, @theletterf! I will keep your requirements in mind. I know the the [Pkl PR](https://github.com/open-telemetry/opentelemetry-collector/pull/10376) is a bit disruptive, mostly due to the Pkl Duration type and the Pkl-specific validation...

@hainenber True, I added the converters now :) @mattiasnensen Unfortunately I think Alloy will only pick up the change once the upstream exporter has implemented it. If you need to...