-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #18981 from newrelic/daily-release/Oct-16-2024-11_36
Daily release/oct 16 2024 11 36
- Loading branch information
Showing
6 changed files
with
101 additions
and
13 deletions.
There are no files selected for viewing
62 changes: 62 additions & 0 deletions
62
...y-your-data/explore-query-data/query-builder/introduction-new-data-explorer.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
--- | ||
title: Introduction to the data explorer | ||
tags: | ||
- Query your data | ||
- Explore and query data | ||
- Data explorer | ||
metaDescription: 'The New Relic data explorer lets you run queries of your data without using NRQL-format queries' | ||
redirects: | ||
- /docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/#query-from-anywhere | ||
|
||
freshnessValidatedDate: never | ||
--- | ||
|
||
You can now explore all your data visually using the <DNT>**query experience data explorer**</DNT> without needing to know how to write [NRQL-format queries](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language). | ||
|
||
Need to perform a more detailed search? Read how to [query your data](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/). If you haven't already, create your free New Relic account to start monitoring your data today. | ||
|
||
|
||
## Importance of data explorer [#importance-of-data-explorer] | ||
|
||
Do you research the state of your systems? Do you need to plan resources, identify and respond to incidents, or troubleshoot faulty behaviors? The data explorer makes it easy to identify, fetch and visualize the data you are looking for through visual menus, without ever using NRQL or building queries. | ||
|
||
With the <DNT>**data explorer**</DNT>, you can access all data stored in the New Relic database (NRDB) in a quick, intuitive way. You can then select facet your queries using the attributes and filter down to the needed value. | ||
|
||
Other things the data explorer view helps you: | ||
|
||
* View data from different perspectives: from raw data to various visualizations that give insights on evolution, distribution, and more. | ||
* Drill down into data using filters. | ||
* Add your searches to a dashboard. | ||
* Understand how NRQL works: the Data Explorer automatically generates the NRQL queries based on your selections. | ||
|
||
### Types of data you can explore [#types-of-data] | ||
|
||
Following are the types of data you can explore using the <DNT>**Data Explorer**</DNT> view: | ||
|
||
* [Dimensional metrics](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics) (the Metric data type). | ||
* [Events](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic) (the Event data type). | ||
* [Logs](/docs/logs/ui-data/use-logs-ui) (the Log data type). | ||
|
||
## Explore your data [#explore-your-data] | ||
|
||
To access the Data Explorer, navigate to the bottom <DNT>**Query your data**</DNT> bar and click the <DNT>**Data Explorer**</DNT> icon. | ||
|
||
### Use the data explorer [#use-data-explorer] | ||
|
||
1. **Define the Scope**: Select the data type (metric, event, or log), the account, and the entities. | ||
2. **Select the Time Range**: Use the time picker to define the time range for your query. | ||
3. **Build Your Search**: Use the blocks on the left to browse the available data and construct your search. Blocks are searchable, and you can use the actions in the action menu to create and update your query. | ||
|
||
<img | ||
title="Data explorer view" | ||
alt="Data explorer view" | ||
src="/images/data-explorer.gif" | ||
/> | ||
|
||
### Components of the data explorer [#data-explorer-components] | ||
|
||
* **Select Your Data Type**: Choose between metrics, events, logs, and accounts. If you select metrics, you can filter by entity. | ||
* **Data Browsing Area**: Located on the left, this area allows you to navigate the data by clicking on the different values displayed on the screen or see the possible actions by clicking on the 3 dots action menu. | ||
* **Workspace**: This area displays the results of your selections. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
35 changes: 35 additions & 0 deletions
35
src/content/docs/style-guide/writing-docs/writer-workflow/edit-automated-docs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
title: How to edit automatically-generated docs | ||
--- | ||
|
||
Some of the teams at New Relic automatically generate docs content from their GitHub repositories. When these automatically-generated docs appear in pull requests for the main docs repository (`https://github.com/newrelic/docs-website`), writers need to edit these somewhat differently than manually generated docs. | ||
|
||
<Callout variant="tip"> | ||
You can determine whether a doc is automatically generated by looking at the author in GitHub. | ||
</Callout> | ||
|
||
## Challenges with editing automatically-generated docs [#challenges] | ||
|
||
When we edit automated documentation, this doesn't address the underlying automation that will generate the same documentation for the next release. | ||
|
||
We need a routine for editing docs that solves two issues: | ||
|
||
* Ensures that the current, automatically-generated pull request is fixed for publication. | ||
* Ensures that the underlying source for these automatically-generated docs is changed. | ||
|
||
## Best practices for editing automatically generated docs [#best-practices] | ||
|
||
When you're reviewing docs that were generated automatically from a repository, do the following: | ||
|
||
1. Make GitHub suggestions instead of pushing up changes directly. | ||
2. Contact the docs hero for the team that pushed up the changes: | ||
* This alerts developers to the suggestions you created. | ||
* They will accept or reject the suggestions. | ||
3. If the suggestions are accepted, merge those changes and publish the current release. | ||
4. If your suggestions also need to be made to the underlying source, create a Github issue in the corresponding team's repository. In that GitHub issue, link to the pull request in the public docs site. This will alert the development team to correct future automated releases. Here are some examples of repositories where you could create follow-up GitHub issues: | ||
* Node.js (`https://github.com/newrelic/node-newrelic`) | ||
* Ruby (`https://github.com/newrelic/newrelic-ruby-agent`) | ||
|
||
<Callout variant="tip"> | ||
For Node.js docs, you only need to create a corresponding GitHub issue if the suggestions you made were between the marker tags of an automatic doc (`{/* begin: compat-table */}` and `{/* end: compat-table */}`). Any changes outside those sections aren't affected by automation. | ||
</Callout> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.