honeycomb-beeline 2.6.0 → 2.7.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.github/ISSUE_TEMPLATE/bug_report.md +27 -0
- data/.github/ISSUE_TEMPLATE/feature_request.md +25 -0
- data/.github/ISSUE_TEMPLATE/question-discussion.md +14 -0
- data/.github/ISSUE_TEMPLATE/security-vulnerability-report.md +22 -0
- data/.github/PULL_REQUEST_TEMPLATE.md +20 -0
- data/.rubocop.yml +1 -0
- data/CHANGELOG.md +12 -0
- data/CODE_OF_CONDUCT.md +3 -72
- data/CONTRIBUTING.md +3 -0
- data/Gemfile.lock +1 -1
- data/OSSMETADATA +1 -0
- data/README.md +1 -0
- data/RELEASING.md +11 -0
- data/SECURITY.md +3 -0
- data/SUPPORT.md +3 -0
- data/lib/honeycomb/beeline/version.rb +1 -1
- data/lib/honeycomb/integrations/active_support.rb +9 -0
- metadata +12 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 97016b5bcb57ce01fa980218fac7d8b71b3b145dec5ff30ad5ab9693d070d665
|
4
|
+
data.tar.gz: df32abbd87b653800ec3ebe2693cc3008593e307ee70ef1f5ab9333f139a96ba
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 51757f1553274cda4c354d16f50998745c41b0f89f4d27d763d8e81f2fe9142a1f491ea3208eb73d26211a81d5c2f2f15e282b9555fd4416d3a20f8cb3373f23
|
7
|
+
data.tar.gz: 0ef3666a518f2e965972967af8fb13d7597bd132026bc6ed8580b93458f0f1cf227a6ab05204dbc31f34da520f25e9f97201d3a9347173da4e7cdece0b6875b0
|
@@ -0,0 +1,27 @@
|
|
1
|
+
---
|
2
|
+
name: Bug report
|
3
|
+
about: Let us know if something is not working as expected
|
4
|
+
title: ''
|
5
|
+
labels: 'type: bug'
|
6
|
+
assignees: ''
|
7
|
+
|
8
|
+
---
|
9
|
+
|
10
|
+
<!---
|
11
|
+
Thank you for taking the time to report bugs!
|
12
|
+
|
13
|
+
We love code snippets and links to repositories that reproduce the issue, but understand if you don't have the time to add them. We'll do our best with the info you provide, and might ask follow-up questions.
|
14
|
+
|
15
|
+
Please see our [OSS process document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#) to get an idea of how we operate.
|
16
|
+
--->
|
17
|
+
|
18
|
+
**Versions**
|
19
|
+
|
20
|
+
- Ruby:
|
21
|
+
- Beeline:
|
22
|
+
|
23
|
+
**Steps to reproduce**
|
24
|
+
|
25
|
+
1.
|
26
|
+
|
27
|
+
**Additional context**
|
@@ -0,0 +1,25 @@
|
|
1
|
+
---
|
2
|
+
name: Feature request
|
3
|
+
about: Suggest an idea for this project
|
4
|
+
title: ''
|
5
|
+
labels: 'type: enhancement'
|
6
|
+
assignees: ''
|
7
|
+
|
8
|
+
---
|
9
|
+
|
10
|
+
<!---
|
11
|
+
Thank you for contributing an idea to this project!
|
12
|
+
|
13
|
+
Please see our [OSS process document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#) to get an idea of how we operate.
|
14
|
+
--->
|
15
|
+
|
16
|
+
**Is your feature request related to a problem? Please describe.**
|
17
|
+
|
18
|
+
|
19
|
+
**Describe the solution you'd like**
|
20
|
+
|
21
|
+
|
22
|
+
**Describe alternatives you've considered**
|
23
|
+
|
24
|
+
|
25
|
+
**Additional context**
|
@@ -0,0 +1,14 @@
|
|
1
|
+
---
|
2
|
+
name: Question/Discussion
|
3
|
+
about: General question about how things work or a discussion
|
4
|
+
title: ''
|
5
|
+
labels: 'type: discussion'
|
6
|
+
assignees: ''
|
7
|
+
|
8
|
+
---
|
9
|
+
|
10
|
+
<!---
|
11
|
+
Thank you for taking the time to say hello!
|
12
|
+
|
13
|
+
Please see our [OSS process document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#) to get an idea of how we operate.
|
14
|
+
--->
|
@@ -0,0 +1,22 @@
|
|
1
|
+
---
|
2
|
+
name: Security vulnerability report
|
3
|
+
about: Let us know if you discover a security vulnerability
|
4
|
+
title: ''
|
5
|
+
labels: 'type: security'
|
6
|
+
assignees: ''
|
7
|
+
|
8
|
+
---
|
9
|
+
|
10
|
+
<!---
|
11
|
+
Thank you for taking the time to report security vulnerabilities!
|
12
|
+
|
13
|
+
Please see our [OSS process document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#) to get an idea of how we operate.
|
14
|
+
--->
|
15
|
+
**Versions**
|
16
|
+
|
17
|
+
- Ruby:
|
18
|
+
- Beeline:
|
19
|
+
|
20
|
+
**Description**
|
21
|
+
|
22
|
+
(Please include any relevant CVE advisory links)
|
@@ -0,0 +1,20 @@
|
|
1
|
+
<!--
|
2
|
+
Thank you for contributing to the project! 💜
|
3
|
+
Please make sure to:
|
4
|
+
- Chat with us first if this is a big change
|
5
|
+
- Open a new issue (or comment on an existing one)
|
6
|
+
- We want to make sure you don't spend time implementing something we might have to say No to
|
7
|
+
- Add unit tests
|
8
|
+
- Mention any relevant issues in the PR description (e.g. "Fixes #123")
|
9
|
+
|
10
|
+
Please see our [OSS process document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#) to get an idea of how we operate.
|
11
|
+
-->
|
12
|
+
|
13
|
+
## Which problem is this PR solving?
|
14
|
+
|
15
|
+
-
|
16
|
+
|
17
|
+
## Short description of the changes
|
18
|
+
|
19
|
+
-
|
20
|
+
|
data/.rubocop.yml
CHANGED
data/CHANGELOG.md
CHANGED
@@ -1,5 +1,17 @@
|
|
1
1
|
# beeline-ruby changelog
|
2
2
|
|
3
|
+
## 2.7.0 2021-09-03
|
4
|
+
|
5
|
+
### Improvements
|
6
|
+
|
7
|
+
- add `error` and `error_detail` fields to spans from `ActiveSupport::Notification` events that contain an exception (#166) | [@leviwilson](https://github.com/leviwilson)
|
8
|
+
|
9
|
+
### Maintenance
|
10
|
+
|
11
|
+
- Add issue and PR templates (#165) | [@vreynolds](https://github.com/vreynolds)
|
12
|
+
- Add OSS lifecycle badge (#164) | [@vreynolds](https://github.com/vreynolds)
|
13
|
+
- Add community health files (#163) | [@vreynolds](https://github.com/vreynolds)
|
14
|
+
|
3
15
|
## 2.6.0 2021-07-23
|
4
16
|
|
5
17
|
### Added
|
data/CODE_OF_CONDUCT.md
CHANGED
@@ -1,74 +1,5 @@
|
|
1
|
-
#
|
1
|
+
# Code of Conduct
|
2
2
|
|
3
|
-
|
3
|
+
This project has adopted the Honeycomb User Community Code of Conduct to clarify expected behavior in our community.
|
4
4
|
|
5
|
-
|
6
|
-
contributors and maintainers pledge to making participation in our project and
|
7
|
-
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
-
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
-
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
-
orientation.
|
11
|
-
|
12
|
-
## Our Standards
|
13
|
-
|
14
|
-
Examples of behavior that contributes to creating a positive environment
|
15
|
-
include:
|
16
|
-
|
17
|
-
* Using welcoming and inclusive language
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
19
|
-
* Gracefully accepting constructive criticism
|
20
|
-
* Focusing on what is best for the community
|
21
|
-
* Showing empathy towards other community members
|
22
|
-
|
23
|
-
Examples of unacceptable behavior by participants include:
|
24
|
-
|
25
|
-
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
-
advances
|
27
|
-
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
-
* Public or private harassment
|
29
|
-
* Publishing others' private information, such as a physical or electronic
|
30
|
-
address, without explicit permission
|
31
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
-
professional setting
|
33
|
-
|
34
|
-
## Our Responsibilities
|
35
|
-
|
36
|
-
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
38
|
-
response to any instances of unacceptable behavior.
|
39
|
-
|
40
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
-
threatening, offensive, or harmful.
|
45
|
-
|
46
|
-
## Scope
|
47
|
-
|
48
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
-
when an individual is representing the project or its community. Examples of
|
50
|
-
representing a project or community include using an official project e-mail
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
53
|
-
further defined and clarified by project maintainers.
|
54
|
-
|
55
|
-
## Enforcement
|
56
|
-
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
-
reported by contacting the project team at me@martinholman.co.nz. All
|
59
|
-
complaints will be reviewed and investigated and will result in a response that
|
60
|
-
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
-
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
-
Further details of specific enforcement policies may be posted separately.
|
63
|
-
|
64
|
-
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
-
faith may face temporary or permanent repercussions as determined by other
|
66
|
-
members of the project's leadership.
|
67
|
-
|
68
|
-
## Attribution
|
69
|
-
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
-
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
-
|
73
|
-
[homepage]: http://contributor-covenant.org
|
74
|
-
[version]: http://contributor-covenant.org/version/1/4/
|
5
|
+
https://www.honeycomb.io/honeycomb-user-community-code-of-conduct/
|
data/CONTRIBUTING.md
ADDED
data/Gemfile.lock
CHANGED
data/OSSMETADATA
ADDED
@@ -0,0 +1 @@
|
|
1
|
+
osslifecycle=maintenance
|
data/README.md
CHANGED
@@ -1,5 +1,6 @@
|
|
1
1
|
# Honeycomb Beeline for Ruby
|
2
2
|
|
3
|
+
[![OSS Lifecycle](https://img.shields.io/osslifecycle/honeycombio/beeline-ruby)](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md)
|
3
4
|
[![Build Status](https://circleci.com/gh/honeycombio/beeline-ruby.svg?style=svg)](https://circleci.com/gh/honeycombio/beeline-ruby)
|
4
5
|
[![Gem Version](https://badge.fury.io/rb/honeycomb-beeline.svg)](https://badge.fury.io/rb/honeycomb-beeline)
|
5
6
|
[![codecov](https://codecov.io/gh/honeycombio/beeline-ruby/branch/main/graph/badge.svg)](https://codecov.io/gh/honeycombio/beeline-ruby)
|
data/RELEASING.md
ADDED
@@ -0,0 +1,11 @@
|
|
1
|
+
# Releasing
|
2
|
+
|
3
|
+
- Update the version number in `lib/honeycomb/beeline/version`.
|
4
|
+
- Run `bundle lock`.
|
5
|
+
- Confirm the version number update appears in `Gemfile.lock`
|
6
|
+
- Update `CHANGELOG.md` with the changes since the last release.
|
7
|
+
- Commit changes, push, and open a release preparation pull request for review.
|
8
|
+
- Once the pull request is merged, fetch the updated `main` branch.
|
9
|
+
- Apply a tag for the new version on the merged commit: vX.Y.Z, for example v1.1.2.
|
10
|
+
- Push the new version tag up to the project repository to kick off build and artifact publishing to GitHub and the Gems registry.
|
11
|
+
- Publish the draft release in GitHub.
|
data/SECURITY.md
ADDED
data/SUPPORT.md
ADDED
@@ -51,6 +51,15 @@ module Honeycomb
|
|
51
51
|
value = value.to_unsafe_hash if value.respond_to?(:to_unsafe_hash)
|
52
52
|
span.add_field("#{name}.#{key}", value)
|
53
53
|
end
|
54
|
+
|
55
|
+
# If the notification event has recorded an exception, add the
|
56
|
+
# Beeline's usual error fields to the span.
|
57
|
+
# * Uses the 2-element array on :exception in the event payload
|
58
|
+
# to support Rails 4. If Rails 4 support is dropped, consider
|
59
|
+
# the :exception_object added in Rails 5.
|
60
|
+
error, error_detail = payload[:exception]
|
61
|
+
span.add_field("error", error) if error
|
62
|
+
span.add_field("error_detail", error_detail) if error_detail
|
54
63
|
end
|
55
64
|
end
|
56
65
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: honeycomb-beeline
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 2.
|
4
|
+
version: 2.7.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Martin Holman
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2021-07
|
11
|
+
date: 2021-09-07 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: libhoney
|
@@ -252,6 +252,11 @@ files:
|
|
252
252
|
- ".circleci/setup-rubygems.sh"
|
253
253
|
- ".editorconfig"
|
254
254
|
- ".github/CODEOWNERS"
|
255
|
+
- ".github/ISSUE_TEMPLATE/bug_report.md"
|
256
|
+
- ".github/ISSUE_TEMPLATE/feature_request.md"
|
257
|
+
- ".github/ISSUE_TEMPLATE/question-discussion.md"
|
258
|
+
- ".github/ISSUE_TEMPLATE/security-vulnerability-report.md"
|
259
|
+
- ".github/PULL_REQUEST_TEMPLATE.md"
|
255
260
|
- ".github/dependabot.yml"
|
256
261
|
- ".github/workflows/add-to-project.yml"
|
257
262
|
- ".github/workflows/apply-labels.yml"
|
@@ -264,12 +269,17 @@ files:
|
|
264
269
|
- Appraisals
|
265
270
|
- CHANGELOG.md
|
266
271
|
- CODE_OF_CONDUCT.md
|
272
|
+
- CONTRIBUTING.md
|
267
273
|
- CONTRIBUTORS.md
|
268
274
|
- Gemfile
|
269
275
|
- Gemfile.lock
|
270
276
|
- LICENSE
|
277
|
+
- OSSMETADATA
|
271
278
|
- README.md
|
279
|
+
- RELEASING.md
|
272
280
|
- Rakefile
|
281
|
+
- SECURITY.md
|
282
|
+
- SUPPORT.md
|
273
283
|
- UPGRADING.md
|
274
284
|
- bin/console
|
275
285
|
- bin/setup
|