W-15161420 tracing and entities

modules/ROOT/nav.adoc

@@ -8,6 +8,7 @@
  ** xref:monitor-applications-on-rtf.adoc[Monitor Applications on Runtime Fabric]
  ** xref:am-installing.adoc[Monitor Hybrid Runtimes]
  ** xref:performance-and-impact.adoc[Anypoint Monitoring Performance, Impact, and Limits]
+* xref:anypoint-insights.adoc[Anypoint Insights]
 * xref:dashboards.adoc[About Dashboards]
 * xref:dashboards-using.adoc[Use Dashboards]
  ** xref:app-dashboards.adoc[Built-in Application Dashboards]
@@ -21,6 +22,8 @@
  ** xref:dashboard-custom-config-table.adoc[Configure Tables]
  ** xref:dashboard-custom-config-text.adoc[Configure Text]
  ** xref:dashboard-config-ref.adoc[Dashboard Configuration Reference]
+* xref:traces-overview.adoc[Exploring Trace Data for Apps and APIs]
+ ** xref:trace-details.adoc[Trace and Span Details]
 * xref:anypoint-custom-metrics-connector.adoc[Configure Custom Metrics]
 * xref:telemetry-exporter.adoc[]
 * xref:monitor-connectors.adoc[Monitor Connectors]
@@ -34,3 +37,4 @@
 * xref:log-points.adoc[Enable Log Points]
 * xref:raw-data.adoc[Download Raw Data]
 * xref:tools.adoc[Use Connectors with Anypoint Monitoring]
+* xref:am-apis.adoc[APIs for Anypoint Monitoring]

modules/ROOT/pages/_partials/amql.adoc

