Notebook(Alerts): Zenoss Alert export generates flux script that cannot be compiled

[karel-rehor]

Note - for this test we are temporarily using a simple HTTP echo server in EC2 before creating and testing against an actual Zenoss account.

About the bug

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

1. Setup a listener to receive Zenoss messages.
2. Go to Influxdbv2 UI (note that during this test the feature flag 'notebooksNewEndpoints' was set)
3. Add test data to a bucket
4. Create an Alert Notebook
5. Use the test data to define the query
6. In the alert section choose Zenoss
7. Add the username, password, severity, action, method and change the URL to point to the listener, if not testing against the actual Zenoss service.
8. Click "Export Alert Task"
9. Open the generated task in the tasks view
10. Click "Run Task". This schedules a run
11. After a moment open the Task List.

Expected behavior:

Expected the task to be run and a message to appear at the listener

Actual behavior:

The Last Run status is Error.
Open the Task Editor. The generated flux script cannot be compiled.

Visual Proof:

The generated flux script

About your environment

Environment info:

Testing in K8SIDPE

Last commit in project UI

commit a832ae6f4e4979fced6e44fb2cc955afa05fa3f6 (HEAD -> master, upstream/master, origin/master, origin/HEAD)
Author: asalem1 <19984220+asalem1@users.noreply.github.com>
Date:   Thu Feb 10 13:02:46 2022 -0800

Last commit in K8SIDPE

commit 68fd2e73d645a0aad1f7075a61a411b4adbe08b1 (HEAD -> master, origin/master, origin/alchemy/automatic, origin/HEAD)
Author: Hercules Mango Churchill <alchemy@influxdata.com>
Date:   Thu Feb 10 05:11:06 2022 +0000

[subirjolly]

The fix is in a PR. In order to test it, we need Zenoss test credentials. @jzahnd or @karel-rehor if you could get those then I will be able to test and finish this issue. Till then, blocking this issue.

[subirjolly]

@karel-rehor Any update on Zenoss credentials?

[karel-rehor]

@subirjolly We looked into using Zenoss community edition but the complexity of the installation would make it time consuming. When all we want to do is try one simple integration test the potential time invested in the installation makes this approach prohibitive. So we would do it only as a last resort. Ivan opened a ticket at Zenoss about creating a simple test account with them. This is currently in discussion. Hopefully we will know more during the day.