profile
viewpoint

ebrodymoore/earnings 0

Text message recommendations for executing post-earnings announcement drift investment strategy

issue commentsourcegraph/sourcegraph

Tour implementation

From #11833

For the analytics, the ideal scenario is adding these two events:

  • ViewOnboardingTour (when the onboarding tour is shown)
  • CloseOnboardingTourClicked with the stage/step the user was at in the tour (e.g. stage: 2)
rrhyne

comment created time in 6 days

Pull request review commentsourcegraph/sourcegraph

Log click events on search homepage and repogroup page

 interface Props     showCampaigns: boolean } -const SearchExampleClicked = (): void => eventLogger.log('ExampleSearchClicked')-const LanguageExampleClicked = (): void => eventLogger.log('ExampleLanguageSearchClicked')+const SearchExampleClicked = (url: string) => (): void => eventLogger.log('ExampleSearchClicked', { url })

No objections from me. Thanks @attfarhan

attfarhan

comment created time in 11 days

Pull request review commentsourcegraph/sourcegraph

Log click events on search homepage and repogroup page

 export const RepogroupPage: React.FunctionComponent<RepogroupPageProps> = (props     ) } +const RepoLinkClicked = (): void => eventLogger.log('RepogroupPageRepoLinkClicked')

Yeah exactly

attfarhan

comment created time in 13 days

pull request commentsourcegraph/sourcegraph

Log click events on search homepage and repogroup page

@attfarhan the naming convention is good!

attfarhan

comment created time in 13 days

Pull request review commentsourcegraph/sourcegraph

Log click events on search homepage and repogroup page

 export const RepogroupPage: React.FunctionComponent<RepogroupPageProps> = (props     ) } +const RepoLinkClicked = (): void => eventLogger.log('RepogroupPageRepoLinkClicked')

If we can pass along data about the specific click that'd be ideal!

attfarhan

comment created time in 13 days

push eventsourcegraph/sourcegraph

Eric Brody-Moore

commit sha 1b6dd154a73e063ffc3de21d113a035379e756f3

updated query took out the 'where' clause in the first subquery. it takes about 3 seconds on dotcom compared to 15 seconds before

view details

push time in 20 days

push eventsourcegraph/sourcegraph

Eric Brody-Moore

commit sha 8118a59f0e1071516481ef05c07b9fbb3e5d89d2

Update query for performance

view details

push time in 21 days

pull request commentsourcegraph/sourcegraph

pings: RFC 197 (user accounting metrics)

If it's slow then we could EXPLAIN ANALYZE it with https://flame-explain.com/

What would you characterize as slow?

ebrodymoore

comment created time in 21 days

Pull request review commentsourcegraph/about

Add sales-to-CE handover process docs, move license keys docs to CE handbook

+# Sales-to-CE new customer handover process++When a new deal is signed, the Account Executive, Customer Engineer, and finance and operations teammates should follow the steps below to ensure the new customer is successful.++## Sales responsibilities++1. Copy the [new customer questionnaire template](https://docs.google.com/document/d/1FiuD-F3rMnTWRkLJizYPgGnpRDRYI1gEB0RAoV8i4AQ/edit#) to a new file (in the same Google Drive folder) and fill it out for the new customer.+1. Post in the #sales Slack channel to announce the sale, and link to the completed new customer questionnaire.+    1. Notify CE by tagging @ce-team.+    1. Notify finance and operations by tagging @business-team.+1. Send a welcome email to the new customer to introduce the CE and to indicate that the CE is their new main point of contact. ++>Hi $COMPANY team,+>Great news—the final docs were just signed. We're thrilled to make this partnership official! +>+>I wanted to introduce $CE, a member of our Customer Engineering team. $CE will be your primary point of contact now that we are past the paperwork and onto the release and rollout, but I'll still be here for you wherever I can help. If you run into any product bugs or have any technical questions, please use our support@sourcegraph.com email (which will go directly to $CE as well).+>+>How is $DATE for a quick check-in to discuss next steps? $CE and I will join to sketch out next steps and prepare for the full rollout. +>+>Best,+>$NAME++1. Update the deal status to "Closed" in HubSpot.++## CE responsibilities++1. The CE team will assign an account owner (typically the same CE that worked on the opportunity before the deal was signed).+1. Rename the shared customer Slack channel from #trial-customer to #support-customer (if applicable).+1. [Create a new license key](../ce/license_keys.md) that reflects the terms of the deal.+1. Once the AE has sent the welcome email, CE is responsible for:+    1. Responding to that email with the new license key (or sending it directly to the administrator, e.g. in Slack).+    1. Following up on any responses and getting the next check-in call on the calendar.+1. If the customer is or has potential to be a [Tier 1 customer](index.md#segmentation), create a success plan using the AE's new customer questionnaire and, if needed, organizing time to discuss plans with the AE.++## Finance and operations responsibilities++1. Once notified by the AE, the finance team will create an invoice and send it via email to the "Point of contact for invoicing/billing" from the new customer questionnaire.+1. Once notified by the AE, the operations team will update the customer status in the [installers-to-company spreadsheet](https://docs.google.com/spreadsheets/d/1Y2Z23-2uAjgIEITqmR_tC368OLLbuz12dKjEl4CMINA/edit#gid=0).
1. Once notified by the AE, the operations team will update the customer status in the [installers-to-company spreadsheet](https://docs.google.com/spreadsheets/d/1Y2Z23-2uAjgIEITqmR_tC368OLLbuz12dKjEl4CMINA/edit#gid=0).
1. The operations team will update the [sources of truth](../../bizops/index.md#sources-of-truth) to reflect the new deal.
dadlerj

comment created time in 21 days

push eventsourcegraph/sourcegraph

Eric Brody-Moore

commit sha 4ee9ff2c431d7e8fee5af4aeca6e9401306ffc0b

Update pings.md

view details

push time in 22 days

push eventsourcegraph/sourcegraph

Eric Brody-Moore

commit sha 48467b1f5782f5918a40665a384456b1e3632b0f

Update SiteAdminPingsPage.tsx

view details

push time in 22 days

PR opened sourcegraph/sourcegraph

Reviewers
pings: RFC 197 (user accounting metrics)

Add metrics listed in RFC 197 to pings )all monthly):

  • Number of created users
  • Number of deleted users
  • Number of resurrected users
  • Number of retained users
  • Number of churned users

<!-- Reminder: Have you updated the changelog and relevant docs (user docs, architecture diagram, etc) ? -->

+117 -0

0 comment

5 changed files

pr created time in 22 days

create barnchsourcegraph/sourcegraph

branch : growth-stats-pings

created branch time in 22 days

issue commentsourcegraph/sourcegraph

Initial search tour

For the analytics, the ideal scenario is adding these two events:

  • ViewOnboardingTour
  • CloseOnboardingTourClicked with the stage/step the user was at in the tour (e.g. stage: 2)
rrhyne

comment created time in 25 days

push eventsourcegraph/about

Eric Brody-Moore

commit sha 97ab7bcf550b3c630419e4a7972ae45d840e9837

