{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":573903333,"defaultBranch":"main","name":"opentelemetry-specification","ownerLogin":"loomis-relativity","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-12-03T19:50:54.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/68860480?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1671488814.7813","currentOid":""},"activityList":{"items":[{"before":"150451d4257be3d4673c7fcbf50fca7fb557d346","after":"feb4dac0742e3dd749954af295086ffdcd4571c8","ref":"refs/heads/main","pushedAt":"2023-04-10T14:33:00.856Z","pushType":"push","commitsCount":148,"pusher":{"login":"loomis-relativity","name":"Cal Loomis","path":"/loomis-relativity","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/68860480?s=80&v=4"},"commit":{"message":"Propose histogram bucket boundary metric advice (aka hint API) (#3216)\n\nFixes #2229.\r\nRelated to #3061 (lays groundwork but does not resolve).\r\nRelated to #2977, which may use this new API to have\r\n`http.server.duration` report in seconds instead of ms without changing\r\n/ breaking default bucket boundaries.\r\n\r\nSummary of the change:\r\n- Proposes a new parameter to optionally include when creating\r\ninstruments, called \"advice\".\r\n- For the moment, advice only has one parameter for specifying the\r\nbucket boundaries of explicit bucket histogram.\r\n- Advice can be expanded with additional parameters in the future (e.g.\r\ndefault attributes to retain). The parameters may be general (aka\r\napplicable to all instruments) or specific to a particular instrument\r\nkind, like bucket boundaries.\r\n- Advice parameters can influence the [default\r\naggregation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#default-aggregation),\r\nwhich is used if there is no matching view and if the reader does not\r\nspecify a preferred aggregation.\r\n- Not clear that all advice will be oriented towards configuring\r\naggregation, so I've intentionally left the scope of what they can\r\ninfluence open ended.\r\n\r\nI've prototyped this in java\r\n[here](https://github.com/open-telemetry/opentelemetry-java/pull/5217).\r\nExample usage:\r\n```\r\nDoubleHistogram doubleHistogram =\r\n        meterProvider\r\n            .get(\"meter\")\r\n            .histogramBuilder(\"histogram\")\r\n            .setUnit(\"foo\")\r\n            .setDescription(\"bar\")\r\n            .setAdvice(\r\n                advice -> advice.setBoundaries(Arrays.asList(10.0, 20.0, 30.0)))\r\n            .build();\r\n```\r\n\r\nAdvice could easily be changed to \"hint\" with everything else being\r\nequal. I thought \"advice\" clearly described what we're trying to\r\naccomplish, which is advice / recommend the implementation in providing\r\nuseful output with minimal configuration.\r\n\r\n---------\r\n\r\nCo-authored-by: Reiley Yang <reyang@microsoft.com>","shortMessageHtmlLink":"Propose histogram bucket boundary metric advice (aka hint API) (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1586795564\" data-permission-text=\"Title is private\" data-url=\"https://github.com/open-telemetry/opentelemetry-specification/issues/3216\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/open-telemetry/opentelemetry-specification/pull/3216/hovercard\" href=\"https://github.com/open-telemetry/opentelemetry-specification/pull/3216\">open-…</a>"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNC0xMFQxNDozMzowMC44NTY2MTJazwAAAAMVj5zR","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNC0xMFQxNDozMzowMC44NTY2MTJazwAAAAMVj5zR"}},"title":"Activity · loomis-relativity/opentelemetry-specification"}