@@ -0,0 +1,233 @@
+// tag::amqlIntro[]
+Anypoint Monitoring Query Language (AMQL) is a domain-specific language that enables you to search your organization’s metering and observability data for specific information that the MuleSoft Observability Platform Service collects. 
+
+AMQL uses similar syntax to SQL `SELECT` statements.
+// end::amqlIntro[]
+
+// tag::queryGrammarUR[]
+
+To adhere to AMQL grammar, arrange your clauses in the following order: 
+
+[source,sql]
+----
+    SELECT fieldList,[aggregationExpressionList][...]
+    FROM DataSource
+    WHERE timestamp between {start} AND {end}[ AND filterExpression]
+    [ORDER BY fieldOrAggregationList {ASC|DESC}]
+    [LIMIT limit]
+    [OFFSET offset]
+----
+
+The following example returns usage data between March 11 and March 13, 2023. The data source is Flex Gateway API calls, and the fields returned are organization ID, environment ID, and how many API calls were made:
+
+[source,sql]
+----
+SELECT org_id, env_id, api_call_count 
+FROM flex_gateway_api_calls 
+WHERE timestamp between 1710198204000 AND 1710371004000  
+----
+
+// end::queryGrammarUR[]
+
+// tag::queryGrammarAll[]
+
+To adhere to AMQL grammar, arrange your clauses in the following order: 
+
+[source,sql]
+----
+    SELECT fieldList,[aggregationExpressionList][...]
+    FROM DataSource
+    WHERE timestamp between {start} AND {end}[ AND filterExpression]
+    [GROUP BY fieldGroupByList]
+    [HAVING havingConditionExpression]
+    [ORDER BY fieldOrAggregationList {ASC|DESC}]
+    [TimeSeries timeWindowSize]
+    [LIMIT limit]
+    [OFFSET offset]
+----
+// end::queryGrammarAll[]
+
+// tag::filtering[]
+The following clause shows AMQL filtering:
+
+[source,sql]
+----
+    filterExpression -> conditionExpresion [AND conditionExpression] 
+    conditionExpression -> field comparisonOperator [literal|literList|field| NULL]
+----
+
+// end::filtering[]
+
+// tag::grouping[]
+
+[source,sql]
+----
+    aggregationExpression -> aggregationFunction(field[,parameters])
+                    AggregationFunction = avg|sum|percentile|histogram|max|min|count
+    aggregatedConditionExpression -> aggregationFunction(field[,parameters]) comparisionOperator [literal|literalList]                  
+    havingConditionExpression -> aggregatedConditionExpression [ AND aggregatedConditionExpression]
+
+----
+// end::grouping[]
+
+// tag::reservedKeywords[]
+
+AMQL has several reserved keywords, which are not case sensitive. 
+
+* `AS`
+* `ASC`
+* `BETWEEN`
+* `BY`
+* `DESC` 
+* `FROM`
+* `GROUP`
+* `HAVING`
+* `IN`
+* `LIKE`
+* `LIMIT`
+* `OFFSET`
+* `ORDER`
+* `SELECT` 
+* `WHERE`
+* `TIMESTAMP`
+* `TIMESERIES`
+
+// end::reservedKeywords[]
+
+// tag::selectClause[]
+The `SELECT` clause enables you to get a list of fields in a data source using describe endpoints. 
+
+When you use `SELECT`, consider the following:
+
+* Use describe endpoints for each service to get a list of fields present in your data source.
+* Using `SELECT` with a wildcard (`select *`) returns all public endpoints for a data source. Not all data sources support this option.
+* Wrap string literals in single quotes.
+* Field names in `SELECT` clauses are case-sensitive. 
+* Using a field alias is supported. The syntax is `field AS aliasName`.
+* Wrap field names within double quotes to handle field names with special characters. The syntax is `select "field1", "field2.a" as 'fieldA' from dataSource`.
+* Aggregated fields support aliases. The syntax is `aggregationFunction(field, ..) AS alias`. If you don't provide an alias, the results return `aggregationFunction(field, ..)`.
+
+// end::selectClause[]
+
+// tag::whereClause[]
+The `WHERE` clause enables you to define your  `timestamp` range filter (in epoch milliseconds) and operators. 
+
+`WHERE` supports the following data types:
+
+* String literal
+* Integer
+* Decimal
+
+`WHERE` uses the following operators:
+
+|====
+|Filter Function |Filter Operator |Notes
+
+|`Equals`
+|`=`
+|
+
+|`NotEquals`
+|`!=`
+|
+
+|`greater`
+|`>`
+|
+
+|`greaterOrEquals`
+|`>=`
+|
+
+|`less`
+|`<`
+|
+
+|`lessOrEquals`
+|`+<=+`
+|
+
+|`in`
+|`IN`
+| in (...)
+
+|`between`
+|`BETWEEN`
+a|The timestamp field supports only `between`. For example: 
+
+[source,sql]
+----
+WHERE timestamp between 1710198204000 AND 1710371004000 
+----
+
+|`match pattern`
+|`LIKE`
+|This operator is a simplified version of the `match` operator, although it lacks regexp support. It supports only `wildcard`, noted as `*`.
+
+|====
+// end::whereClause[]
+
+// tag::groupingClauseUR[]
+
+The `GROUPING` clause enables you to aggregate numeric values using the following functions:
+
+|====
+|Aggregation |Arguments
+
+|`avg`
+|`<fieldName>`
+
+|`sum`
+|`<fieldName>`
+
+|`percentile`
+|`<fieldName, percentage value in range (0;100)>`
+
+|`max`
+|`<fieldName>`
+
+|`min`
+|`<fieldName>`
+
+|`count`
+|`<fieldName>`  or `<dimensionName>`
+
+|`distinct_count`
+|`<fieldName>` or `<dimensionName>`
+
+|`histogram`
+|`<fieldName, splitPointsArray>`
+
+|====
+
+Some fields in the data might not support certain aggregations.
+
+// end::groupingClauseUR[]
+
+// tag::timeseriesClause[]
+
+//was "The TIMESERIES clause takes time window size returns events aggregated in provided time-buckets."
+The `TIMESERIES` clause takes the time window size and returns events that are aggregated in time buckets you specified.
+
+Use the following format:
+
+[source,sql]
+----
+TimeWindowSize
+// n is an integer
+P{n}M // n months
+P{n}D // n days
+PT{n}H // n hours
+PT{n}M // n minutes
+PT{n}S // n seconds
+----
+
+The following examples show `TIMESERIES` windows:
+
+* 1 month: `TIMESERIES P1M`
+* 1 day: `TIMESERIES P1D`
+* 1 hour: `TIMESERIES PT1H`
+* 1 minute: `TIMESERIES PT1M`
+* 30 seconds: `TIMESERIES PT30S`
+
+// end::timeseriesClause[]

modules/ROOT/pages/_partials/archive-api.adoc

