2023.5 Blows up customizations

We’re on 2023.1.x and can’t see our logs to download them. I’m with @klincecum I think it’s coming just not until 2023.2 or some thing we need to ask to be enabled.

Product change was made in 2023.1 but it needed a configuration change on the AppServer configuration. After checking with the Cloud team, it looks like the work to enable this was not rolled out for all systems.

You can enable this via a Service Now request to change the Server logging location to your EpicorData folder and enabling the Server logging.

Kevin - have you checked your AKS environment?

Yes sir, not there either.

How is cleanup handled? Do we need to handle it when there are too many?

Cleanup / management (with the exception of Application logging for things like MRP) is automatic. There is a specification for max size of log files and number of log files to retain (I think Cloud Ops sets the production limits to something like 20 Megs and 10 files). Once the active log file hits max size, a new log file is started and the oldest log file is deleted - assuming the maximum number of log files to retain has been reached.

AKS environment - I will check on that.

1 Like

I bother y’all enough, no rush :blush:

Will this need to be requested to be enabled, or is enabled by default for all cloud customers on 2023.1 moving forward?

Was this mentioned in release notes anywhere?

Rollout for all Cloud Customers has been delayed (my bad, I thought it had been done to coincide with the feature work done in 2023.1). This is being applied as we upgrade the Cloud infrastructure but if not done for an instance, it can be requested via EpicCare.

Surprisingly, this was not included in the Release Notes but it is documented in the Server File Download section - new Admin Folder option. The option is available for all Systems - Cloud and on-prem.

2 Likes

I have it now in my AKS environment. It works as expected.

Now, time to build a dashboard. :safe_harbor:

1 Like

Oh man, this is awesome, and also totally sucks.