[CoE Starter Kit - HOWTO] Maintain custom connector methodology to gather audit logs after deprecation

[Jenefer-Monroe]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

If you are unable to use the new Http methodology to collect audit logs and instead need to maintain the old custom connector methodology, you will need to preserve a copy of the custom connector locally in your tenant as it will no longer be released with the Core components.
This write up is intended to walk you through how to do this.

Note Env Var values

Go to the Admin Command Center and get the current values for all these env vars
If they are marked as customized, store them in a notepad as you will make sure to re-enter them later

Delete old solution

Delete the Center of Excellence - Audit Logs solution from the environment. Don't worry, the data is stored in a table in Core and so you wont be losing data by deleting it.

Import the new Custom Connector

Import this solution into your CoE Environment. It contains only a copy of the custom connector.
NewAuditLogCC_1_0_0_1.zip

Setup new Custom Connector

Update the security information for the new custom connector, just as you used to for the old one.

Create connection to new Custom Connector

Create a connection, if it does not work in this UX sometimes you have to refresh the page or go to the connections page itself and try there.

Import the rest of the new Audit Logs by CC Solution

NewAuditLogSolution_1_0_0_3.zip

Validate Env vars

Go to the Default Solution and validate or update the values in your env vars from above

Turn on the flows

Back in the New Audit Log Solution, turn on New | [Child] Admin | Sync Logs
Next turn on New | Admin | Sync Audit Logs

Validate the run

New | Admin | Sync Audit Logs flow should have run when you turned it on, but if not, please run. It should now run and pass, and you are now safe from us removing the CC later

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.11

What app or flow are you having the issue with?

audit logs

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[bhupendra14]

**### Validate the run **

** New | Admin | Sync Audit Logs flow should have run when you turned it on, but if not, please run. It should now run and pass, and you are now safe from us removing the CC later.**

Can someone help me to understand which on to remove, as mentioned in above line ( CC ??? ) ??

Thanks in advance.

[Jenefer-Monroe]

That was referencing something we would remove not you. The steps above have this step where you delete the old audit logs solution. If you share a screenshot of what you are struggling to decide if you should delete or not I can let you know.

[bhupendra14]

That was referencing something we would remove not you. The steps above have this step where you delete the old audit logs solution. If you share a screenshot of what you are struggling to decide if you should delete or not I can let you know.

okay got it now. Thanks for the response.

[JanetK12]

Hello @Jenefer-Monroe !
Could we ask the question:
For now we are unable to use the new Http methodology to collect audit logs and instead we need to maintain the old custom connector methodology, and as we understood we will need to preserve a copy of the custom connector locally in our tenant as it will no longer be released with the Core components.
Because of that we had some questions to understand and confirm the correct sequence of upgrading the solutions. Usually we updated solutions in this sequence:

1. Core components
2. Audit Components
3. Audit Logs
4. Nurture Components

Do we need to do it that way (in this sequence) this time as well? So that the Audit Logs solution will be upgraded (as explained in this #6017 writing) only as the third solution.
Or the first thing that needs to be mandatory done is the maintenance the old custom connector methodology as you explained in this #6017 writing? And only after we can procced with the Core components, Audit Components and Nurture Components solutions upgrade?
We thought it is imported to confirm this before the actual upgrade, so that we won't ruin anything.
Thank you in advance!