Skip to content
This repository has been archived by the owner on Dec 19, 2022. It is now read-only.

v1.0.0b1
Compare
Choose a tag to compare
@owais owais released this 07 May 18:37
· 47 commits to master since this release
v1.0.0b1
ddfea30
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Breaking Changes

  • Use SignalFx semantic conventions to represent errors in spans as attributes.

Errors will now be recorded in spans as attributes. The following
attributes will be used to represent errors:

  • error: A boolean field set to true in case an operation resulted in an error.
  • sfx.error.kind: The short name for type or “kind” of an error (only for event="error" logs). E.g., "Exception", "OSError".
  • sfx.error.object: The type or “kind” of an error e.g., "subprocess.CalledProcessError".
  • sfx.error.stack: A stack trace in platform-conventional format; may or may not pertain to an error. E.g., "File "example.py", line 7, in <module>\ncaller()\nFile "example.py", line 5, in caller\ncallee()\nFile "example.py", line 2, in callee\nraise Exception("Yikes")\n"
  • sfx.error.message: A concise, human-readable, one-line message explaining the error . E.g., "Could not connect to backend", "Cache invalidation succeeded"
Assets 2
Loading