View categories

Categories

Language Support
- Node.js
- Ruby
  - Working with Bundler
  - Rails Support
- Python
  - Working with Django
  - Background Jobs in Python
- Java
  - Working with Maven
  - Java Database Operations
  - Java Advanced Topics
  - Working with Spring Boot
- PHP
- Go
  - Go Dependency Management
- Scala
- Clojure

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
- Heroku Data For Redis
- Apache Kafka on Heroku
- Other Data Stores

Monitoring & Metrics
- Logging

App Performance

Add-ons
- All Add-ons

Collaboration

Security
- App Security
- Identities & Authentication
  - Single Sign-on (SSO)
- Compliance

Heroku Enterprise
- Private Spaces
  - Infrastructure Networking
- Enterprise Accounts
- Enterprise Teams
- Heroku Connect (Salesforce sync)
  - Heroku Connect Administration
  - Heroku Connect Reference
  - Heroku Connect Troubleshooting

Patterns & Best Practices

Extending Heroku
- Platform API
- App Webhooks
- Heroku Labs
- Building Add-ons
  - Add-on Development Tasks
  - Add-on APIs
  - Add-on Guidelines & Requirements
- Building CLI Plugins
- Developing Buildpacks
- Dev Center

Accounts & Billing

Troubleshooting & Support

Integrating with Salesforce

Fix Connection Issues with New Relic on Bamboo

Change effective on 12 December 2012

A fix has been deployed to our Bamboo stack when using the New Relic Addon and ActiveSupport 2.x. There have been issues with the monkey patches to the JSON code that would cause an error like the following to happen:

>> ** [NewRelic][12/11/12 14:32:12 -0800 117d4803-159e-40a5-8c9d-d0a9098f2ba2 (3)] ERROR : Error establishing connection with New Relic Service at collector.newrelic.com:80: wrong number of arguments (2 for 1)

This prevents any data from getting sent to New Relic.

JRuby 1.7.1 now Supported Updated New Relic Plugin on Bamboo