Tags – auto SW builds quality status

‘Tags’ is the best way for you to understand your version status at a glance, integrate with your deployment pipeline and get your latest builds status. Whether it’s new exceptions, higher error ratios, or new broken flows – we got you covered

Tags can be anything, they can be received automatically from your pipelines or inserted manually, they can be a new version, a new big customer, or an attribution point to that day when your dev team had sangria at lunch. 

Simply go to “Tags” on your top menu, integrate into your pipeline or manually add an event tag, and get a full status in context of your event. 

1) High level status: Number of Flow Anomalies, Alerts, and the general percentage of high severity logs since the tag time and in comparison to the corresponding time of the day before the tag.

2) Suspected errors – errors which behave above their normal since the inserted tag 

3) Top errors – Top errors since the tag (maximum appearances

4) Newly introduced logs: logs which appeared on your system for the first time after the tag/build

coralogix auto version status

Integrate with your deployment pipelines: 

1) Bitbucket
2) TFS
3) GitLab
4) Heroku Pipeline

1. Integrate Coralogix with BitBucket:

Coralogix supports integration with bitbucket web hooks, use web hooks to inform coralogix when new build is issued. 
1) Login to bit bucket using your user credentials.
2) Go to your overview page and then go to settings.
3) In settings go to webhooks.
4) Add new webhook.

a) Add title (for example: “Coralogix builds”

b) Add url: https://api.coralogix.com/api/v1/bitbucket?key=ADD_YOUR_PRIVATE_KEY&application=YOUR_APPLICATION_NAME&subsystem=YOUR_SUBSYSTEM_NAME&name=YOUR_TAG_NAME

c) Key – use your private key. – must

d) Application – your desired application name – please use identical name to correspond with your logs application name. – must

e) Subsystem – your desired system name – please use identical name to correspond with your logs subsystem name, you can add more than 1 subsystem name separated by comma. 

5) Select trigger
Select build status updated:
coralogix integration to bitbucket
6) Click save.

2. Integrate Coralogix TFS:

1) Sign in to TFS using your user credentials.
2) Select your team project.
3) Click settings.
4) Go to Service hooks.
5) Click add new service hooks.
6) Select “Web Hooks”
7) Select “Build Completed” as the trigger.
8) Select Build Status “Succeeded”  and click Next.
a) You may choose any filter as you desire.
9) Add url: https://api.coralogix.com/api/v1/bitbucket?key=ADD_YOUR_PRIVATE_KEY&application=YOUR_APPLICATION_NAME&subsystem=YOUR_SUBSYSTEM_NAME&name=YOUR_TAG_NAME

a) Key – use your private key. – must

b) Application – your desired application name – please use identical name to correspond with your logs application name. – must

c) Subsystem – your desired system name – please use identical name to correspond with your logs subsystem name. you can add more than 1 subsystem name separated by comma. 

coralogix integration to TFS
10) Click finish 

3. Integrate Coralogix Git lab:

1) Login to GitLab using your Credentials:.
2) Go to your project page.
3) Go to Settings -> Integrations
4)Add url: https://api.coralogix.com/api/v1/bitbucket?key=ADD_YOUR_PRIVATE_KEY&application=YOUR_APPLICATION_NAME&subsystem=YOUR_SUBSYSTEM_NAME&name=YOUR_TAG_NAME

a) Key – use your private key. – must

b) Application – your desired application name – please use identical name to correspond with your logs application name. – must

c) Subsystem – your desired system name – please use identical name to correspond with your logs subsystem name. you can add more than 1 subsystem name separated by comma. 

5) Select PipeLine events.
coralogix integration to Gitlab
6) Click Save.

4. Integrate Coralogix Heroku Pipelines:

Simply provision the Coralogix add-on and in case you use Heroku pipelines, Coralogix will integrate into it automatically and you will start seeing your Heroku builds on the Coralogix log timelines and in the Tags display.

WordPress Lightbox