Explains how to monitor and manage legacy services.

In the app monitor in section Legacy services it is possible to see the status of the legacy services of the app. There you will see the following information:

  • Status: indicates if the legacy service is deployed, undeployed or in an intermediate status.
  • Last 24 hs activity: shows the number of function calls and events received in the last 24 hs.
  • Running instances: you can see how many instances are running of your legacy service.
  • Configuration details: if you click on one of the legacy service you will be able to see the configuration details.

You can perform the following operations over legacy services:

  • Deploy: if the legacy service is undeploy, you can deploy it by selecting it and clicking on the Deploy button.
  • Undeploy: if the legacy service is deployed, you can undeploy it by selecting it and clicking on the Undeploy button. Once the legacy service is deployed it will stop working (calls to this endpoint will fail and no more events will be received) and no resources will be used by the legacy service.
  • Redeploy: this basically restarts the selected legacy services, which might be needed if configuration was changed through environment variables or something looks odd in the behavior of the legacy service.

Legacy service configuration

  • Generate Token: legacy service has a token that is needed to communicate to it from the outside. You can regenerate that token from here in case it was compromised.

  • Profile: some legacy services support different memory profiles. For example, the Slack legacy services has different memory profiles based on the number of members you have in your team.

  • Multiple instances: if the legacy service allow multiple instances here you can resize it. Adding more instance for an legacy service will allow to handle more load on your integrations.

  • Hide logs content: if the legacy service works with sensitive information you can hide logs setting this flag. For example an legacy service for credit card processing in production should have this option enabled to avoid logging any sensitive information.

Back to top