metrics 0.8.0 → 0.9.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9a0802f7beb149dcdce020eb36925fa4045016b45de6f89b4550b695db5c992b
4
- data.tar.gz: 891f6c7e9081ea55ffca2ef6cf701bfafaacd41d2521ee11b93ac152b0067e46
3
+ metadata.gz: 1b477758de3efc0c6e9f8413e7ae7f518387bbc9bb55164f4cceaf1d049e0274
4
+ data.tar.gz: c326efa64964828683525a305ae5cd8dabe87b471315cf1ff090a4d77f3ac540
5
5
  SHA512:
6
- metadata.gz: f09de9a1ffaad3e083f265956dd583916f19e5625b2f302b3dc7c8e8aa2b084ad5bd4e1b93a6e3cf91f2d40d45e5e16330bc100375c191e9e29c6f1773af8b24
7
- data.tar.gz: a6d341a4b630f02f34a1640fac5549815e2f3581dbff9a9f0a847bb7f983c43eb7f379577b4c60537c02e1a2ace3861c4c3c55061eb094447ab31b7c259c02fb
6
+ metadata.gz: edbc02219eb5edfb389e5cbc7124d3a7f6bd0654d7af82d7ab17d0eb52f3b1b4085bb41bffcca536ecd53e32c683a67fa19d2dd957076785b54595a5aad4b401
7
+ data.tar.gz: 864f4b88279171df6fc0e5e34ceda481cd6da3385aa486cfaf19685c65b3a787a737718772b4bd6d32a93cd2a99894601d698920dcc3e72b11498bb57c43568c
checksums.yaml.gz.sig CHANGED
Binary file
@@ -3,11 +3,17 @@
3
3
  # Released under the MIT License.
4
4
  # Copyright, 2021-2023, by Samuel Williams.
5
5
 
6
+ require 'console/event/failure'
7
+
6
8
  module Metrics
7
9
  # Require a specific trace backend.
8
10
  def self.require_backend(env = ENV)
9
- if path = env['METRICS_BACKEND']
10
- require(path)
11
+ if backend = env['METRICS_BACKEND']
12
+ begin
13
+ require(backend)
14
+ rescue LoadError => error
15
+ ::Console::Event::Failure.for(error).emit(self, "Unable to load metrics backend!", backend: backend, severity: :warn)
16
+ end
11
17
 
12
18
  Metrics.extend(Backend::Interface)
13
19
  end
@@ -4,5 +4,5 @@
4
4
  # Copyright, 2021-2023, by Samuel Williams.
5
5
 
6
6
  module Metrics
7
- VERSION = "0.8.0"
7
+ VERSION = "0.9.0"
8
8
  end
data/license.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # MIT License
2
2
 
3
- Copyright, 2021-2023, by Samuel Williams.
3
+ Copyright, 2021-2024, by Samuel Williams.
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining a copy
6
6
  of this software and associated documentation files (the "Software"), to deal
data/readme.md CHANGED
@@ -11,7 +11,13 @@ Capture metrics about code execution in a vendor agnostic way. As the author of
11
11
 
12
12
  ## Usage
13
13
 