Post to Lever if no debrief (#1183) Proposing the HM posts to Lever to close the loop for those who interviewed the candidate and to limit confusion about cancelled debriefs

view details

push time in 25 days

delete branch sourcegraph/about

delete branch : debrief-lever-process

delete time in 25 days

PR merged sourcegraph/about

Reviewers
Post to Lever if no debrief

Proposing the HM posts to Lever to close the loop for those who interviewed the candidate and to limit confusion about cancelled debriefs

+2 -0

0 comment

1 changed file

ebrodymoore

pr closed time in 25 days

push eventsourcegraph/about

Eric Brody-Moore

commit sha 648020100318d9341d57c1c6d5e482bc4be4bfbd

Add line break

view details

push time in 25 days

PR opened sourcegraph/about

Reviewers
Creating email lists

Best practices approach to creating email lists in HubSpot

+9 -0

0 comment

1 changed file

pr created time in 25 days

create barnchsourcegraph/about

branch : creating-email-lists

created branch time in 25 days

PR opened sourcegraph/about

Reviewers
Post to Lever if no debrief

Proposing the HM posts to Lever to close the loop for those who interviewed the candidate and to limit confusion about cancelled debriefs

+2 -0

0 comment

1 changed file

pr created time in 25 days

create barnchsourcegraph/about

branch : debrief-lever-process

created branch time in 25 days

issue commentsourcegraph/sourcegraph

Add anonymous user ID to HubSpot forms

Could we use a solution like this to maintain the cookie across the subdomain?

ebrodymoore

comment created time in a month

pull request commentsourcegraph/sourcegraph

Add new metrics to site admin usage statistics

This one's on me. I thought we had buy-in for these changes but now we're changing the pricing structure and need to reflect that in this dashboard so we'll be holding off on this until a future iteration

lguychard

comment created time in a month

push eventsourcegraph/about

Eric Brody-Moore

commit sha 01d313158f0036f8a99169eee408b2da0261fc4f

Add analytics onboarding + small reorg (#1100) * Add analytics onboarding + small reorg * Add quick links back in

view details

push time in a month

delete branch sourcegraph/about

delete branch : analytics-onboarding

delete time in a month

PR merged sourcegraph/about

Reviewers
Add analytics onboarding + small reorg
+34 -53

0 comment

5 changed files

ebrodymoore

pr closed time in a month

push eventsourcegraph/about

Eric Brody-Moore

commit sha e6f3e52d3cb0aaa2124f9d4033027b6db6028cfa

Add quick links back in

view details

push time in a month

issue commentsourcegraph/sourcegraph

Add browser argument to BrowserExtensionConnectedToServer event

@lguychard could we get this into 3.18 also to understand the breakdown of extension by browser?

ebrodymoore

comment created time in a month

issue commentsourcegraph/sourcegraph

Add 'activity histogram' to admin usage stats + rearrange

Updates are reflected in Figma and a doc for the queries. I'm getting a final review on this because we've added more since this issue was opened. @lguychard @tsenart do you know who/when this will be worked on in 3.18?

ebrodymoore

comment created time in a month

issue commentsourcegraph/sourcegraph

RFC 159: Stage 1 - repository group pages tracking issue

@attfarhan could you add two logged events with these additions:

  • ViewRepositoryGroup for when any of these individual repo group page is viewed
  • RepositoryGroupSuggestionClicked when a suggested search is clicked (in red below) Screen Shot 2020-06-25 at 3 25 02 PM
christinaforney

comment created time in a month

issue openedsourcegraph/sourcegraph

Missing events from eventLog

Here's are the results from my eventLog audit. Could you review and then I'll go ahead and assign the web team.

created time in a month

issue commentsourcegraph/sourcegraph

Add Google Analytics event tracking to cloud deployments

Actually could we switch that to ViewRepositoryGroup____? Would it be accurate to call that page 'RepositoryGroupHome' instead of page?

rrhyne

comment created time in a month

issue commentsourcegraph/sourcegraph

Add Google Analytics event tracking to cloud deployments

@rrhyne are you ok with the following changes (for syntax consistency): SearchResultFileClicked SearchModeRegexpToggled SearchModeStructuralToggled SearchModeCaseSensitivityToggled

rrhyne

comment created time in a month

pull request commentsourcegraph/careers

Add FP&A role

Sounds good, I just wasn't sure if you wanted to frame it as broader than FP&A!

dadlerj

comment created time in a month

pull request commentsourcegraph/careers

Add FP&A role

@dadlerj why not just Financial Analyst?

dadlerj

comment created time in a month

PR opened sourcegraph/sourcegraph

Reviewers
Remove DisableNonCriticalTelemetry

Changes based on @juliasourceress proposal

<!-- Reminder: Have you updated the changelog and relevant docs (user docs, architecture diagram, etc) ? -->

+2 -2

0 comment

1 changed file

pr created time in a month

create barnchsourcegraph/sourcegraph

branch : ebrodymoore-patch-1

created branch time in a month

Pull request review commentsourcegraph/careers

Add FP&A role

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Financial planning & analysis++We are looking for the first hire on our finance team. You will help establish the accounting and financial systems and processes we need to succeed and grow as a Series B start-up.++Our team and our sales are growing fast—we’ve proven strong product-market fit, with wall-to-wall usage, Net Promoter Scores above 60, and tens of thousands of paid daily active users at some of the world’s premier development teams (Uber, Yelp, Lyft, SoFi, Quantcast, and many more).++You will help us build the financial and accounting systems to manage our growth.++## Responsibilities++### In the first 30 days you will...++- Go through a week-long training program on our product, our value propositions, our customers, our team, and our processes.+- Dive deep into our financials, our OKRs, our business metrics, and all of our systems for measuring and tracking all of the above.+- Meet our external accounting team and each of our internal organization leads.+- Take ownership of our monthly reporting, A/P, and A/R efforts.+- Run an evaluation of our tooling and propose a recommendation for improvement to a key system.++### In the first 90 days you will...++- Use existing materials to build a quarterly 1-year and 3-year forward-looking models to be shared with our Board of Directors on an ongoing basis+  - Work with our go-to-market operations and business operations team.+- Take ownership of our quarterly (and annual) financial planning and help us establish an internal budgeting process.+- Be deeply involved if/when any strategic finance discussions arise, including fundraising, M&A, debt financing, and more.+- Take on at least one strategic initiative to improve our financial systems and processes.++## Qualifications+
- An excitement for software development (no training as an Engineer required, but you should have an understanding of how software development happens and Sourcegraph's value proposition).
- Demonstrated background in strategic or operational finance functions roles (Finance, BizOps, or Accounting at a technology company, Consulting, Investment Banking, etc.)
dadlerj

comment created time in a month

Pull request review commentsourcegraph/careers

Add GTM (sales) operations role

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Go-to-market (Sales) Operations Analyst++We are looking for the first hire on our go-to-market/sales operations team, and the second on our broader business operations team. You will enable and help our GTM teams sell to and support our customers better and faster. You will own sales forecasting and planning, formulation and management of sales and customer engineering incentive programs, collection and analysis of go-to-market metrics, pipeline and territory assignment, and most importantly, defining sales and customer engineering strategy.++Our team and our sales are growing fast—we’ve proven strong product-market fit, with wall-to-wall usage, Net Promoter Scores above 60, and tens of thousands of paid daily active users at some of the world’s premier development teams (Uber, Yelp, Lyft, SoFi, Quantcast, and many more).++You will help build the organization that enables us to reach every developer in the world faster and more efficiently. ++## Responsibilities++### In the first 30 days you will...++- Go through a week-long training program on our product, our value propositions, our customers, our team, and our processes.+- Go through an additional week-long training program on our customer lifecycle, our sales processes, and our support and success functions.+- Dive deep into our OKRs, our metrics (both revenue/ARR and usage/engagement), and our CRM and marketing suite (HubSpot) to understand how we measure our pipeline and customer engagement.+- Work with the rest of our Business Operations team to understand our go-to-market data collection, needs and gaps, and current modeling capabilities.+- Take ownership of our sales and customer engineering OKRs and tracking.++### In the first 90 days you will...++- Take ownership of our quarterly revenue forecasting process for new accounts and expansion/upsells.+  - Work with our finance and accounting team to build a complete go-to-market top and bottom-line forecast model.+- Take ownership of our sales and customer engineering incentive program management.+- Take on at least one strategic initiative to optimize our sales and/or customer engineering funnels. E.g., sales process evaluation, customer communications playbook, support processes and SLAs, customer success metrics and alerts, and more.++## Qualifications++- A passion and excitement for software development (no training as an Engineer required, but you should have an understanding of how software development happens and Sourcegraph's value proposition).

Passion sounds really strong to me and this could turn people off

dadlerj

comment created time in a month

Pull request review commentsourcegraph/careers

Add GTM (sales) operations role

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Go-to-market (Sales) Operations Analyst++We are looking for the first hire on our go-to-market/sales operations team, and the second on our broader business operations team. You will enable and help our GTM teams sell to and support our customers better and faster. You will own sales forecasting and planning, formulation and management of sales and customer engineering incentive programs, collection and analysis of go-to-market metrics, pipeline and territory assignment, and most importantly, defining sales and customer engineering strategy.++Our team and our sales are growing fast—we’ve proven strong product-market fit, with wall-to-wall usage, Net Promoter Scores above 60, and tens of thousands of paid daily active users at some of the world’s premier development teams (Uber, Yelp, Lyft, SoFi, Quantcast, and many more).++You will help build the organization that enables us to reach every developer in the world faster and more efficiently. ++## Responsibilities++### In the first 30 days you will...++- Go through a week-long training program on our product, our value propositions, our customers, our team, and our processes.+- Go through an additional week-long training program on our customer lifecycle, our sales processes, and our support and success functions.+- Dive deep into our OKRs, our metrics (both revenue/ARR and usage/engagement), and our CRM and marketing suite (HubSpot) to understand how we measure our pipeline and customer engagement.+- Work with the rest of our Business Operations team to understand our go-to-market data collection, needs and gaps, and current modeling capabilities.+- Take ownership of our sales and customer engineering OKRs and tracking.++### In the first 90 days you will...++- Take ownership of our quarterly revenue forecasting process for new accounts and expansion/upsells.+  - Work with our finance and accounting team to build a complete go-to-market top and bottom-line forecast model.+- Take ownership of our sales and customer engineering incentive program management.+- Take on at least one strategic initiative to optimize our sales and/or customer engineering funnels. E.g., sales process evaluation, customer communications playbook, support processes and SLAs, customer success metrics and alerts, and more.++## Qualifications++- A passion and excitement for software development (no training as an Engineer required, but you should have an understanding of how software development happens and Sourcegraph's value proposition).
- An excitement for software development (no training as an Engineer required, but you should have an understanding of how software development happens and Sourcegraph's value proposition).
dadlerj

comment created time in a month

Pull request review commentsourcegraph/careers

Add GTM (sales) operations role

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Go-to-market (Sales) Operations Analyst++We are looking for the first hire on our go-to-market/sales operations team, and the second on our broader business operations team. You will enable and help our GTM teams sell to and support our customers better and faster. You will own sales forecasting and planning, formulation and management of sales and customer engineering incentive programs, collection and analysis of go-to-market metrics, pipeline and territory assignment, and most importantly, defining sales and customer engineering strategy.
We are looking for the first hire on our go-to-market/sales operations team, and the second on our broader business operations team. You will enable and help our GTM teams sell to and support our customers better and faster. You will own sales forecasting and planning, formulation and management of sales and customer engineering incentive programs, collection and analysis of go-to-market metrics in collaboration with the marketing team, pipeline and territory assignment, and most importantly, defining sales and customer engineering strategy.
dadlerj

comment created time in a month

Pull request review commentsourcegraph/careers

Add GTM (sales) operations role

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Go-to-market (Sales) Operations Analyst

I would recommend going with sales or go-to-market (I prefer sales); another option would be Sales Strategy and Operations Analyst (sounds cooler 😄)

dadlerj

comment created time in a month

PR opened sourcegraph/about

Reviewers
Add analytics onboarding + small reorg
+30 -53

0 comment

5 changed files

pr created time in a month

push eventsourcegraph/about

Eric Brody-Moore

commit sha 2c670c9df3c363013a8f9a12564c9ca8276921b3

Add analytics onboarding + small reorg

view details

push time in a month

create barnchsourcegraph/about

branch : analytics-onboarding

created branch time in a month

issue openedsourcegraph/sourcegraph

Add anonymous user ID to HubSpot forms

For RFC 185, we need to start capturing anonymous user ID as a hidden field in all our HubSpot forms (demo, contact).

I've added the anonymous_user_id as a hidden field to the contact and demo forms. This just needs to be filled with the anonymous user ID we embed in localStorage. This HubSpot link is similar to what might need to be done. I struggle to add a lot more knowledge behind this so @dadlerj is probably the best resource to answer more technical questions about this.

created time in a month

pull request commentsourcegraph/about

Add Slack messaging during off-hours policy

@dadlerj already here, actually! https://about.sourcegraph.com/company/remote/tips

dadlerj

comment created time in 2 months

pull request commentsourcegraph/about

Add Slack messaging during off-hours policy

I'll leave it up to you on whether this is the place for it, but some related advice I've gotten is to be really intentional with written communication (especially with different time zones) because otherwise an async conversation can take days and possible slow your work down

dadlerj

comment created time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha d25751364657b72d55e9ffc0558ac23a6652f705

Add bizops commitments for updating financial metrics (#1054)

view details

push time in 2 months

delete branch sourcegraph/about

delete branch : updating-cadence-financials

delete time in 2 months

PR merged sourcegraph/about

Reviewers
Add bizops commitments for updating financial metrics

FYI @sqs @dadlerj - this is what I'm proposing for how often we keep the 'cash receipts' spreadsheet up-to-date

+1 -0

0 comment

1 changed file

ebrodymoore

pr closed time in 2 months

PR opened sourcegraph/about

Reviewers
Add bizops commitments for updating financial metrics

FYI @sqs @dadlerj - this is what I'm proposing for how often we keep the 'cash receipts' spreadsheet up-to-date

+1 -0

0 comment

1 changed file

pr created time in 2 months

create barnchsourcegraph/about

branch : updating-cadence-financials

created branch time in 2 months

issue openedsourcegraph/sourcegraph

Add browser argument to BrowserExtensionConnectedToServer event

Now that we're sending browser extension data to Sourcegraph.com, could we add which browser it's coming from?

To me, the most logical path would be to add browser: Chrome (or similar) as an argument to the event BrowserExtensionConnectedToServer. Does that seem like the best route for this?

I'm only interested in this data for Sourcegraph.com, but it would give us the option to add to pings at a later date.

@lguychard tagging you on this because it'd be in the web team domain (pun intended)

created time in 2 months

issue openedsourcegraph/sourcegraph

Add event logging to campaign pages

Events are not triggering on campaign pages.

Slack conversation

created time in 2 months

push eventsourcegraph/sourcegraph

Dan Adler

commit sha fc354691095f3b9905584f523a0d0aca538b83f9

Add argument field to BigQuery event logs (#11251) * Add argument field to BigQuery event logs * cast

view details

push time in 2 months

delete branch sourcegraph/sourcegraph

delete branch : bq-args

delete time in 2 months

PR merged sourcegraph/sourcegraph

Reviewers
Add argument field to BigQuery event logs

@ebrodymoore before this is merged, we need to test that this doesn't break anything with events that actually contain JSON argument data... My #1 concern is that we wouldn't be properly escaping the characters, so an arguments field that looks like {"query_data": { "combined": "<SEARCH STRING>", ... } } would break things if <SEARCH STRING> itself contained {s and ,s and etc.

Would you be able to do that test? Let me know if I can help here!

Note that we are already capturing search query data at https://sourcegraph.com/github.com/sourcegraph/sourcegraph@89f9e5f0889ae3966fe76f65c06ef1f743785386/-/blob/web/src/search/queryTelemetry.tsx#L10:9

+2 -0

4 comments

1 changed file

dadlerj

pr closed time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha 0dfe1b5f57adf8f47f4ecc8457ff41777e0b17ca

viewing license keys (#1038)

view details

push time in 2 months

delete branch sourcegraph/about

delete branch : ebrodymoore-patch-2

delete time in 2 months

PR merged sourcegraph/about

viewing license keys
+4 -0

0 comment

1 changed file

ebrodymoore

pr closed time in 2 months

PR opened sourcegraph/about

Reviewers
viewing license keys
+4 -0

0 comment

1 changed file

pr created time in 2 months

create barnchsourcegraph/about

branch : ebrodymoore-patch-2

created branch time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha bae3cb2dcfa9d36b06930955574c1fb2ad71fa14

new MQL definition (#955) * new MQL definition * exclude domains * Update index.md * Update index.md * Update index.md

view details

push time in 2 months

delete branch sourcegraph/about

delete branch : mql-definition-update

delete time in 2 months

PR merged sourcegraph/about

Reviewers
new MQL definition
+5 -2

0 comment

1 changed file

ebrodymoore

pr closed time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha cfd4c07e8610eb4105a3f83e8e6619adf75c0d58

Update index.md

view details

push time in 2 months

issue commentsourcegraph/sourcegraph

Add 'activity histogram' to admin usage stats + rearrange

Web team conversation going on here. Let's hold off and involve this in 3.18 planning. We'll want to add more graphs soon so let's just wait and do it all at once

ebrodymoore

comment created time in 2 months

issue commentsourcegraph/sourcegraph

Add 'activity histogram' to admin usage stats + rearrange

@tsenart only assigning you because you were gracious enough to do part 1 and you may have the best view on who should do part 2 😄

ebrodymoore

comment created time in 2 months

issue openedsourcegraph/sourcegraph

Add 'activity histogram' to admin usage stats + rearrange

Part 2 to RFC 145

The following are also reflected in [Figma]:(https://www.figma.com/file/B8c4C4FwQaigNw5QTOcgov/Admin-Panel?node-id=0%3A1)

  • Add activity histogram to usage tab (query is in RFC 145)
  • Create 'user activity logs' tab and move the user table from activity tab to this new tab

created time in 2 months

issue commentsourcegraph/sourcegraph

Add ping JSONs back into admin dashboard

@slimsag good to know, thanks! Would this be in distribution's purview or another team?

ebrodymoore

comment created time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha f0c8353fd011a5fbbfcac1a401d2e3543a3eb4df

debugging pings (#858) * debugging pings * Update index.md * Update index.md * add life of a ping link

view details

push time in 2 months

delete branch sourcegraph/about

delete branch : debugging-pings

delete time in 2 months

PR merged sourcegraph/about

Reviewers
debugging pings

@dadlerj please add more context you think would be helpful, in particular what to look for in the Stackdriver logs!

+17 -0

1 comment

1 changed file

ebrodymoore

pr closed time in 2 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha d386573cb354b1abd80a4bc6e9980384ef4b2c37

Update index.md

view details

push time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha dfb7dfa48ca17098dea45eea9a34f618e1764ac4

Update index.md

view details

push time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha d8d97fc9e98e7d343a6b333be17fa1c93df71f66

exclude domains

view details

push time in 3 months

pull request commentsourcegraph/about

debugging pings

@dadlerj friendly ping on this (pun intended)

ebrodymoore

comment created time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha 2d857bd418b4baa6bf6306d691aee39fb45e6a37

Update adding_ping_data.md (#929) New link to pubsub message

view details

push time in 3 months

delete branch sourcegraph/about

delete branch : update-adding-pings

delete time in 3 months

PR merged sourcegraph/about

Reviewers
Update adding_ping_data.md

New link to pubsub message

+2 -2

0 comment

1 changed file

ebrodymoore

pr closed time in 3 months

PR opened sourcegraph/about

Reviewers
new MQL definition
+2 -2

0 comment

1 changed file

pr created time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha ce2fb3540c88bfe23d7f4cd9f59b8a7882f2c7c8

new MQL definition

view details

push time in 3 months

create barnchsourcegraph/about

branch : mql-definition-update

created branch time in 3 months

issue commentsourcegraph/sourcegraph

Reduce number of queries for pings

Do we need p50 and p90 or is p99 latency enough?

I would say no, we don't need p50 and p90. @rvantonder @efritz any objections?

dadlerj

comment created time in 3 months

pull request commentsourcegraph/sourcegraph

updatecheck: Simplify return values

LGTM 👍

@dadlerj just to clarify, does this mean you're ok merging without alerting?

ryanslade

comment created time in 3 months

issue commentsourcegraph/about

Add cookie for maintaining UTM parameters after navigating from landing page

@aileenrose FYI I haven't looked at your comment in detail yet but there was PII in your comment that I removed (this repo is public)

aileenrose

comment created time in 3 months

issue openedsourcegraph/sourcegraph

Add cookie for maintaining UTM parameters after navigating from landing page

Background

We can't report the effectiveness of digital campaigns unless UTM parameters are maintained once the browser navigates from a landing page. Results right now are showing close to 0 MQLs for all marketing campaigns through the utm_source parameter, which I don't think is true.

More discussion here: https://sourcegraph.slack.com/archives/CNC4YAL1E/p1589302784090800

created time in 3 months

Pull request review commentsourcegraph/about

debugging pings

 We collect data from the following:  We have [written policies about how we handle customer information](customer_data_policy.md).  +## Debugging pings++Use this section to debug ping abnormalities (from top to bottom).

@dadlerj agree with those suggestions. I've been thinking about changing the architecture of the page; I'll address that in a separate PR 👍

ebrodymoore

comment created time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha 7aefb1c0e53086f565689df3121a01ca87675f6a

add life of a ping link

view details

push time in 3 months

PR opened sourcegraph/about

Reviewers
Update adding_ping_data.md

New link to pubsub message

+2 -2

0 comment

1 changed file

pr created time in 3 months

create barnchsourcegraph/about

branch : update-adding-pings

created branch time in 3 months

issue commentsourcegraph/sourcegraph

RFC 145: Event-level data from customers export button

That's all correct, thanks @dadlerj . As long as the output is usage stats aggregated by individual user, I'm fine with any implementation - you know better than I do about the best way to get there.

It's important to note that GetSearchUsageStatistics and GetCodeIntelUsageStatistics are important, but a user does not necessarily have to take one of these actions to be an 'active user'. In the sample output in the RFC there are circumstances where the user was active but search and codeintel actions were null/zero, and these users still need to show up in this output.

ebrodymoore

comment created time in 3 months

issue openedsourcegraph/sourcegraph

RFC 145 implementation

RFC 145

cc @christinaforney

created time in 3 months

issue commentsourcegraph/sourcegraph

Add ping JSONs back into admin dashboard

cc @dadlerj

ebrodymoore

comment created time in 3 months

issue openedsourcegraph/sourcegraph

Add ping JSONs back into admin dashboard

Feature request description

A section/tab in the admin dashboard of the latest ping JSON sent back to Sourcegraph, and what the full ping would look like (in the case the admin has pings turned off).

Is your feature request related to a problem? If so, please describe.

$CUSTOMER was wondering what the pings looked like because they were thinking about re-enabling. Dan had to do a lot of background work to get this.

This also would make it easier for testing when adding a ping.

Describe alternatives you've considered.

Adding an example ping JSON to the docs, but this is hard to maintain for all versions.

Additional context

We had this at one point (according to Dan).

created time in 3 months

push eventsourcegraph/about

Eric Brody-Moore

commit sha 394c5ad58ae49af50de693dee42b8982827179ad

Update index.md

view details

push time in 3 months

PR opened sourcegraph/about

Reviewers
debugging pings

@dadlerj please add more context you think would be helpful, in particular what to look for in the Stackdriver logs!

+14 -0

0 comment

1 changed file

pr created time in 3 months

more