search

elastic / integrations

Elastic Integrations
https://www.elastic.co/integrations
Other
30 stars 447 forks source link

[STAN Integration] Product EOL update #11532

Open muthu-mps opened 3 weeks ago

muthu-mps commented 3 weeks ago

Summary

The STAN integration monitors the logs and metrics for the NATS streaming server(STAN). This product has reached EOL as mentioned here. This product has been replaced by Jetstream server.

This integration can be marked as deprecated as the product is already deprecated and reached EOL last year. As the product is replaced by Jetstream, We can consider adding support for monitoring the Jetstream server.

The deprecation warning can be added to the title of the integration similar to F5 Logs integration.

muthu-mps commented 3 weeks ago

cc: @daniela-elastic

muthu-mps commented 2 weeks ago

As the product has reached EOL and replaced by Jetstream. We need to validate whether the existing integration itself is capable of processing the Jetstream metrics.

daniela-elastic commented 2 weeks ago

Are we talking about updating the STAN integration to support Jetstream server or are we talking about creating a brand new integration and deprecating the STAN integration?

muthu-mps commented 2 weeks ago

Are we talking about updating the STAN integration to support Jetstream server or are we talking about creating a brand new integration and deprecating the STAN integration?

There are two options, 1) Verify the Jetstream metrics using the current STAN integration. This is by upgrading the integration. 2) Create a brand new integration for Jetstream.

My suggestion is we can try with the option 1 and if it doesn't work then we can go for option 2. I would like to hear your thoughts.

daniela-elastic commented 2 weeks ago

Agree with the proposal. In this case we need to test the whole upgrade experience. Eg, for a customer who has already installed the legacy STAN integration, what would their experience be - can we disable collection of metrics/logs? Can we show a message somewhere in the integration (eg dashboard, collected metrics, somewhere else? ) that the user needs to upgrade to be able to get the metrics/logs for jetstream? Do we have similar integrations in the past where the underlying tech was deprecated and replaced with a new one and if so, how did we address that?

daniela-elastic commented 2 weeks ago

Additional questions:

  1. If a user has an application that relies in the legacy NATS streaming server (STAN) continues to use it and hasn't yet updated to using JetStream, would their application continue to function? Is it just a matter of using a component that is not longer maintained or it relies on a service that will cease to function which then renders the application relying on it not functioning either?
  2. Assuming the answer to the above is "the application relying on legacy STAN will continue to function", then would a user who has already installed the STAN integration (for legacy STAN) be able to continue to use the integration if they didn't do anything to upgrade?
  3. If the answer to Q2 is "the legacy STAN integration will continue to function" then is there a way to show somewhere that this is a legacy integration ?
  4. Can we estimate the effort needed to create a new integration for Jetstream-based NATS streaming server?
  5. Can we test the following experience: a user that has installed the legacy STAN integration upgrades their NATS streaming server to using jetstream. What happens to the legacy integration they've installed? Does it continue to work 100%? What's the delta - eg some legacy metrics don't exist anymore, some new jetstream-based metrics don't exist in the legacy integration, etc