Ryan Musser fIa5h

Utilizing New Relic APM inside of a Meteor application

This is a running log of information I plan to use to help me research, understand, implement and communicate why and how to utilize New Relic's APM suite inside of a Meteor application.

Why?

Meteor's rise to prominence (currently 30th ranked project on GitHub) has brought challenges for developers that choose to utilize the framework in a production environment. One of those challenges is application monitoring. With the downfall of Kadira, Meteor's defacto go to application monitoring service, developers have been relegated primarily to self hosting Kadira, or jumping into the larger Galaxy platform for insights.

Enter New Relic and it's industry leading APM suite.

#The api_console

The api console can be called from app/Console similar to this: ./cake api_console param param param

##Non user removing calls

./cake api_console "all"

This call assigns all users to the proper rooms based upon the most recent api dumps for all institutions

./cake api_console "$org_id" "$org_id"

	<script>
	/*
	INSTRUCTIONS
	To begin syncing this parameters with SFDC you will need to excplitly reference
	them as qualification attributes in your Intercom Qualification Data settings in the Intercom UI:
	https://www.intercom.com/help/faqs-and-troubleshooting/capture-qualify-and-convert-leads/what-is-qualification-data
	Then, you will need to map those qualification attributes to your SFDC lead fields in the Intercom UI.
	See the "Map and sync your qualification attributes" section of this document:
	https://www.intercom.com/help/apps-in-intercom/apps/salesforce-app
	*/

	//does Intercom exist in this scope
	if(window.Intercom){
	//track our event
	window.Intercom("trackEvent", "YOUR EVENT NAME");
	setTimeout(function(){
	//refresh our user, so we can take actions based off of the action above
	Intercom("update", {last_request_at: parseInt((new Date()).getTime()/1000)})
	}, 500);
	};

	<script>
	/*
	INSTRUCTIONS

	To begin syncing these parameters with SFDC you will need to excplitly reference
	them as qualification attributes in your Intercom Qualification Data settings in the Intercom UI:
	https://www.intercom.com/help/faqs-and-troubleshooting/capture-qualify-and-convert-leads/what-is-qualification-data

	Then, you will need to map those qualification attributes to your SFDC lead fields in the Intercom UI.
	See the "Map and sync your qualification attributes" section of this document:

	<script>
	(function() {
	var w = window;
	var ic = w.Intercom;
	if (typeof ic === "function") {
	ic('reattach_activator');
	ic('update', intercomSettings);
	} else {
	var d = document;
	var i = function() { i.c(arguments) };

	{
	"type": "notification_event_data",
	"item": {
	"type": "conversation",
	"id": "18255009678",
	"created_at": 1535647240,
	"updated_at": 1535952882,
	"user": {
	"type": "user",
	"id": "5b881d43dc78d66a0817eab9",

	//instantiate globally
	//below is the global array where we'll record the last 6 steps
	window.NewRelicDirectFunnelArray = ["", "", "", "", "", ""];
	//and the function we'll use to manage the data structure
	window.NewRelicDirectFunnelFunction = function(pageActionName){
	//capture a delimited string containing the last 6 pageActions since the initial pageload
	var previousSixPageActionsString = window.NewRelicDirectFunnelArray.join("\|\|");
	//dequeue the oldest pageAction value out of the queue
	window.NewRelicDirectFunnelArray.shift();
	//push the newest pageAction value into the queue

	/*
	New Relic GPT ad monitoring code
	//
	This snippet captures PageActions containing references to Google publisher tag ads
	Should you have any questions about this, please reach out to me at rmusser@newrelic.com
	Please note that you must be using New Relic's SPA browser agent.
	//
	*/
	//
	//first, make sure the newrelic object exists properly