Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Confusion... #294

Closed
cmdematos opened this issue Apr 13, 2020 · 7 comments
Closed

Installation Confusion... #294

cmdematos opened this issue Apr 13, 2020 · 7 comments

Comments

@cmdematos
Copy link

I have been reading the documentation. I have built and extracted the js but I don't have enough information on how to use this yet. The documentation references a beacon, some server-side resource but I dont understand whether the beacon is what is being measured or whether it is receiving posted information. There is also no documentation on how to implement the beacon on the server-side, assuming that is receiving information from boomerang, can we have a simple example of how to implement the server-side? What about integration with PIWIK/matomo or other servers that are supposed to receive this information?

The documentation omits all of this, it seems to be tribal information, like you I would know if I was grandfathered into this project by some beneficial happenstance.

Can someone please provide high level guidance beyond the HTTP javascript to be inserted and complete the picture on what happens when this information is posted...

@quintenp
Copy link

Beacon is simply a naming convention for the payload boomerang builds and sends to the server side.

The payload or Beacon contains information gathered from the browser apis and specific plugins you have enabled.(Performance / Resources / Errors / W.e)

The server side implementation is up to you, it's a JSON payload at the end of the day with a bit of encoded fields and a lightweight compression, think there is a tri for resources as well. You could easily spin up an api and process it in which ever way your needs require, stick it into elastic or your storage of choice / visualize it with tools like kibana/splunk or build your own processing and visualization it's very open ended.

@bluesmoon
Copy link
Member

Sorry, there used to be howto documents for what to do on the server-side. They should still be in git history in the gh-pages branch.

@mc-chaos
Copy link

mc-chaos commented May 15, 2020

You could use the inspectit ocelot eum Server(1) to receive the beacons and Export the to influxdb or Prometheus. There will be an opentelemetry Plugin(2), next time. You could than export Traces from your your Browser.

  1. https://inspectit.github.io/inspectit-ocelot/docs/next/enduser-monitoring/enduser-monitoring-server
  2. https://github.com/NovatecConsulting/boomerang-opentelemetry-plugin

@mc-chaos
Copy link

There is a other new and active Projekt to receive beacons.
https://github.com/basicrum/backoffice

@nicjansma
Copy link

The current tutorial at https://akamai.github.io/boomerang/tutorial-howto-read-data-from-a-beacon.html covers some of this, but it would be worthwhile to update the Backend Servers section with more recent implementations.

@nicjansma
Copy link

Here's some additional links we know of right now

There are several open-source projects that can receive and analyze Boomerang data:

Here are some articles for putting it all together:

We'll update the documentation with those soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants