Fabian Stäber

My initial impulse is that `opentelemetry-extension-incubator` is a better fit because users would explicitly use these annotations in their code. Should I move it?

I moved it to `extensions/incubator/`. The new annotations are now in package `io.opentelemetry.extension.incubator.annotations`. From the discussion above I think the only unresolved point is how to use return values as...

Thanks for the quick response. If a user wants to time something that takes microseconds they certainly want to use different buckets than if they time something that takes milliseconds...

Thanks a lot for the explanation, this makes sense. In that case the annotations would be quite simple, as they only provide configuration options for the metric name and attributes....

Opened PR #4260.

I'm wondering how much of a problem this actually is. Even if some attributes change occasionally, `target_info` still are time series with constant values of `1`, which should be fairly...

> in general I think I agree that it shouldn't be a big problem most of the time. One solution would be to have the prometheus exporter have a configurable...

The best way to debug this is to uncomment these lines at the top of the script: ``` # echo >> /tmp/cifs.log # date >> /tmp/cifs.log # echo "$@" >>...

I don't really maintain this repository anymore but if you create a PR with the MIT or BSD license I'm happy to merge it.

Not sure if there is a complete list somewhere, but in most cases you should find documentation in the corresponding javadoc. Example: `java_lang_OperatingSystem_TotalSwapSpaceSize` corresponds to [OperatingSystemMXBean.getTotalSwapSpaceSize()](https://docs.oracle.com/en/java/javase/11/docs/api/jdk.management/com/sun/management/OperatingSystemMXBean.html)