@@ -0,0 +1,9 @@
+You can access API analytics metrics data directly via the Anypoint Monitoring Archive API. Using this API, you can navigate and discover your API metrics data using a directory hierarchy.
+
+The Anypoint Monitoring Archive API enables you to download files that contain https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/Metric%20Data/[JSON objects] that represent one or more metric events. You can write an application to navigate the data collected by the API and integrate it into your own system.
+
+You can also enable non-aggregated API events by setting this property: `anypoint.platform.config.analytics.agent.api_raw_metrics.enabled=true`.
+These events contain more detailed information about each API invocation and can be accessed using the Anypoint Monitoring Archive API under the `raw` file type.
+
+For more information about this API, see the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/home/[Anypoint Monitoring Archive API] page in Anypoint Exchange. 
+include::reuse::partial$billing/pricing.adoc[tag=apiAvailability]

modules/ROOT/pages/_partials/data-aggregation.adoc

@@ -0,0 +1 @@
+Anypoint Monitoring aggregates data in charts based on the selected time interval. The number of data points shown in a chart varies based on your selected time interval.

modules/ROOT/pages/_partials/endpoint-operation-metrics.adoc

@@ -0,0 +1,7 @@
+Anypoint Monitoring collects top occurring endpoints or operations for each data collection interval. Endpoints or operations that are not top occurring are sorted into a group called *Other*.
+
+In each data collection interval, top occurring endpoints or operations vary. An endpoint or operation that is top occurring in one interval might not be top occurring in the next.
+
+In Anypoint Monitoring charts and tables, the data comes from multiple data collection intervals. As a result, aggregated data shown in the dashboard is an estimation since the intervals might not have the same top occurring endpoints or operations. The tables show approximate counts for the most commonly occurring endpoints or operations when the *Other* grouping appears.
+
+For example, when an endpoint occurs more often than other endpoints in one interval but less often in another interval, Anypoint Monitoring sorts it into the Other group for the first interval. In this case, the resulting table displays lower than actual values for that endpoint, since the metrics that do not appear are grouped into the *Other* group.

modules/ROOT/pages/_partials/include-nav-distributed-tracing.adoc

@@ -0,0 +1 @@
+. In the Anypoint Monitoring sidebar, click *Traces*.

modules/ROOT/pages/_partials/include-nav-entities.adoc

@@ -0,0 +1 @@
+. In the Anypoint Monitoring navigation menu, click *Insights*.

modules/ROOT/pages/_partials/include-nav-steps-no-permissions.adoc

@@ -1,2 +1,2 @@
-. Log in to Anypoint Platform.
+. Log in to Anypoint Platform with a user account that has xref:am-permissions.adoc[permission to access Anypoint Monitoring content] .
 . In the navigation bar or the main Anypoint Platform screen, click *Monitoring*.

modules/ROOT/pages/alerts.adoc

@@ -29,7 +29,7 @@ include::reuse::partial$billing/pricing.adoc[tag=monitoringAlerts]
 
 include::partial$include-nav-steps-no-permissions.adoc[]
 
-. In the Anypoint Monitoring navigation menu, click *Alerts*.
+include::partial$include-nav-alerts.adoc[]
 
 In the *Alerts* page, you can:
 

modules/ROOT/pages/am-apis.adoc

@@ -0,0 +1,58 @@
+= APIs for Anypoint Monitoring
+
+Anypoint Monitoring has APIs that enable you to view, sort, and query your data:
+
+* Anypoint Monitoring Archive API 
++
+Enables you to navigate and discover your API metrics data using a directory hierarchy.
+* Metrics API 
++
+Enables you to query and transform data from a specific time range using the Anypoint Monitoring Query Language.
+* Traces API 
++
+Enables you to query traces data using the Anypoint Monitoring Query Language.
+
+[[archive-api]]
+== Anypoint Monitoring Archive API
+
+include::partial$archive-api.adoc[]
+
+[[metrics-api]]
+== Anypoint Monitoring Metrics API
+
+WIP
+
+[[traces-api]]
+== Anypoint Monitoring Traces API
+
+WIP
+
+
+[[amql]]
+== Anypoint Monitoring Query Language (AMQL)
+
+include::monitoring::partial$amql.adoc[tag=amqlIntro]
+
+=== Query Grammar
+
+include::monitoring::partial$amql.adoc[tag=queryGrammarAll]
+
+=== Filtering
+
+include::monitoring::partial$amql.adoc[tag=filtering]
+
+=== Grouping
+
+include::monitoring::partial$amql.adoc[tag=grouping]
+
+=== Reserved Keywords
+
+include::monitoring::partial$amql.adoc[tag=reservedKeywords]
+
+=== SELECT Clause
+
+include::monitoring::partial$amql.adoc[tag=selectClause]
+
+=== WHERE Clause
+
+include::monitoring::partial$amql.adoc[tag=whereClause]