14
- Please see the [project documentation](https://socketry.github.io/metrics).
14
+ Please see the [project documentation](https://socketry.github.io/metrics/) for more details.
15
+
16
+ - [Getting Started](https://socketry.github.io/metrics/guides/getting-started/index) - This guide explains how to use `metrics` for capturing run-time metrics.
17
+
18
+ - [Capture](https://socketry.github.io/metrics/guides/capture/index) - This guide explains how to use `metrics` for exporting metric definitions from your application.
19
+
20
+ - [Testing](https://socketry.github.io/metrics/guides/testing/index) - This guide explains how to write assertions in your test suite to validate `metrics` are being emitted correctly.
15
21
 
16
22
  ## Contributing
17
23
 
@@ -23,6 +29,14 @@ We welcome contributions to this project.
23
29
  4. Push to the branch (`git push origin my-new-feature`).
24
30
  5. Create new Pull Request.
25
31
 
32
+ ### Developer Certificate of Origin
33
+
34
+ In order to protect users of this project, we require all contributors to comply with the [Developer Certificate of Origin](https://developercertificate.org/). This ensures that all contributions are properly licensed and attributed.
35
+
36
+ ### Community Guidelines
37
+
38
+ This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.
39
+
26
40
  ## See Also
27
41
 
28
42
  - [metrics-backend-datadog](https://github.com/socketry/metrics-backend-datadog) — A Metrics backend for Datadog.
data.tar.gz.sig CHANGED
Binary file
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: metrics
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.8.0
4
+ version: 0.9.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Samuel Williams
@@ -37,64 +37,8 @@ cert_chain:
37
37
  Q2K9NVun/S785AP05vKkXZEFYxqG6EW012U4oLcFl5MySFajYXRYbuUpH6AY+HP8
38
38
  voD0MPg1DssDLKwXyt1eKD/+Fq0bFWhwVM/1XiAXL7lyYUyOq24KHgQ2Csg=
39
39
  -----END CERTIFICATE-----
40
- date: 2023-06-25 00:00:00.000000000 Z
41
- dependencies:
42
- - !ruby/object:Gem::Dependency
43
- name: bake-test
44
- requirement: !ruby/object:Gem::Requirement
45
- requirements:
46
- - - "~>"
47
- - !ruby/object:Gem::Version
48
- version: '0.2'
49
- type: :development
50
- prerelease: false
51
- version_requirements: !ruby/object:Gem::Requirement
52
- requirements:
53
- - - "~>"
54
- - !ruby/object:Gem::Version
55
- version: '0.2'
56
- - !ruby/object:Gem::Dependency
57
- name: bake-test-external
58
- requirement: !ruby/object:Gem::Requirement
59
- requirements:
60
- - - "~>"
61
- - !ruby/object:Gem::Version
62
- version: '0.2'
63
- type: :development
64
- prerelease: false
65
- version_requirements: !ruby/object:Gem::Requirement
66
- requirements:
67
- - - "~>"
68
- - !ruby/object:Gem::Version
69
- version: '0.2'
70
- - !ruby/object:Gem::Dependency
71
- name: covered
72
- requirement: !ruby/object:Gem::Requirement
73
- requirements:
74
- - - "~>"
75
- - !ruby/object:Gem::Version
76
- version: '0.16'
77
- type: :development
78
- prerelease: false
79
- version_requirements: !ruby/object:Gem::Requirement
80
- requirements:
81
- - - "~>"
82
- - !ruby/object:Gem::Version
83
- version: '0.16'
84
- - !ruby/object:Gem::Dependency
85
- name: sus
86
- requirement: !ruby/object:Gem::Requirement
87
- requirements:
88
- - - "~>"
89
- - !ruby/object:Gem::Version
90
- version: '0.13'
91
- type: :development
92
- prerelease: false
93
- version_requirements: !ruby/object:Gem::Requirement
94
- requirements:
95
- - - "~>"
96
- - !ruby/object:Gem::Version
97
- version: '0.13'
40
+ date: 2024-08-25 00:00:00.000000000 Z
41
+ dependencies: []
98
42
  description:
99
43
  email:
100
44
  executables: []
@@ -102,7 +46,6 @@ extensions: []
102
46
  extra_rdoc_files: []
103
47
  files:
104
48
  - bake/metrics/capture.rb
105
- - conduct.md
106
49
  - lib/metrics.rb
107
50
  - lib/metrics/backend.rb
108
51
  - lib/metrics/backend/capture.rb
@@ -117,7 +60,9 @@ files:
117
60
  homepage: https://github.com/socketry/metrics
118
61
  licenses:
119
62
  - MIT
120
- metadata: {}
63
+ metadata:
64
+ documentation_uri: https://socketry.github.io/metrics/
65
+ source_code_uri: https://github.com/socketry/metrics.git
121
66
  post_install_message:
122
67
  rdoc_options: []
123
68
  require_paths:
@@ -126,14 +71,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
126
71
  requirements:
127
72
  - - ">="
128
73
  - !ruby/object:Gem::Version
129
- version: '0'
74
+ version: '3.1'
130
75
  required_rubygems_version: !ruby/object:Gem::Requirement
131
76
  requirements:
132
77
  - - ">="
133
78
  - !ruby/object:Gem::Version
134
79
  version: '0'
135
80
  requirements: []
136
- rubygems_version: 3.4.10
81
+ rubygems_version: 3.5.11
137
82
  signing_key:
138
83
  specification_version: 4
139
84
  summary: Application metrics and instrumentation.
metadata.gz.sig CHANGED
Binary file
data/conduct.md DELETED
@@ -1,133 +0,0 @@
1
-
2
- # Contributor Covenant Code of Conduct
3
-
4
- ## Our Pledge
5
-
6
- We as members, contributors, and leaders pledge to make participation in our
7
- community a harassment-free experience for everyone, regardless of age, body
8
- size, visible or invisible disability, ethnicity, sex characteristics, gender
9
- identity and expression, level of experience, education, socio-economic status,
10
- nationality, personal appearance, race, caste, color, religion, or sexual
11
- identity and orientation.
12
-
13
- We pledge to act and interact in ways that contribute to an open, welcoming,
14
- diverse, inclusive, and healthy community.
15
-
16
- ## Our Standards
17
-
18
- Examples of behavior that contributes to a positive environment for our
19
- community include:
20
-
21
- * Demonstrating empathy and kindness toward other people
22
- * Being respectful of differing opinions, viewpoints, and experiences
23
- * Giving and gracefully accepting constructive feedback
24
- * Accepting responsibility and apologizing to those affected by our mistakes,
25
- and learning from the experience
26
- * Focusing on what is best not just for us as individuals, but for the overall
27
- community
28
-
29
- Examples of unacceptable behavior include:
30
-
31
- * The use of sexualized language or imagery, and sexual attention or advances of
32
- any kind
33
- * Trolling, insulting or derogatory comments, and personal or political attacks
34
- * Public or private harassment
35
- * Publishing others' private information, such as a physical or email address,
36
- without their explicit permission
37
- * Other conduct which could reasonably be considered inappropriate in a
38
- professional setting
39
-
40
- ## Enforcement Responsibilities
41
-
42
- Community leaders are responsible for clarifying and enforcing our standards of
43
- acceptable behavior and will take appropriate and fair corrective action in
44
- response to any behavior that they deem inappropriate, threatening, offensive,
45
- or harmful.
46
-
47
- Community leaders have the right and responsibility to remove, edit, or reject
48
- comments, commits, code, wiki edits, issues, and other contributions that are
49
- not aligned to this Code of Conduct, and will communicate reasons for moderation
50
- decisions when appropriate.
51
-
52
- ## Scope
53
-
54
- This Code of Conduct applies within all community spaces, and also applies when
55
- an individual is officially representing the community in public spaces.
56
- Examples of representing our community include using an official e-mail address,
57
- posting via an official social media account, or acting as an appointed
58
- representative at an online or offline event.
59
-
60
- ## Enforcement
61
-
62
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
63
- reported to the community leaders responsible for enforcement at
64
- [INSERT CONTACT METHOD].
65
- All complaints will be reviewed and investigated promptly and fairly.
66
-
67
- All community leaders are obligated to respect the privacy and security of the
68
- reporter of any incident.
69
-
70
- ## Enforcement Guidelines
71
-
72
- Community leaders will follow these Community Impact Guidelines in determining
73
- the consequences for any action they deem in violation of this Code of Conduct:
74
-
75
- ### 1. Correction
76
-
77
- **Community Impact**: Use of inappropriate language or other behavior deemed
78
- unprofessional or unwelcome in the community.
79
-
80
- **Consequence**: A private, written warning from community leaders, providing
81
- clarity around the nature of the violation and an explanation of why the
82
- behavior was inappropriate. A public apology may be requested.
83
-
84
- ### 2. Warning
85
-
86
- **Community Impact**: A violation through a single incident or series of
87
- actions.
88
-
89
- **Consequence**: A warning with consequences for continued behavior. No
90
- interaction with the people involved, including unsolicited interaction with
91
- those enforcing the Code of Conduct, for a specified period of time. This
92
- includes avoiding interactions in community spaces as well as external channels
93
- like social media. Violating these terms may lead to a temporary or permanent
94
- ban.
95
-
96
- ### 3. Temporary Ban
97
-
98
- **Community Impact**: A serious violation of community standards, including
99
- sustained inappropriate behavior.
100
-
101
- **Consequence**: A temporary ban from any sort of interaction or public
102
- communication with the community for a specified period of time. No public or
103
- private interaction with the people involved, including unsolicited interaction
104
- with those enforcing the Code of Conduct, is allowed during this period.
105
- Violating these terms may lead to a permanent ban.
106
-
107
- ### 4. Permanent Ban
108
-
109
- **Community Impact**: Demonstrating a pattern of violation of community
110
- standards, including sustained inappropriate behavior, harassment of an
111
- individual, or aggression toward or disparagement of classes of individuals.
112
-
113
- **Consequence**: A permanent ban from any sort of public interaction within the
114
- community.
115
-
116
- ## Attribution
117
-
118
- This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119
- version 2.1, available at
120
- [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121
-
122
- Community Impact Guidelines were inspired by
123
- [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124
-
125
- For answers to common questions about this code of conduct, see the FAQ at
126
- [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127
- [https://www.contributor-covenant.org/translations][translations].
128
-
129
- [homepage]: https://www.contributor-covenant.org
130
- [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131
- [Mozilla CoC]: https://github.com/mozilla/diversity
132
- [FAQ]: https://www.contributor-covenant.org/faq
133
- [translations]: https://www.contributor-covenant.org/translations