youngmon/atlassian-qna huggingface dataset:
Trying to integrate Opsgenie with AppDynamics, but we need to route issues to different teams
Asked by Andrew Feland:

Hi, I'm managing a SAAS operations team in a company that grew through acquisition. We are trying to consolidate our tools, and historically we had one monitoring tool for one SAAS application and a different one for a second SAAS application. Each had a separate integration into Opsgenie, so it was pretty simple to route issues to the appropriate ops team.

Now we're in the process of rolling out AppDynamics, and the integration seems fairly limited--it only wants to send all issues to one on-call schedule regardless of origin.

I know we could probably solve this using email integration instead of the API integration, but that seems overly complex, and I feel like I must be missing something. I'm relatively new to both tools, so any advice would be appreciated.

Thanks in advance!


Answers:
author: Arumugam M
body: Hey Andrew,

Thank you for your question. This is Arumugam from Atlassian support, happy to help.

I understand that you would like to route alerts to different teams from a single integration.

You should be able to achieve this by creating a global integration on Opsgenie (i.e, creating an integration by going to Settings -\> Integration and not associating it with any teams)

Once the integration is created, you can go to Advanced Integration settings and can filter the alerts based on the data that is posted to us and can add responders on the fly.

Here is a sample screenshot for your reference:

![appdynamics.png](https://community.atlassian.com/t5/image/serverpage/image-id/242467iAA5995B9084862D5/image-size/large?v=v2&px=999 "appdynamics.png")

You can learn more about advanced integration in the link below:

<https://support.atlassian.com/opsgenie/docs/use-advanced-integration-settings/>

Please give it a try and let us know if you have any follow-up questions.

Thanks,

Arumugam


Tags: cloud
Modification Rules Around Closed Incidents
Asked by Erica Dohring:

I'm a bit confused by some fields are modifiable after an incident is closed and some aren't. For example, you can modify the P level or incident time, you can write a postmortem, but you can't remove responders or reopen the incident.

It's my understanding you must close an incident to prevent further alerts that come in from attaching to it. If the incident is simply resolved, folks won't get paged for new alerts.

Is it configureable to ...

- Reopen closed incidents?

- Modify the responders after the fact?


Answers:
author: Mona Singh
body: Hello Erica,

This is Mona and I'm here to help :)

As you rightly pointed out that you can modify some of the incident fields when it's closed like updating the Priority, Impacted Date, Add Entry under Timeline \& Create Postmortem report. However, once the incident is closed, unfortunately, you won't be able to reopen the incident as per the current design.

This is because the Closed state is considered conclusive, indicating that all necessary actions have been taken. Therefore, once closed, an incident's only available action is to delete. Also, Recipients will be notified when an incident is closed.  
For more details, you can refer to [this](https://support.atlassian.com/opsgenie/docs/close-or-delete-an-incident/) doc.

That being said, we would like to inform you that we already have a Feature Request raised to our concerned teams for this use case which is still under review. Please feel free to add yourself as a watcher and vote on this ticket to get the latest updates on it.

Here's the ticket link for your reference:  
<https://jira.atlassian.com/browse/OPSGENIE-262>

Hope this helps. Please let us know if you have any follow-up questions.

Thanks,  
Mona Singh


Tags: cloud
Can a bamboo agent get started already dedicated?
Asked by Jonathan Ghellere:

Hello Community!

Can we start a new fresh agent already dedicated to a plan/job/project?

Sometimes we hit a limit between the number of JOBs vs. Agents. We want to bring up an agent already dedicated to a Plan or a specific Job, because this one plan or job need to be processed first. There's any config on the agent side that forces the agent to register to Bamboo server already dedicated?

I know I could change my jobs to be "requirements" driven, but ignore that please.

ps. I wonder if there's something related to this via wrapper.conf, like we have the "disable capabilities auto detection".

Thx!


Answers:
author: Eduardo Alvarenga
body: Hello [@Jonathan Ghellere](/t5/user/viewprofilepage/user-id/4894655)

The Agent dedication is controlled by the Bamboo Server and cannot be defined at the Agent level. No settings are available on the agent that would control how it is dedicated on startup.

Dedicating an Agent is not an Agent setting, but a Project/Plan/Job setting, so the Agents are not modified at all.

We have an FR <https://jira.atlassian.com/browse/BAM-8741> that was closed due to low engagement which suggests that Agents could start in a disabled state.

As a workaround, you can "Pause" the server queue, add the Agent, set the dedication and "Unpause" the server. That will guarantee that no Builds will be triggered on the agent during the pause duration.

To Pause/Unpause the server:  

```
curl -k -u admin:admin -H 'Accept: application/json' -X POST <bamboo_url>/rest/api/latest/server/pause?os_authType=basic
```

```
curl -k -u admin:admin -H 'Accept: application/json' -X POST <bamboo_url>/rest/api/latest/server/resume?os_authType=basic
```

You can also POST the Pause/Unpause commands through the UI:

* Bamboo Administration -\> Manage Apps -\> Pause/Unpause

Regards,

Eduardo Alvarenga  
Atlassian Support APAC
Bamboo Upgrade Path
Asked by Alok Kundu:

Hi Team,

We are reaching out to see what is the best version upgrade our environment needs to be able to mitigate the 2 x security vulnerabilites published here:

<https://confluence.atlassian.com/security/multiple-products-security-advisory-cve-2022-26136-cve-2022-26137-1141493031.html>

Our environment is on 8.0.4 version today. Server is installed on AMI with 5 other AMI agents.

Are you able to advise, please?

Thanks so much,

Alex.


Answers:
author: Alexey Chystoprudov
body: Hi [@Alok Kundu](/t5/user/viewprofilepage/user-id/4993253) , it's always better to upgrade to latest version which is 8.2.5 now. See <https://confluence.atlassian.com/bamboo/bamboo-8-2-release-notes-1115684503.html>

If for some reason it's not possible, then use the latest 8.0.x which is 8.0.10, see <https://confluence.atlassian.com/bamboo/bamboo-8-0-release-notes-1077903836.html>

Upgrade documentation is at <https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html>

If you decide to upgrade to 8.2.x, then pay attention to <https://confluence.atlassian.com/bamboo/version-specific-upgrade-notes-992678288.html>

comments: author: Alok Kundu
body: Thank you, Alexey for the links. I have bookmarked it and will go from here. I have additionally found that somewhere towards the center of this link (see below), there is a picture that additionally gives me a clearance on from what version I can safely upgrade to, and looks like mine is very much one of the supported versions.

<https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html>

Awesome!

Thanks for the quick help there :-)


Tags: aws

bamboo-administration

security

upgrade
Can bamboo agents be used with two URL's ?
Asked by saroj kumar singh:

We currently have multiple bamboo servers, they have there own bamboo remote agents, so i want to know is it possible to use same bamboo agents in multiple bamboo server, that would help us lower our number of bamboo agents.


Answers:
author: Eduardo Alvarenga
body: I guess this one is a duplicate of [Can bamboo agents be used with two URL's](https://community.atlassian.com/t5/Bamboo-questions/Can-bamboo-agents-be-used-with-two-URL-s/qaq-p/2086808?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic#U2087220)
Can bamboo agents be used with two URL's
Asked by saroj kumar singh:

We currently have multiple bamboo servers, they have there own bamboo remote agents, so i want to know is it possible to use same bamboo agents in multiple bamboo server, that would help us lower our number of bamboo agents.


Answers:
author: Eduardo Alvarenga
body: Hello [@saroj kumar singh](/t5/user/viewprofilepage/user-id/4992453)

Welcome to **Atlassian Community**!

Each Agent needs to be linked to a specific Bamboo Server. You can have many Agents running on the same server as long as the Bamboo Agent Home location is different. Make sure to use the following property:

```
-Dbamboo.home=/different/location
```

When installing the second agent to indicate an alternative bamboo agent home.

\* [Bamboo remote agent installation guide](https://confluence.atlassian.com/bamboo/bamboo-remote-agent-installation-guide-289276832.html)

Regards,

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: saroj kumar singh
body: So would it be possible for different plan on different bamboo url to run on the same bamboo agent simultaneously ?
Bamboo Remote Agent fails to start
Asked by Rakesh Yadav:

I approved the remote agent from the bamboo interface but the remote agent got stuck at Registering Agent on the server step.

![2022-07-22_18-12-37.png](https://community.atlassian.com/t5/image/serverpage/image-id/207460iA909A6DF5FEE521F/image-size/large?v=v2&px=999 "2022-07-22_18-12-37.png")


Answers:
author: Eduardo Alvarenga
body: Hello [@Rakesh Yadav](/t5/user/viewprofilepage/user-id/2790890)

Other than the HTTP/HTTPS port, the Remote Agent needs access to the JMS port running on Bamboo.

Bamboo listens on port TCP/54663 and your Remote Agent needs to connect to that port.

More on troubleshooting agents:

* [Troubleshooting Remote Agents](https://confluence.atlassian.com/bamkb/troubleshooting-remote-agents-216957427.html#TroubleshootingRemoteAgents-JMSConnection)

Regards,

Eduardo Alvarenga  
Atlassian Support APAC
Build warnings parser using variable in configuration
Asked by IG:

"Variables can be used to make values available when building plans in Bamboo."

I created a new variable called "warning.num" and tried to use this in the Build parser configuration in the field: Fail build threshold.

However, I've got: "Fail build threshold must be a number."

Is it possible to use a variable in that task field?

Thanks


Answers:
author: jvelapol
body: I'm assuming that you're using

```
$bamboo.warning.num
```

in the entry, and not just

```
warning.num
```

?

comments: author: IG
body: Under default plan configuration -\> variables I've added:

trunk.warnings.num with value 2

Then in build warnings parser I set the threshold to:

${trunk.warnings.num}

or

${bamboo.trunk.warnings.num}

or

$bamboo.trunk.warnings.num

All the time I get: *Fail build threshold must be a number.*


author: jvelapol
body: Maybe that field can't bet set as a variable? It's also possible that the value is being parsed as the literal string "2", in which case that won't work either. Hrm. I've never used the Build Warnings Task, though.

I'd recommend opening a support ticket with Atlassian, then.


Tags: build
How to get agent information of a build by using rest api?
Asked by Golla Sai Venkatesh:

I want to know on which agent a build was run using bamboo REST API

I tried with agent assignment API, but it will give the project, plan or job it is assigned to. But I want which agent from set of capability matching agents ran the build?


Answers:
author: Nicolas Mertens
body: it should work via [https://developer.atlassian.com/server/bamboo/rest/api-group-api/#api-api-latest-result-projectkey-buildkey-buildnumber-get.](https://developer.atlassian.com/server/bamboo/rest/api-group-api/#api-api-latest-result-projectkey-buildkey-buildnumber-get)

buildSummary-Response should include **buildAgentId**

But exactly buildAgentId is missing in response (tested with 8.1.6 build 80114)
org.hibernate.engine.jdbc.spi.SqlExceptionHelper: IO Error: The Network Adapter could not establish
Asked by Surya Chowdary:

build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,635 INFO \[main\] com.bizrule.BusinessRules: validateMailingAddressEffectiveDates method : OrchId = 0; TimeTaken : 0(ms)  
build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,653 INFO \[main\] com.bizrule.BusinessRules: validateMailingAddressEffectiveDates method : OrchId = 0; TimeTaken : 0(ms)  
build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,672 INFO \[main\] com.bizrule.BusinessRules: handleInputRequestForRemitanceAddressCheck method : OrchId = 0; TimeTaken : 0(ms)  
build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,690 INFO \[main\] com.bizrule.BusinessRules: setAcceptingPatient method : OrchId = 0; TimeTaken : 0(ms)  
build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,710 INFO \[main\] com..bizrule.BusinessRules: setAcceptingPatient method : OrchId = 0; TimeTaken : 1(ms)  
build 19-Jul-2022 09:00:22 2022-07-19 09:00:22,729 INFO \[main\] com.bizrule.BusinessRules: setAcceptingPatient method : OrchId = 0; TimeTaken : 1(ms)  
build 19-Jul-2022 09:01:22 2022-07-19 09:01:22,770 WARN \[main\] org.hibernate.engine.jdbc.spi.SqlExceptionHelper: SQL Error: 17002, SQLState: 08006  
build 19-Jul-2022 09:01:22 2022-07-19 09:01:22,771 ERROR \[main\] org.hibernate.engine.jdbc.spi.SqlExceptionHelper: IO Error: The Network Adapter could not establish the connection  
build 19-Jul-2022 09:01:22 \[ERROR\] Tests run: 46, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 554.529 s \<\<\< FAILURE! - in com.bizrule.BusinessRulesTest  
build 19-Jul-2022 09:01:22 \[ERROR\] TestvalidateAtypicalRegistrationForARScenario2 Time elapsed: 60.586 s \<\<\< ERROR!  
build 19-Jul-2022 09:01:22 org.springframework.dao.DataAccessResourceFailureException: Unable to acquire JDBC Connection; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection


Answers:
author: Mahesh Shinde
body: Hi [@Surya Chowdary](/t5/user/viewprofilepage/user-id/4986599) :

Please, check with network administrator team to validate connection between server and database.

comments: author: Surya Chowdary
body: [@Mahesh Shinde](/t5/user/viewprofilepage/user-id/2230848) Thank you. The issue is resolved.

it was a firewall connection issue between the Bamboo agent and DB.
Error while trying to initialise Bamboo Container. Mission critical plugins did not start: com.atlas
Asked by venkat prasad chary:

Error while trying to initialize![Screenshot 2022-07-19 165745.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/206719iF55D61C50A994AC1/image-size/large?v=v2&px=999 "Screenshot 2022-07-19 165745.jpg") Bamboo Container. Mission critical plugins did not start: com.atlassian.bamboo.plugins.stash.atlassian-bamboo-plugin-stash:bbserver


Answers:
author: venkat prasad chary
body: i have not update any java path in os level


author: Mahesh Shinde
body: Hi [@venkat prasad chary](/t5/user/viewprofilepage/user-id/4989730) :

It seems, might be issue with JAVA process. Have you made any changes before starting the application like plugin updates, java updates or patching at OS level?

I would like to get some application present in

* **`<bamboo-home>/logs/atlassian-bamboo.log`**

`Regards,`

`Mahesh Shinde`

comments: author: venkat prasad chary
body: ![Screenshot 2022-07-19 213236.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/206772i8A05466B97A519B2/image-size/large?v=v2&px=999 "Screenshot 2022-07-19 213236.jpg")


author: Mahesh Shinde
body: Hi [@venkat prasad chary](/t5/user/viewprofilepage/user-id/4989730) :

I don't see those error logs in the screenshot, can you please check the log files once again, it should be there.

Regards,

Mahesh Shinde
permission issues after the upgrade
Asked by tabrez ahmad:

Users are not able to clone the deployment projects after the upgrade of Bamboo 7.0.2 to 8.2.3


Answers:
author: jvelapol
body: I seem to recall that some permissions updated when we migrated to 8.0.x (from 7.x). Go into the Deployment project permissions, and make sure that your users have "Edit" permissions on the deployment project itself. See <https://confluence.atlassian.com/bamboo0802/creating-and-configuring-a-deployment-project-1103433372.html?permissionViolation=true#Creatingandconfiguringadeploymentproject-Configuringdeploymentprojectpermissions> for more information.
Bamboo Plan triggers cron expression
Asked by Nat Tsai:

Can any way update the bamboo plan triggers schedule without Bamboo UI? for example restful API

We hope through automation action change Bamboo Plan triggers cron expression, but Bamboo API doesn't have any about triggers configs.

Bamboo API: <https://docs.atlassian.com/atlassian-bamboo/REST/8.2.4/>


Answers:
author: Craig Castle-Mead
body: Hey [@Nat Tsai](/t5/user/viewprofilepage/user-id/4527527)

Unfortunately as you've found, the Bamboo REST API is far from having parity with the UI itself. You're unable to setup/configure linked repositories and much more via REST API.

One non-UI approach that may help you out is to configure your plan using Bamboo Specs - this can be done via Java or YAML. The YAML reference for specifying triggers using a cron schedule can be found at <https://docs.atlassian.com/bamboo-specs-docs/7.0.1/specs.html?yaml#polling-the-repository-for-changes>

CCM

comments: author: jvelapol
body: Yeah - the YAML configurations for 8.2.x are "better" than they were for 7.0.1. The link for the 8.2.x version of the YAML specs are <https://docs.atlassian.com/bamboo-specs-docs/8.2.4/specs.html?yaml#polling-the-repository-for-changes> but they look to be the same for polling based checking in Bamboo 7.0.1 also.
How to link multiple repositories to a single Bamboo plan?
Asked by Chong Jing Hong:

I have a Bamboo plan, I want to link multiple Bitbucket repositories to it such that the plan runs whenever code is pushed to whichever repository. How do I achieve this? Thank you


Answers:
author: jvelapol
body: I've found that once you manage a Build Plan via Specs, you can no longer interact with it via the UI (other than to "see" what's there - you can no longer make any edits/changes).

What you're probably interested in may be covered in the "[Repositories](https://docs.atlassian.com/bamboo-specs-docs/8.2.4/specs.html?yaml#multiple-repositories)" section of the Spec docs. Note that I've not gotten this to work unless the extra repos you want to use in the Plan are also Linked repositories, too. We pull git repos from a variety of sources (on-prem bitbucket server, Github, GitLab, etc) and they're all "Linked repositories". We use the YAML based specs, and we have, for example:

    repositories:  - linked-repo-name-1  - linked-repo-name-2

Which works fine for one of our Build Plans. Note that the name of the linked repos (from the Gear -\> Lined repositories menu) in the yaml is the same as the "name" listed in the "Linked repositories" location.

EDIT: One gotcha that you have to be aware of is that inside the repo that you're adding to the plan as an extra linked repo, you'll need to make sure that you configure the "Permissions" for that linked repo to include the Specs repo, too. You can find that on the "Permissions" tab of the linked repo. There will be an error that will point you in that direction, too.


author: Eduardo Alvarenga
body: Hello [@Chong Jing Hong](/t5/user/viewprofilepage/user-id/4789367)

Depending on how your repository is configured (Bitbucket, Bitbucket Cloud, Github or plain Git), you will need to configure a repository trigger on the Plan.

The repository trigger will watch for changes to the repositories you have selected or be notified passively (for Bitbucket)

You can find more information here:

* [Triggering builds](https://confluence.atlassian.com/bamboo/triggering-builds-289276897.html)

Regards,

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Chong Jing Hong
body: Hi Eduardo,

Thanks for the reply. But how do I linked the repos to the plan? Whenever I set up a spec repository, the previous repo that was linked would be replaced by the newer repo. And the add repo button is grey-ed out as well, as such: <https://imgur.com/a/Rv6oqHx>


author: Eduardo Alvarenga
body: Hello [@Chong Jing Hong](/t5/user/viewprofilepage/user-id/4789367)

It can be a permission issue in case you are not an Administrator. It can also be the case of your Plans are using Bamboo Specs. If your plan uses Bamboo specs, you will need to use Specs to modify it.

More information here:

* [Bamboo Specs](https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html)

Eduardo Alvarenga  
Atlassian Support APAC


Tags: bitbucket
Plan could not be started JDBC exception in Hibernate data access: SQLException for SQL
Asked by Julian Jaramillo:

Hi Team,  
one of our plans stopped working recently, when we try to run manually we get this error and the plan doesn't start at all:  

Plan 'PTAUT' could not be started. org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL \[n/a\]; SQL state \[53300\]; error code \[0\]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet

in the logs we can see this:

```
JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [53300]; error code [0]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet
```

```
Caused by: org.postgresql.util.PSQLException: ERROR: remaining connection slots are reserved for non-replication superuser and rds_superuser connections
```

We have Bamboo datacentre 8.1.2 build 80109 connected to RDS

anyone knows what could be the problem here?

Thank you!


Answers:
author: Julian Jaramillo
body: we found the reason why our plans wouldn't run.

we hit a limit on the number of iterations.  
basically one of our customers configured a plan to run every 15 min, after a year this became over 26k iterations and suddenly stop working

<br />

deleting old entries from the history of the plan got it working again, however it was easier to clone it and start fresh


author: Julian Jaramillo
body: Hi [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410)   
thank you very much for the information, checking the database we are pretty sure max_connections is not the problem. we are well below  

```
SHOW max_connections; 
3466
```

we also experience this problem with only one plan in particular, all the other plans are working fine.

we suspect there is something in the cache related to this plan that is throwing this error.  
is there a way to refresh that for a particular plan?  

Cheers


author: Eduardo Alvarenga
body: Hey [@Julian Jaramillo](/t5/user/viewprofilepage/user-id/3717435)

The following message:

```
Caused by: org.postgresql.util.PSQLException: ERROR: remaining connection slots are reserved for non-replication superuser and rds_superuser connections
```

Indicates that the database has exceeded the **max_connections** parameter.

You can try extending upgrade your RDS instance or adjusting the **max_connections** on parameter groups directly on the database:

* [Working with parameter groups](max_connectionshttps://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html)

Regards,

Eduardo Alvarenga  
Atlassian Support APAC