signalfx-lambda 0.2.1 → 0.2.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +16 -0
- data/lib/signalfx/lambda/tracing.rb +1 -0
- data/lib/signalfx/lambda/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 017f434afdb0c59000e072360b64b35f3e239fcfd7b99cdde8f875d59f693286
|
4
|
+
data.tar.gz: eb1704cf3eb290c791e28ed99df75f283c7a179efec5935b37f855dd30d4ef0c
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ca5df09ab26aad318af8f5467b3d4f3239fef14e3d0fcae4727f3dcd01f641f58ccc3ebb4d713bb8542aae9535f795d49fcefa2970ac76528f2eca172cc6b339
|
7
|
+
data.tar.gz: 8f990b7f6ed62d02ae39b43979d36a9e7a2a48bb3177abacba544b411673d873158ab38aa0612fd053d7cd3e9a21d48f417ab7d3954f386b76072740d0fa054a
|
data/README.md
CHANGED
@@ -57,6 +57,10 @@ SIGNALFX_ENDPOINT_URL=<gateway_url>
|
|
57
57
|
If the component-specific URLs below are set, they will take precedence over
|
58
58
|
`SIGNALFX_ENDPOINT_URL` for those components.
|
59
59
|
|
60
|
+
By default, the metrics and traces will be reported to the `us0` realm. If you are
|
61
|
+
not in this realm you will need to set the `SIGNALFX_TRACING_URL` and
|
62
|
+
`SIGNALFX_METRICS_URL` environment variables, as described below.
|
63
|
+
|
60
64
|
### Tracer configuration
|
61
65
|
|
62
66
|
The tracer used by the function is configured through environment variables:
|
@@ -72,6 +76,12 @@ When pointing to the Smart Gateway, an access token is not needed. When not
|
|
72
76
|
configured, the ingest URL defaults to `https://ingest.signalfx.com/v1/trace`,
|
73
77
|
which requires an access token to be configured.
|
74
78
|
|
79
|
+
The default `SIGNALFX_TRACING_URL` points to the `us0` realm. If you are not in
|
80
|
+
this realm, you will need to set the environment variable to the correct realm
|
81
|
+
ingest endpoint (https://ingest.{REALM}.signalfx.com/v1/trace). To determine what realm
|
82
|
+
you are in, check your profile page in the SignalFx web application (click the
|
83
|
+
avatar in the upper right and click My Profile).
|
84
|
+
|
75
85
|
The tracer will be persisted across invocations to the same context, reducing
|
76
86
|
the time needed for tracer initialization.
|
77
87
|
|
@@ -89,6 +99,12 @@ access token is not needed.
|
|
89
99
|
|
90
100
|
The metrics URL will default to `https://ingest.signalfx.com` when not configured.
|
91
101
|
|
102
|
+
The default `SIGNALFX_METRICS_URL` points to the `us0` realm. If you are not in
|
103
|
+
this realm, you will need to set the environment variable to the correct realm
|
104
|
+
ingest endpoint (https://ingest.{REALM}.signalfx.com). To determine what realm
|
105
|
+
you are in, check your profile page in the SignalFx web application (click the
|
106
|
+
avatar in the upper right and click My Profile).
|
107
|
+
|
92
108
|
## Trace and tags
|
93
109
|
|
94
110
|
The wrapper will generate a trace per function invocation. The parent span will
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: signalfx-lambda
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Ashwin Chandrasekar
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-
|
11
|
+
date: 2019-04-01 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: jaeger-client
|