Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deploy the agent bundles on Elastic CDN

See original GitHub issue

Currently we recommend users to install our package from npm and serve the JavaScript bundle from their own servers. However, providing the RUM agent via our own CDN simplifies testing and deployment for our users.

I think we should meet the following requirements:

Ability to publish the final JavaScript bundles to our CDN (this can be done through CI/CD), currently we don’t have any CDN endpoints.
We should have some sort of versioning in the URL, e.g. https://elastic.co/cdn/apm-rum@4/apm-rum.min.js for the 4th major version of the agent. It would be better if the version in the url supports semantic versioning (example) but at the moment we only require supporting the major version (because of breaking changes).
We should provide high availability, since the JS bundle might be deployed by our users in production and if the endpoint is not available it might result in disrupting their service. This also means that this CDN endpoint could potentially be hit by a huge number of requests.

Depends on: https://github.com/elastic/apm-agent-rum-js/issues/518

Issue Analytics

State:
Created 4 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

6reactions

alvarolobatocommented, Jul 1, 2020

We’ve discussed this and we are going to move forward, with a phased approach.

Initially we will host the agent on a CDN with a unique URL per patch version and infinite TTL (we will reevaluate in the future)
This URLs will be shared with a set of cloud users before making it available to a broader set.
We should make sure we can analyze the CDN logs to understand the usage, like we do with the Package manager logs.
After this, we will decide if we offer it to all the paid users or to everyone even basic on-prem users.

Not use elastic.co URL, @drewpost was concerned of our domain being identified with a tracker. cc. @graphaelli

1reaction

v1vcommented, Jun 24, 2020

@olksdr just pointed that the current implementation will show an error message when accessing http://apm-assets.elastic.co/, as long as there is no an index.html file in the root of the bucket. We can deploy a beautiful page with list of the assets (maybe generate it on deployment), what do you think?

Top Results From Across the Web

Install the Agent | APM Real User Monitoring ... - Elastic

Using Package Managers: Install the Agent as a dependency to your application. ... However, they make the RUM agent bundle size larger so...

Install the Agent | APM Real User Monitoring ... - Elastic

By default, RUM agent logs all the debug messages to the browser console. These logs are very useful in development. However, they make...

Deploy on Elastic Cloud | Fleet and Elastic Agent Guide [8.5]

In Kibana, go to Management → Fleet. On the Agents tab, look for the Elastic Cloud agent policy. This policy is managed by...

Upload custom plugins and bundles - Elastic

After uploading your files, you can select to enable them when creating a new Elasticsearch deployment. For existing deployments, you must update your ......

Quick start guide | APM User Guide [master] - Elastic

Step 1: Spin up the Elastic Stackedit · Get a free trial. · Log into Elastic Cloud. · Click Create deployment. · Select...