feat(Getting Started): Added a new getting started page

[nbaenam]

Added a new getting started page.

[github-actions]

Hi @nbaenam 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes).

[netlify]

✅ Deploy Preview for docs-website-netlify ready!

Name	Link
🔨 Latest commit	96bca33
🔍 Latest deploy log	https://app.netlify.com/sites/docs-website-netlify/deploys/66103a1173163b00086ef47d
😎 Deploy Preview	https://deploy-preview-16312--docs-website-netlify.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⏳ Netlify Preview Deployment Information

This comment will auto update when your preview build is ready

[akristen]

@rhetoric101 Is OpenTelemetry an integration? I'm a little hazy on the details here, but the way I understand it is that New Relilc has some kind of compatibility with OTel so that OTel customers can forward that data into New Relic.

i think this section might benefit from describing why would someone might OTel and New Relic? Or maybe telling a story about how using New Relic enhances OTel monitoring

[nbaenam]

I'm going to wait for what Rob has to say here.

[nbaenam]

Hey @rhetoric101, could you please check the paragraph and see if it's accurate? Thanks!

[akristen]

Hi, hi! I left some comments but I'll summarize at a high level why I suggested certain changes:

• I don't think we should reference "performance of your apps and service" or "health of your environment" or anything vague like that under every capability, bc it's vague and a little redundant. As an observability platform, it's assumed that we're doing something with performance, health, metrics, etc.
• When we talk about how a capability improves performance/tracks problems, we should be extremely specific about the kind of data that's being collected and how we're getting it. Not just MELT data, which is assumed, but the data that distinguishes each feature from one another. e.g., referencing packets for network performance monitoring, or clusters/pods for k8s, or HTTP domains for browser. I made a few suggestions for things like that. Since instrumentation is making a technology measurable, we should consider getting pretty specific about what's being measured from that tech, and why that's valuable.
• On a structural level, I do think we need to move 'How it works' to the front and maybe shorten the intro so both sections can appear above the fold.
• Explaining at a high level how the install process works and what instrumentation is is important before we frontload a lot of information about how we help you measure/monitor/improve different layers of a system. It's the rule of starting general then getting more specific: we should start generally about how the New Relic platform keeps your data for you, how you access it, then go specifically into the technologies we can collect data from
• We definitely need an NRDB and NRQL section. NRQL is the main tool that gives people the ability to find data and dashboards/alerts are built on top of it. We don't need to get too specific, but since we deal with data, it might be good to let customers know that you can query it a la SQL... You introduce NRQL already in dashboards, but i think it should be its own thing.
• NRDB is where the data goes. I def think this is more important than explaining service levels or even a tertiary feature like errors inbox.. Maybe it appears in the intro as a throw away thing. "Your data is then stored in the New Relic Database, or NRDB." It's a pretty key part of the data ingest pipeline so it can appear in a high level explanation of how new relic functions

[nbaenam]

I'm going to merge this PR because 2 TW has already reviewed it.