User API Key is a problem when an employee leaves

[nthornton2010]

Problem: Right now, this requires that an API Key be provided. The problem with this is that the API Key required is a key type that is linked to an individual user within a New Relic account and is not linked to the account itself. This becomes an issue when the employee associated with the user leaves and their user account is deleted because the API Key no longer returns a licenseKey value when nerdgraph is called.

We learned this the hard way after our instrumentation stopped working in all Lambdas.

Proposed Solution: Change the plugin to support Ingest - License keys. These are linked to the New Relic account and not the user. These keys are meant for data ingestion (like this).

Workaround: Create a full New Relic user that is not used by anybody that is there only for API Keys that are really linked to the account. This will make it so that the user account is never deleted. Here are the issues with this:

1. This goes against New Relic's TOS because it's technically considered a "shared" account because all company admins can access it.
2. We are charged extra on our bill. We now have to pay for another full user that is never really going to be used other than for this.
3. We must provide internal documentation to all engineers that say this.
4. There's still the chance that an engineer misses this documentation or forgets and sees this shared user costing money, making them think that deleting the account or changing it to be a Basic user will save us money. The account must be a full account for nerdgraph to return a licenseKey.

[workato-integration]

https://issues.newrelic.com/browse/NR-140836