forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kafkaexporter zipkin encoding #1
Open
yaroliakh
wants to merge
644
commits into
main
Choose a base branch
from
kafkaexporter_zipkin_encoding
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yaroliakh
pushed a commit
that referenced
this pull request
Aug 18, 2023
…emetry#24676) **Description:** The metadata.yml for the SSH check receiver currently documents a resource attribute containing the SSH endpoint but this is not emitted. This PR updates the receiver to include this resource attribute. **Link to tracking Issue:** open-telemetry#24441 **Testing:** Example collector config: ```yaml receivers: sshcheck: endpoint: 13.245.150.131:22 username: ec2-user key_file: /Users/dewald.dejager/.ssh/sandbox.pem collection_interval: 15s known_hosts: /Users/dewald.dejager/.ssh/known_hosts ignore_host_key: false resource_attributes: "ssh.endpoint": enabled: true exporters: logging: verbosity: detailed prometheus: endpoint: 0.0.0.0:8081 resource_to_telemetry_conversion: enabled: true service: pipelines: metrics: receivers: [sshcheck] exporters: [logging, prometheus] ``` The log output looks like this: ``` 2023-07-30T16:52:38.724+0200 info MetricsExporter {"kind": "exporter", "data_type": "metrics", "name": "logging", "resource metrics": 1, "metrics": 2, "data points": 2} 2023-07-30T16:52:38.724+0200 info ResourceMetrics #0 Resource SchemaURL: Resource attributes: -> ssh.endpoint: Str(13.245.150.131:22) ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope otelcol/sshcheckreceiver 0.82.0-dev Metric #0 Descriptor: -> Name: sshcheck.duration -> Description: Measures the duration of SSH connection. -> Unit: ms -> DataType: Gauge NumberDataPoints #0 StartTimestamp: 2023-07-30 14:52:22.381672 +0000 UTC Timestamp: 2023-07-30 14:52:38.404003 +0000 UTC Value: 319 Metric #1 Descriptor: -> Name: sshcheck.status -> Description: 1 if the SSH client successfully connected, otherwise 0. -> Unit: 1 -> DataType: Sum -> IsMonotonic: false -> AggregationTemporality: Cumulative NumberDataPoints #0 StartTimestamp: 2023-07-30 14:52:22.381672 +0000 UTC Timestamp: 2023-07-30 14:52:38.404003 +0000 UTC Value: 1 ``` And the Prometheus metrics look like this: ``` # HELP sshcheck_duration Measures the duration of SSH connection. # TYPE sshcheck_duration gauge sshcheck_duration{ssh_endpoint="13.245.150.131:22"} 311 # HELP sshcheck_status 1 if the SSH client successfully connected, otherwise 0. # TYPE sshcheck_status gauge sshcheck_status{ssh_endpoint="13.245.150.131:22"} 1 ```
yaroliakh
pushed a commit
that referenced
this pull request
Aug 18, 2023
) **Description:** Adding command line argument `--status-code` to `telemetrygen traces`, which accepts `(Unset,Error,Ok)` (case sensitive) or the enum equivalent of `(0,1,2)`. Running ```shell telemetrygen traces --otlp-insecure --traces 1 --status-code 1 ``` against a minimal local collector yields ```txt 2023-07-29T21:27:57.862+0100 info ResourceSpans #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.4.0 Resource attributes: -> service.name: Str(telemetrygen) ScopeSpans #0 ScopeSpans SchemaURL: InstrumentationScope telemetrygen Span #0 Trace ID : f6dc4be32c78b9999c69d504a79e68c1 Parent ID : 4e2cd6e0e90cf2ea ID : 20835413e32d26a5 Name : okey-dokey Kind : Server Start time : 2023-07-29 20:27:57.861602 +0000 UTC End time : 2023-07-29 20:27:57.861726 +0000 UTC Status code : Error Status message : Attributes: -> net.peer.ip: Str(1.2.3.4) -> peer.service: Str(telemetrygen-client) Span #1 Trace ID : f6dc4be32c78b9999c69d504a79e68c1 Parent ID : ID : 4e2cd6e0e90cf2ea Name : lets-go Kind : Client Start time : 2023-07-29 20:27:57.861584 +0000 UTC End time : 2023-07-29 20:27:57.861726 +0000 UTC Status code : Error Status message : Attributes: -> net.peer.ip: Str(1.2.3.4) -> peer.service: Str(telemetrygen-server) ``` and similarly (the string version) ```shell telemetrygen traces --otlp-insecure --traces 1 --status-code '"Ok"' ``` produces ```txt Resource SchemaURL: https://opentelemetry.io/schemas/1.4.0 Resource attributes: -> service.name: Str(telemetrygen) ScopeSpans #0 ScopeSpans SchemaURL: InstrumentationScope telemetrygen Span #0 Trace ID : dfd830da170acfe567b12f87685d7917 Parent ID : 8e15b390dc6a1ccc ID : 165c300130532072 Name : okey-dokey Kind : Server Start time : 2023-07-29 20:29:16.026965 +0000 UTC End time : 2023-07-29 20:29:16.027089 +0000 UTC Status code : Ok Status message : Attributes: -> net.peer.ip: Str(1.2.3.4) -> peer.service: Str(telemetrygen-client) Span #1 Trace ID : dfd830da170acfe567b12f87685d7917 Parent ID : ID : 8e15b390dc6a1ccc Name : lets-go Kind : Client Start time : 2023-07-29 20:29:16.026956 +0000 UTC End time : 2023-07-29 20:29:16.027089 +0000 UTC Status code : Ok Status message : Attributes: -> net.peer.ip: Str(1.2.3.4) -> peer.service: Str(telemetrygen-server) ``` The default is `Unset` which is the current behaviour. **Link to tracking Issue:** 24286 **Testing:** Added unit tests which covers both valid and invalid inputs. **Documentation:** Command line arguments are self documenting via the usage info in the flag. Co-authored-by: Pablo Baeyens <[email protected]>
…ry#26114) Use the Timeout setting from ScraperHelper instead --------- Signed-off-by: Alex Boten <[email protected]>
Add missing parentheses for link.
This PR contains several simplifications within and relating to the new tokenization package: - `tokenize.Multiline` now returns a `bufio.splitFunc` without concern for a flush func. A flush func is applied later if necessary. - Remove `tokenize.Splitter`. `SplitterConfig` can now generate a `bufio.SplitFunc` directly. - Unexport `tokenize.Flusher`. `FlusherConfig` can now wrap a `bufio.SplitFunc` directly. (It does still create a struct to maintain state, but then wraps the split func with a receiver that interacts with this state.) - `fileconsumer`'s internal `splitter` package was also simplified. It may make sense to merge this into `tokenize` in a future PR, but this PR is large enough.
…telemetry#24764) **Link to tracking Issue:** open-telemetry#24034
…etry#26104) We are going to release a new version of Grafana Agent which includes two more Collector components. The Grafana Agent release will be on 2023-08-30, so ideally the PR should be merged on 2023-08-30 as well.
…6355) **Description:** Bumps `github.com/DataDog/opentelemetry-mapping-go` to v0.8.0, fixes crash with empty exponential histograms. **Link to tracking Issue:** Fixes open-telemetry#26103
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> The `go` directive was pointing to Go 1.19 instead of Go 1.20.
This just changes a very recently added package name. I think it matches typical naming conventions better, especially when viewed as part of open-telemetry#26241.
…ry#26357) Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.333 to 1.45.0 in /receiver/awsxrayreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.732 to 1.0.735 in /exporter/tencentcloudlogserviceexporter
**Link to tracking Issue:** open-telemetry#26304
…info (open-telemetry#25117) **Description:** Added saving instrumentation library information. Fix issue: open-telemetry#13642 How solved: 1. Add saving information about instrumentation scope for traces: processor/tailsamplingprocessor/processor.go:307 2. Sampled spans will now be put into the previous version of the instrumentation scope: processor/tailsamplingprocessor/processor.go:435 **Testing:** on production with high load. Unit tests in progress **Documentation:** no documentation changes
…try#26362) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> The add-label workflow is used by GitHub when manually adding labels to issues. When adding a new component to an issue, the workflow attempts to ping codeowners of the given component. However, the link to the ping codeowners script was outdated, and was failing. This change references the moved script. **Link to tracking Issue:** <Issue number if applicable> Resolves open-telemetry#26361 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.>
Description: Allows conversion of time to nanoseconds, microseconds, milliseconds or seconds Link to tracking Issue: Related to open-telemetry#24686 Testing: Unit tests for each converter Documentation: --------- Co-authored-by: Alex Boten <[email protected]> Co-authored-by: Tyler Helmuth <[email protected]> Co-authored-by: Evan Bradley <[email protected]>
…#26342) **Description:** <Describe what has changed.> Adds new config value `LogRecordDimensions` to influxdbexporter, similar to open-telemetry#23230. This allows the user to specify which otel attributes translate to InfluxDB tags, and which should be written to the `attributes` InfluxDB field. Incidentally, this change also updates the main dependency of influxdbreceiver, but no important changes were made to that module. **Link to tracking Issue:** influxdata/influxdb-observability#273
Add a link from the Loki receiver's readme to some of the helpers that can be used with it. closes open-telemetry#26352 Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: Juraci Paixão Kröhling <[email protected]>
…y#26457) Bump actions/checkout from 3 to 4 Bump github.com/IBM/sarama from 1.41.0 to 1.41.1 in /exporter/kafkaexporter Bump github.com/IBM/sarama from 1.41.0 to 1.41.1 in /receiver/kafkametricsreceiver Bump github.com/IBM/sarama from 1.41.0 to 1.41.1 in /receiver/kafkareceiver Bump github.com/antonmedv/expr from 1.14.3 to 1.15.0 in /pkg/stanza Bump github.com/antonmedv/expr from 1.14.3 to 1.15.0 in /receiver/receivercreator Bump github.com/apache/thrift from 0.18.1 to 0.19.0 in /exporter/jaegerthrifthttpexporter Bump github.com/apache/thrift from 0.18.1 to 0.19.0 in /receiver/jaegerreceiver Bump github.com/apache/thrift from 0.18.1 to 0.19.0 in /receiver/kafkareceiver Bump github.com/apache/thrift from 0.18.1 to 0.19.0 in /receiver/pulsarreceiver Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.45.0 to 1.45.2 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go-v2/config from 1.18.37 to 1.18.38 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/config from 1.18.37 to 1.18.38 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.35 to 1.13.36 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.35 to 1.13.36 in /extension/sigv4authextension Bump github.com/influxdata/influxdb-observability/common from 0.5.6 to 0.5.7 in /exporter/influxdbexporter Bump github.com/influxdata/influxdb-observability/common from 0.5.6 to 0.5.7 in /receiver/influxdbreceiver Bump github.com/influxdata/influxdb-observability/influx2otel from 0.5.6 to 0.5.7 in /receiver/influxdbreceiver Bump github.com/influxdata/influxdb-observability/otel2influx from 0.5.6 to 0.5.7 in /exporter/influxdbexporter Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /exporter/signalfxexporter Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /extension/observer/hostobserver Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /receiver/awscontainerinsightreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /receiver/hostmetricsreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /receiver/jmxreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.7 to 3.23.8 in /testbed Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.735 to 1.0.739 in /exporter/tencentcloudlogserviceexporter Bump github.com/wavefronthq/wavefront-sdk-go from 0.13.0 to 0.14.0 in /exporter/tanzuobservabilityexporter Bump golang.org/x/sys from 0.11.0 to 0.12.0 in /exporter/signalfxexporter Bump golang.org/x/sys from 0.11.0 to 0.12.0 in /pkg/stanza Bump golang.org/x/sys from 0.11.0 to 0.12.0 in /pkg/winperfcounters Bump golang.org/x/sys from 0.11.0 to 0.12.0 in /receiver/hostmetricsreceiver Bump golang.org/x/sys from 0.11.0 to 0.12.0 in /receiver/windowseventlogreceiver Bump golang.org/x/text from 0.12.0 to 0.13.0 in /cmd/configschema Bump golang.org/x/text from 0.12.0 to 0.13.0 in /cmd/mdatagen Bump golang.org/x/text from 0.12.0 to 0.13.0 in /internal/coreinternal Bump golang.org/x/text from 0.12.0 to 0.13.0 in /pkg/stanza Bump golang.org/x/text from 0.12.0 to 0.13.0 in /testbed Bump sigs.k8s.io/controller-runtime from 0.15.1 to 0.16.1 in /exporter/loadbalancingexporter
…etadata sending (open-telemetry#25145) **Description:** - [\*/datadog] Bump opentelemetry-mapping-go/\* to v0.7.1 - [exporter/datadog] Use reporter for exporter host as well
…hed objects (open-telemetry#26042) **Description:** Adds a new configuration option that allows excluding `DELETED` updates for watched objects. **Link to tracking Issue:** Closes open-telemetry#24904 **Testing:** New unit tests and tested locally **Documentation:** Updated the readme
I recently missed that func docs were missing when I merged some new functions. Also updated some godoc typos and renamed some function files to match our naming pattern. --------- Co-authored-by: Evan Bradley <[email protected]> Co-authored-by: Curtis Robert <[email protected]>
…y#26459) Bump actions/checkout from 3 to 4 Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.739 to 1.0.740 in /exporter/tencentcloudlogserviceexporter
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | golang | stage | minor | `1.20` -> `1.21` | --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi43OS4xIiwidXBkYXRlZEluVmVyIjoiMzYuNzkuMSIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
…pen-telemetry#26318) **Description:** Added new metric -- postgresql.database_locks -- the number of database locks . **Link to tracking Issue:** open-telemetry#26317 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Antoine Toulme <[email protected]>
…y#26383) **Description:** Remove exposed function, only keep NewFactory to pass checkapi **Link to tracking Issue:** open-telemetry#26304
…etry#24834) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.>
**Description:** Fixed a bug introduced by [open-telemetry#25174](open-telemetry#25174) There was check that was supposed to ensure that all resource attributes added to a metric were scalar, but it was really checking if the number of resource attributes on a metric was the same as the total number of possible scalar resource attributes defined in the config. This check has been updated to explicitly verify that all of the resource attributes on the metric are scalar. Bug examples: - A column metric indexed by a column attribute has two scalar resource attributes with different names but the same oid value. They are the only two scalar RAs defined in the config. Since the oids are added to a map whose length is checked, they are seen as one value and the comparison fails so many resources are created instead of one. - A column metric indexed by a column attribute has only one scalar resource attribute when two possible attributes are defined in the config. The check fails and many resources are created instead of one. **Testing:** - Test that a metric with one scalar resource attribute when two are available still creates only one resource - First bug does not feel necessary to unit test, it has been tested locally and is fixed. **Documentation:** - N/A
…metry#25894) **Description:** Adds new `k8s.pod.memory.utilization` and `container.memory.utilization` metrics that represent the ratio of memory used vs limits set. The metrics are only emitted for pods/containers that have defined resource limits. It takes advantage of the pod metadata to acquire the container limits. A pod limit is computed as the sum of all the container limits and if any container limit is zero or undefined the pod limit is also considered undefined. **Link to tracking Issue:** Related to open-telemetry#24905 **Testing:** Unit tests and local testing
**Description:** This PR creates a gh action that generates a weekly report on repo statistics. It delivers on the requirements specified in open-telemetry#24672 You can see the sample output here: kevinslin#16 **Link to tracking Issue:** open-telemetry#24672 **Testing:** Manual testing in fork: https://github.com/kevinslin/opentelemetry-collector-contrib/actions Example output: kevinslin#17 **Documentation:** The architecture: - we use `actions/github-script@v6` to make calls to the gh apis - we require installing `js-yaml` in order to parse `metadata.yaml` files in order to get components. this dependency is installed during the github action run and not persisted Some caveats about the logic: - when this action runs, it looks back the previous 7 days and gets issues created in that time period, normalizing times to UTC - eg. if running this on wednesday (eg. 2023-08-25 17:35:00), it will scan issues from the previous wednesday (2023-08-18 00:00:00Z) to beginning of this wednesday (2023-08-28 0:00:00Z) - this action writes the json payload of the report inside the issue. the payload is parsed by future reports to calculate deltas - the report issue has a custom label: `report` - this is used so we can properly filter previous issues when calculating deltas. the [github issues api](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#list-repository-issues) only does filtering based on labels and `since` date This action currently runs every Tuesday at 1AM UTC --------- Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Tyler Helmuth <[email protected]>
…27267) Picking up codeowners from .GITHUB/CODEOWNERS
**Description:** <Describe what has changed.> Allows setting empty metric units in mdatagen. Example of using it https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27091/files **Tracking Issues:** open-telemetry#27089 open-telemetry#10553
**Description:** The existing k8s example configures the filelog receiver to `start_at: beginning`. This results in a significant amount of data to be ingested on startup, and significant duplicate data on a collector restart. I propose we recommend using `start_at:end` for default k8s log ingestion.
This overhauls a document in `pkg/stanza` which describes how to chain operators together. - Disambiguates the term "pipelines" but introducing the term "operator sequences". - Reworks all examples to show the context of being used in a full receiver configuration. - Removes references to input and output operators, which are either abstracted or unused. - Removes some extraneous examples. - Clarifies how to output from a non-linear pipeline.
…etry#26506) **Description:** Add support to customize metric name and its attributes. **Link to tracking Issue:** open-telemetry#26505 **Testing:** - **Documentation:** self-documented in added flags --------- Signed-off-by: Claudio B <[email protected]> Co-authored-by: Alex Boten <[email protected]> Co-authored-by: Sean Marciniak <[email protected]>
…emetry#27286) Name Windows event provider on error msg
open-telemetry#27294) This fixes a bug detected while attempting to migrate test to the new `splittest` framework. Generally speaking, the responsibility of a `bufio.SplitFunc` is to parse a token from a given buffer (`[]byte`). However, the split func does not have control over the size of the buffer, so it must be able to ask for more data. The mechanism for asking for more data is to return `0, nil, nil`. A split func is also told whether there is any more data to read. This allows it to chose whether to "give up" and return a truncated token, or to insist that it will wait until there is more data (which may never happen). This particular function is parsing tokens based on a simple numerical prefix which indicates how long the token will be. e.g. `54 This is the actual token and it is 54 characters long.` The problem is that the function would give up prematurely and return a truncated token. The proper behavior is to ask for more data _unless_ the function is specifically told that there is no more data to receive. This fixes the behavior so that whenever we are able to parse an expected length but find there is not enough data in the buffer to fulfill the expectation, we ask for more data. It only returns a truncated token when there is no more data to ask for.
…y#27296) Follows open-telemetry#27275 All tests have been migrated away from the old `splittest` framework in favor of the newer more thorough test. This removes the old version and renames the file containing the new one.
…pen-telemetry#27397) Reverts open-telemetry#27286 This is failing tests on main. I apologize for not enabling Windows tests on the PR. @pjanotti, would you mind updating tests and resubmitting?
open-telemetry#27399) **Description:** Restore open-telemetry#27286 (see PR open-telemetry#27397) and add missing test update. **Link to tracking Issue:** N/A **Testing:** Ran test locally. **Documentation:** N/A cc @djaglowski @songy23
**Description:** Deprecate Parquet exporter before removing it altogether. **Link to tracking Issue:** open-telemetry#27285
…ames (open-telemetry#20896) Fixes open-telemetry#3148 This change was initially created to only fix open-telemetry#20731 by replacing the slash `/` characters in component names with a tilde `~`. After that, we decided that it is a breaking change, and so it's better to fix other characters as well in a single breaking change.
…rim package (open-telemetry#27260) This extracts the "max length" responsibility from the scanner. A couple benefits of this: 1. The function can be applied _after_ the flush function. Previously, if a token was flushed due to timing, we were not enforcing the max length. 2. It makes the function directly testable. 4. We can simplify the scanner constructor, which previously had a parameter for the buffer size which was only used for testing the behavior of the extracted function. This is now tested within the trim function.
…y#27400) Bump actions/checkout from 3 to 4 Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.19 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.20 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.20 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.20 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.45.17 to 1.45.20 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go-v2/config from 1.18.42 to 1.18.43 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/config from 1.18.42 to 1.18.43 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.40 to 1.13.41 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.40 to 1.13.41 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/service/sts from 1.22.0 to 1.23.0 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/service/sts from 1.22.0 to 1.23.0 in /extension/sigv4authextension Bump github.com/aws/aws-xray-sdk-go from 1.8.1 to 1.8.2 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-xray-sdk-go from 1.8.1 to 1.8.2 in /internal/aws/xray/testdata/sampleserver Bump github.com/jcchavezs/porto from 0.4.0 to 0.5.1 in /internal/tools Bump github.com/rs/cors from 1.10.0 to 1.10.1 in /receiver/opencensusreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /exporter/signalfxexporter Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /extension/observer/hostobserver Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /processor/resourcedetectionprocessor Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /receiver/awscontainerinsightreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /receiver/hostmetricsreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /receiver/jmxreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.8 to 3.23.9 in /testbed Bump github.com/snowflakedb/gosnowflake from 1.6.24 to 1.6.25 in /receiver/sqlqueryreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.756 to 1.0.759 in /exporter/tencentcloudlogserviceexporter Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /extension/observer/dockerobserver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /internal/coreinternal Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/aerospikereceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/apachereceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/dockerstatsreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/elasticsearchreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/flinkmetricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/jmxreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/kafkametricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/memcachedreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/mongodbreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/mysqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/nginxreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/postgresqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/redisreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/sqlqueryreceiver Bump github.com/testcontainers/testcontainers-go from 0.23.0 to 0.25.0 in /receiver/zookeeperreceiver Bump github.com/vmware/govmomi from 0.31.0 to 0.32.0 in /receiver/vcenterreceiver Bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.44.0 to 0.45.0 in /receiver/opencensusreceiver Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /examples/demo/client Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /internal/aws/metrics Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /internal/coreinternal Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /internal/metadataproviders Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /processor/routingprocessor Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /receiver/opencensusreceiver Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /receiver/simpleprometheusreceiver/examples/federation/prom-counter Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /receiver/solacereceiver Bump go.opentelemetry.io/otel from 1.18.0 to 1.19.0 in /receiver/statsdreceiver Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc from 0.41.0 to 0.42.0 in /examples/demo/client Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc from 0.41.0 to 0.42.0 in /examples/demo/server Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp from 0.41.0 to 0.42.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.18.0 to 1.19.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.18.0 to 1.19.0 in /examples/demo/client Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc from 1.18.0 to 1.19.0 in /examples/demo/server Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp from 1.18.0 to 1.19.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel/exporters/prometheus from 0.41.0 to 0.42.0 in /receiver/simpleprometheusreceiver/examples/federation/prom-counter Bump go.opentelemetry.io/otel/metric from 1.18.0 to 1.19.0 in /examples/demo/server Bump go.opentelemetry.io/otel/metric from 1.18.0 to 1.19.0 in /processor/routingprocessor Bump go.opentelemetry.io/otel/metric from 1.18.0 to 1.19.0 in /receiver/simpleprometheusreceiver/examples/federation/prom-counter Bump go.opentelemetry.io/otel/schema from 0.0.4 to 0.0.7 in /processor/schemaprocessor Bump go.opentelemetry.io/otel/sdk from 1.18.0 to 1.19.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel/sdk from 1.18.0 to 1.19.0 in /examples/demo/client Bump go.opentelemetry.io/otel/sdk from 1.18.0 to 1.19.0 in /internal/metadataproviders Bump go.opentelemetry.io/otel/sdk from 1.18.0 to 1.19.0 in /receiver/carbonreceiver Bump go.opentelemetry.io/otel/sdk from 1.18.0 to 1.19.0 in /receiver/opencensusreceiver Bump go.opentelemetry.io/otel/sdk/metric from 0.41.0 to 1.19.0 in /cmd/telemetrygen Bump go.opentelemetry.io/otel/sdk/metric from 0.41.0 to 1.19.0 in /examples/demo/client Bump go.opentelemetry.io/otel/sdk/metric from 0.41.0 to 1.19.0 in /examples/demo/server Bump go.opentelemetry.io/otel/sdk/metric from 0.41.0 to 1.19.0 in /receiver/simpleprometheusreceiver/examples/federation/prom-counter Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /examples/demo/server Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /internal/coreinternal Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /pkg/ottl Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /processor/routingprocessor Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /processor/tailsamplingprocessor Bump go.opentelemetry.io/otel/trace from 1.18.0 to 1.19.0 in /receiver/opencensusreceiver --------- Co-authored-by: Yang Song <[email protected]>
This adds an example for setting headers on the check. Signed-off-by: Alex Boten <[email protected]>
…elemetry#27418) This reworks a recent addition (See open-telemetry#27064) to how we handle rotated files. The solution depends upon re-reading a file's fingerprint. This is unchanged, but most of the implementation is now localized to the reader struct.
…age (open-telemetry#27416) Follows open-telemetry#27396 This PR creates an internal `reader` package and moves directly related structs into it. I intend to clean up this codebase substantially from here. This is just a first step that creates a crude boundary between concerns. There are many exported fields which can later be abstracted, but currently the codebase has many direct interactions. Tests remain in the `fileconsumer` package for now but will be migrated once there are cleaner interfaces to test.
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/releases">actions/checkout's releases</a>.</em></p> <blockquote> <h2>v4.0.0</h2> <h2>What's Changed</h2> <ul> <li>Update default runtime to node20 by <a href="https://github.com/takost"><code>@takost</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1436">actions/checkout#1436</a></li> <li>Support fetching without the --progress option by <a href="https://github.com/simonbaird"><code>@simonbaird</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1067">actions/checkout#1067</a></li> <li>Release 4.0.0 by <a href="https://github.com/takost"><code>@takost</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1447">actions/checkout#1447</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/takost"><code>@takost</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1436">actions/checkout#1436</a></li> <li><a href="https://github.com/simonbaird"><code>@simonbaird</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1067">actions/checkout#1067</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v3...v4.0.0">https://github.com/actions/checkout/compare/v3...v4.0.0</a></p> <h2>v3.6.0</h2> <h2>What's Changed</h2> <ul> <li>Mark test scripts with Bash'isms to be run via Bash by <a href="https://github.com/dscho"><code>@dscho</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1377">actions/checkout#1377</a></li> <li>Add option to fetch tags even if fetch-depth > 0 by <a href="https://github.com/RobertWieczoreck"><code>@RobertWieczoreck</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/579">actions/checkout#579</a></li> <li>Release 3.6.0 by <a href="https://github.com/luketomlinson"><code>@luketomlinson</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1437">actions/checkout#1437</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/RobertWieczoreck"><code>@RobertWieczoreck</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/579">actions/checkout#579</a></li> <li><a href="https://github.com/luketomlinson"><code>@luketomlinson</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1437">actions/checkout#1437</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v3.5.3...v3.6.0">https://github.com/actions/checkout/compare/v3.5.3...v3.6.0</a></p> <h2>v3.5.3</h2> <h2>What's Changed</h2> <ul> <li>Fix: Checkout Issue in self hosted runner due to faulty submodule check-ins by <a href="https://github.com/megamanics"><code>@megamanics</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1196">actions/checkout#1196</a></li> <li>Fix typos found by codespell by <a href="https://github.com/DimitriPapadopoulos"><code>@DimitriPapadopoulos</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1287">actions/checkout#1287</a></li> <li>Add support for sparse checkouts by <a href="https://github.com/dscho"><code>@dscho</code></a> and <a href="https://github.com/dfdez"><code>@dfdez</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1369">actions/checkout#1369</a></li> <li>Release v3.5.3 by <a href="https://github.com/TingluoHuang"><code>@TingluoHuang</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1376">actions/checkout#1376</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/megamanics"><code>@megamanics</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1196">actions/checkout#1196</a></li> <li><a href="https://github.com/DimitriPapadopoulos"><code>@DimitriPapadopoulos</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1287">actions/checkout#1287</a></li> <li><a href="https://github.com/dfdez"><code>@dfdez</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1369">actions/checkout#1369</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v3...v3.5.3">https://github.com/actions/checkout/compare/v3...v3.5.3</a></p> <h2>v3.5.2</h2> <h2>What's Changed</h2> <ul> <li>Fix: Use correct API url / endpoint in GHES by <a href="https://github.com/fhammerl"><code>@fhammerl</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1289">actions/checkout#1289</a> based on <a href="https://redirect.github.com/actions/checkout/issues/1286">#1286</a> by <a href="https://github.com/1newsr"><code>@1newsr</code></a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v3.5.1...v3.5.2">https://github.com/actions/checkout/compare/v3.5.1...v3.5.2</a></p> <h2>v3.5.1</h2> <h2>What's Changed</h2> <ul> <li>Improve checkout performance on Windows runners by upgrading <code>@actions/github</code> dependency by <a href="https://github.com/BrettDong"><code>@BrettDong</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1246">actions/checkout#1246</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/BrettDong"><code>@BrettDong</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/1246">actions/checkout#1246</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2>v4.1.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1396">Add support for partial checkout filters</a></li> </ul> <h2>v4.0.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1067">Support fetching without the --progress option</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1436">Update to node20</a></li> </ul> <h2>v3.6.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1377">Fix: Mark test scripts with Bash'isms to be run via Bash</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/579">Add option to fetch tags even if fetch-depth > 0</a></li> </ul> <h2>v3.5.3</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1196">Fix: Checkout fail in self-hosted runners when faulty submodule are checked-in</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1287">Fix typos found by codespell</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1369">Add support for sparse checkouts</a></li> </ul> <h2>v3.5.2</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1289">Fix api endpoint for GHES</a></li> </ul> <h2>v3.5.1</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1246">Fix slow checkout on Windows</a></li> </ul> <h2>v3.5.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1237">Add new public key for known_hosts</a></li> </ul> <h2>v3.4.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1209">Upgrade codeql actions to v2</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1210">Upgrade dependencies</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1225">Upgrade <code>@actions/io</code></a></li> </ul> <h2>v3.3.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/1045">Implement branch list using callbacks from exec function</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1050">Add in explicit reference to private checkout options</a></li> <li>[Fix comment typos (that got added in <a href="https://redirect.github.com/actions/checkout/issues/770">#770</a>)](<a href="https://redirect.github.com/actions/checkout/pull/1057">actions/checkout#1057</a>)</li> </ul> <h2>v3.2.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/942">Add GitHub Action to perform release</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/967">Fix status badge</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1002">Replace datadog/squid with ubuntu/squid Docker image</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/964">Wrap pipeline commands for submoduleForeach in quotes</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1029">Update <code>@actions/io</code> to 1.1.2</a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/1039">Upgrading version to 3.2.0</a></li> </ul> <h2>v3.1.0</h2> <ul> <li><a href="https://redirect.github.com/actions/checkout/pull/939">Use <code>@actions/core</code> <code>saveState</code> and <code>getState</code></a></li> <li><a href="https://redirect.github.com/actions/checkout/pull/922">Add <code>github-server-url</code> input</a></li> </ul> <h2>v3.0.2</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/checkout/commit/8ade135a41bc03ea155e62e844d188df1ea18608"><code>8ade135</code></a> Prepare 4.1.0 release (<a href="https://redirect.github.com/actions/checkout/issues/1496">#1496</a>)</li> <li><a href="https://github.com/actions/checkout/commit/c533a0a4cfc4962971818edcfac47a2899e69799"><code>c533a0a</code></a> Add support for partial checkout filters (<a href="https://redirect.github.com/actions/checkout/issues/1396">#1396</a>)</li> <li><a href="https://github.com/actions/checkout/commit/72f2cec99f417b1a1c5e2e88945068983b7965f9"><code>72f2cec</code></a> Update README.md for V4 (<a href="https://redirect.github.com/actions/checkout/issues/1452">#1452</a>)</li> <li><a href="https://github.com/actions/checkout/commit/3df4ab11eba7bda6032a0b82a6bb43b11571feac"><code>3df4ab1</code></a> Release 4.0.0 (<a href="https://redirect.github.com/actions/checkout/issues/1447">#1447</a>)</li> <li><a href="https://github.com/actions/checkout/commit/8b5e8b768746b50394015010d25e690bfab9dfbc"><code>8b5e8b7</code></a> Support fetching without the --progress option (<a href="https://redirect.github.com/actions/checkout/issues/1067">#1067</a>)</li> <li><a href="https://github.com/actions/checkout/commit/97a652b80035363df47baee5031ec8670b8878ac"><code>97a652b</code></a> Update default runtime to node20 (<a href="https://redirect.github.com/actions/checkout/issues/1436">#1436</a>)</li> <li>See full diff in <a href="https://github.com/actions/checkout/compare/v3...v4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/checkout&package-manager=github_actions&previous-version=3&new-version=4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…metry#27269) **Description:** Change entirely how dependabot update entries are generated, by using the metadata.yaml status to find which components are most important in the distribution. The code now takes into account the distributions and the stability of the component as a score to decide whether to push the component. Go modules that don't have an associated metadata.yaml are not considered and therefore not present in the module updates path. **Link to tracking Issue:** open-telemetry#19410
…elemetry#27253) **Description:** Move the filestats receiver to beta stability **Link to tracking Issue:** Fixes open-telemetry#27252
Prune histograms when the dimension cache evictions are removed **Description:** Prunes histograms when the dimension cache is pruned. This prevents metric series from growing indefinitely **Link to tracking Issue:** open-telemetry#27080 **Testing:** I modified the the existing test to check `histograms` length instead of dimensions cache length. This required simulating ticks to hit the exportMetrics function **Documentation:** <Describe the documentation added.> Co-authored-by: Sean Marciniak <[email protected]>
…lemetry#27266) Co-authored-by: Sean Marciniak <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Link to tracking Issue:
Testing:
Documentation: