[JIRA] (JENKINS-54445) Publishing data to influxDb

13 views
Skip to first unread message

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 5, 2018, 3:27:03 AM11/5/18
to jenkinsc...@googlegroups.com
Mohamed Nazeer Mohamed Ibrahim created an issue
 
Jenkins / Improvement JENKINS-54445
Publishing data to influxDb
Issue Type: Improvement Improvement
Assignee: Aleksi Simell
Components: influxdb-plugin
Created: 2018-11-05 08:26
Priority: Major Major
Reporter: Mohamed Nazeer Mohamed Ibrahim

I want to customize the tags and keys in the collected data. As of now only the project name is the tag in influxdb. But i want add some more fields as tags in influxdb.

Example

I want to filter the data build wise. So that i want to add the build number as tag in the influxdb.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 5, 2018, 3:29:01 AM11/5/18
to jenkinsc...@googlegroups.com
I want to customize the tags and keys in the collected data. As of now only the project name is the tag in influxdb. But i want add some more fields as tags in influxdb.

Example

I want to filter the data build wise. So that i want to add the build number as tag in the influxdb.

 


 

And also i could not get the pipeline data such as stage duration, failed at which stage.

 

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 3:47:02 AM11/5/18
to jenkinsc...@googlegroups.com
Aleksi Simell commented on Improvement JENKINS-54445
 
Re: Publishing data to influxDb

Custom tags were added in PR 32 (https://github.com/jenkinsci/influxdb-plugin/pull/32). Does this already address your issue? You can add build number tag to your build with adding a jenkins-env-parameter tag build_number=${BUILD_NUMBER}.

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 5, 2018, 5:28:02 AM11/5/18
to jenkinsc...@googlegroups.com

Thanks for replying. The pull request 32 will solve our one requirement. But we have one more requirement blocking our progress. Which is already created as ticket by someone else. The ticket is https://issues.jenkins-ci.org/browse/JENKINS-53360

 

We are publishing data as step configuration of InfluxDb as below 

step([$class: 'InfluxDbPublisher', customData: myDataMap, customDataMap: myCustomDataMap, customPrefix: null, target: 'Influxtarget'])

But we do not know how to configure the  jenkins-env-parameter tag build_number=${BUILD_NUMBER}. And also we could not find the UI to configure the same. 

Our Jenkins version is Jenkins ver. 2.107.3 and InfluxDb Plugin version is 1.20

 

 

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 6:22:01 AM11/5/18
to jenkinsc...@googlegroups.com

Mohamed Nazeer Mohamed Ibrahim You can add build number tag in your pipeline by adding for example

jenkinsEnvParameterTag: 'build_number=' + env.BUILD_NUMBER,

to your step.

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 6:22:01 AM11/5/18
to jenkinsc...@googlegroups.com
Aleksi Simell edited a comment on Improvement JENKINS-54445
[~mohamednazeer] You can add build number tag in your pipeline by adding for example
{noformat}
jenkinsEnvParameterTag: 'build_number=' + env.BUILD_NUMBER
,
{noformat}
to your step.

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 5, 2018, 6:50:02 AM11/5/18
to jenkinsc...@googlegroups.com

Thank you very much its working.

could you please give some update for https://issues.jenkins-ci.org/browse/JENKINS-53360 

 

Thanks in advance

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 7:07:02 AM11/5/18
to jenkinsc...@googlegroups.com

My current project has kept me busy for a very long time, so I haven't had time to do any work on any ticket for quite some time. However, now my project is coming to an end so in the near future I might have more time to work on new features for the plugin (instead of just bug fixes and pull requests).

In short: Nothing done whatsoever.

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 7:11:02 AM11/5/18
to jenkinsc...@googlegroups.com
Aleksi Simell updated Improvement JENKINS-54445
 

Tags already implemented.

Other issue continued in https://issues.jenkins-ci.org/browse/JENKINS-53360.

Change By: Aleksi Simell
Status: Open Fixed but Unreleased
Resolution: Won't Do

aleksi.simell@eficode.com (JIRA)

unread,
Nov 5, 2018, 7:11:02 AM11/5/18
to jenkinsc...@googlegroups.com
Change By: Aleksi Simell
Status: Fixed but Unreleased Closed

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 5, 2018, 7:41:01 AM11/5/18
to jenkinsc...@googlegroups.com

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 20, 2018, 5:48:01 AM11/20/18
to jenkinsc...@googlegroups.com
Mohamed Nazeer Mohamed Ibrahim reopened an issue
Change By: Mohamed Nazeer Mohamed Ibrahim
Resolution: Won't Do
Status: Closed Reopened

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 20, 2018, 5:48:02 AM11/20/18
to jenkinsc...@googlegroups.com

Sorry to reopen this issue.

The given solution is effect only for jenkins_data measurement. But the same is not reflect in other measurements which are collected by the same plugin such as "jacaco_data, suite_results, rf_results...etc"

 

Thanks in advance

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 27, 2018, 1:23:02 AM11/27/18
to jenkinsc...@googlegroups.com

We have implemented the given solution but it seems the tags are not present in the databases.

The influx version is : 1.5.4

jenkins Configuration is :

step([$class: 'InfluxDbPublisher', customData: myDataMap, customDataMap: null, customPrefix: null, target: 'Jenkins Build Status', jenkinsEnvParameterTag: 'build_number=' + env.BUILD_NUMBER])

 

When we execute the below query in influxdb it shows nothing.

SHOW TAG KEYS FROM "testcase_point"

 

 

 

aleksi.simell@eficode.com (JIRA)

unread,
Nov 27, 2018, 1:30:02 AM11/27/18
to jenkinsc...@googlegroups.com

That is because with the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement jenkins_data as documented. I will try to add those tags to all measurements once I find time.

aleksi.simell@eficode.com (JIRA)

unread,
Nov 27, 2018, 1:31:01 AM11/27/18
to jenkinsc...@googlegroups.com
Aleksi Simell edited a comment on Improvement JENKINS-54445
That is because with the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement " jenkins_data ", as documented. I will try to add those tags to all measurements once I find time.

m.mohamednazeer@gmail.com (JIRA)

unread,
Nov 27, 2018, 2:33:02 AM11/27/18
to jenkinsc...@googlegroups.com

Thanks for reply!!

If i want to add some more tag keys then what should i do?

Any specific format for this?

 

 

sudeep_pranavam@yahoo.com (JIRA)

unread,
Jan 8, 2020, 1:25:02 PM1/8/20
to jenkinsc...@googlegroups.com
_peedus commented on Improvement JENKINS-54445

> the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement "jenkins_data", as documented. I will try to add those tags to all measurements once I find time.

Is there any tentative time when this will be available?

Thanks!

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

sudeep_pranavam@yahoo.com (JIRA)

unread,
Jan 8, 2020, 1:26:02 PM1/8/20
to jenkinsc...@googlegroups.com
_peedus edited a comment on Improvement JENKINS-54445
Hi [~aleksisimell],

> the current configuration the
_* jenkinsEnvParameterTag *_ adds the tags only to the measurement " _* jenkins_data *_ ", as documented. I will try to add those tags to all measurements once I find time.


Is there any tentative time when this will be available?

Thanks!

sudeep_pranavam@yahoo.com (JIRA)

unread,
Jan 8, 2020, 1:30:02 PM1/8/20
to jenkinsc...@googlegroups.com
_peedus edited a comment on Improvement JENKINS-54445
Hi [~aleksisimell],

> the current configuration the _*jenkinsEnvParameterTag*_ adds the tags only to the measurement "_*jenkins_data*_", as documented. I will try to add those tags to all measurements once I find time.

Is there any tentative time when this will be available?
Hope the same could be also done for 
_*jenkinsEnvParameterField*_ ?
Thanks!

sudeep_pranavam@yahoo.com (JIRA)

unread,
Jan 8, 2020, 1:31:02 PM1/8/20
to jenkinsc...@googlegroups.com

aleksi.simell@eficode.com (JIRA)

unread,
Jan 9, 2020, 1:09:09 AM1/9/20
to jenkinsc...@googlegroups.com

Hi _peedus,

I had completely forgotten this one. I made a note for myself to have this in my own "backlog". I will try to make this ASAP, but might not make it for the next release (I try to make releases ~once a month or so).

Reply all
Reply to author
Forward
0 new messages