curl http://localhost:8200 should respond with JSON indicating the APM server is running otlp:
endpoint: host.docker.internal:8200
tls:
insecure: true
We want to instrument Remix apps with the Elastic APM Node.js Agent on the server and the Elastic APM Real User Monitoring JavaScript Agent on the client.
We want the server-rendered page to have the trace id and other data available to the client, so we can correlate the traces between server and client. Elastic's distributed tracing docs explain this.
I've been able to make this work with Remix on Express, but it's super hacky, so this gist shows what I'm doing so hopefully somebody can point me to a better way to do this.
These are instructions on how to use Elastic Observability with Remix.
The easiest way to get a working cluster is with Elastic Cloud. Create a new deployment. Once it's ready you'll want to copy the APM endpoint URL:
In your Remix app, install the Elastic RUM JavaScript agent:
npm install @elastic/apm-rum --save
I hereby claim:
To claim this, I am signing this object:
| # List of installed extensions. These are not the friendly names on the marketplace, but you could figure it out, | |
| # and I think you can run `code --install-extension Orta.vsocde-jest` | |
| nsmith@nsmith ~/s/s/m/meatballs-ui> code --list-extensions (master=) | |
| DSKWRK.vscode-generate-getter-setter | |
| EditorConfig.EditorConfig | |
| Orta.vscode-jest | |
| Pendrica.Chef | |
| PeterJausovec.vscode-docker | |
| TeddyDD.fish | |
| Tyriar.sort-lines |
| import React, { Component } from 'react' | |
| import cacheComponent from './cacheComponent' | |
| class AComponent extends Component { | |
| onClick = () => { | |
| this.props.set({ clicked: true }); | |
| } | |
| render() { | |
| return <div>Have I been clicked? {this.props.cache.clicked ? "yes :)" : "no :("} <button onClick={this.onClick}>click me</button></div>; |
A list, in no particular order, of useful things I've read or watched about Go
| gcc: WARN | |
| gcc: WARN The following runtime dependencies have more than one version | |
| gcc: WARN release in the full dependency chain: | |
| gcc: WARN | |
| gcc: WARN * core/gmp ( core/gmp/6.1.2/20170526062114 core/gmp/6.1.0/20170513202112 ) | |
| gcc: WARN | |
| gcc: WARN The current situation usually arises when a Plan has a direct | |
| gcc: WARN dependency on one version of a package (`acme/A/7.0/20160101200001`) | |
| gcc: WARN and has a direct dependency on another package which itself depends | |
| gcc: WARN on another version of the same package (`acme/A/2.0/20151201060001`). |
| [1;36m: [1;37mLoading /src/opam/plan.sh[0m | |
| [1;36mopam: [1;37mPlan loaded[0m | |
| [1;36mopam: [1;37mValidating plan metadata[0m | |
| [1;36mopam: [1;37mhab-plan-build setup[0m | |
| [1;36mopam: [1;37mUsing HAB_BIN=/hab/pkgs/core/hab/0.24.1/20170522083228/bin/hab for installs, signing, and hashing[0m | |
| [1;36mopam: [1;37mResolving build dependencies[0m | |
| [1;36mopam: [1;37mResolving run dependencies[0m | |
| » Installing core/aspcud | |
| [1;36mopam: [1;37mResolved dependency 'core/aspcud' to /hab/pkgs/core/aspcud/1.9.1/20170609203426[0m | |
| » Installing core/camlp4 |
| frog-hornets-nest/automate/0.7.0-dev/20170221170131 | |
| frog-hornets-nest/automate-ctl/0.1.0/20170217222334 | |
| core/coreutils/8.25/20161208223423 | |
| core/glibc/2.22/20160612063629 | |
| core/linux-headers/4.3/20160612063537 | |
| core/acl/2.2.52/20161208223311 | |
| core/glibc/2.22/20160612063629 | |
| core/linux-headers/4.3/20160612063537 | |
| core/attr/2.4.47/20161208223238 | |
| core/glibc/2.22/20160612063629 |