v1.9.0

fix/sentry: middlewares and span creation method (#54)

Since discussions we had, I suggest the following change:

- Merge ginsentry into sentryx (because of possible confusion with
  the legacy sentrygin package)
- Rename Middleware to GinMiddleware (because of the package change)
- Remove Recover since now it's embeded in the middleware
- Catch panic in GinMiddleware, send it to Sentry and repanic.
- Prefix URL params with `params`
- StartSpan ensures the context used is not `gin.Context`.
- Prefix params transaction tags with `param.`

v1.8.0

fix(ginsentry): put params in tags instead of span names (#53)

This PR allow grouping of Sentry span by the request handler, and puts the URL params as tags.

Fixes (partly) https://github.com/EmerisHQ/demeris-backend/issues/760. Will need to upgrade api-server to use this new utils version.

v1.7.0

remove gaia dependency (#52)

Do we ever use `store.Cdc` anywhere?

Removing `gaia.MakeCodecs` will allow us to use newer versions of the cosmos sdk wherever utils are imported.

v1.6.0

feat: add sentryx.StartSpan method (#50)

This is a handy method that ensures the context passed to StartSpan can
be overrided with span.Context. Using span.Context is required to make
new span children of the first span.

v1.5.0

feat: add ginsentry package (#49)

This PR adds a utility package to use Sentry SDK from a gin server. Sentry already provides a gin package but it doesn't work for monitoring API performances, only errors (panics).

v1.4.0

feat: add request params to gin logger (#47)

This PR enriches the logger we already use for gin servers, with fields extracted from request's params (both in the route like /chain/:chain_name that in query params like ?key=42).

I have seen in api-server that a lot of params are manually added each time, so my goal is to clean up the code and automatically add what we can without copy paste 😁

v1.3.0

Rename module name from github.com/allinbits/emeris-utils to github.com/emerishq/emeris-utils

v1.2.0

What's Changed

• split k8s.Client initialization from k8s.Config @Pitasi in #38

Full Changelog: v1.1.2...v1.2.0

Breaking changes

Update your code as following:

client, _ = NewInCluster()

becomes

cfg, _ = InClusterConfig()
client, _ = NewClient(cfg)

and

client, _ = New()

becomes

cfg, _ = KubectlConfig()
client, _ = NewClient(cfg)

v1.1.2

What's Changed

• add function to add Correlation IDs to logger by @Pitasi in #37

Full Changelog: v1.1.1...v1.1.2

v1.1.1

What's Changed

• Fix LogRequest Middleware by @SpideyPool192 in #35

Full Changelog: v1.0.1...v1.1.1