W-15161420 tracing and entities

[sarathecoubian]

Writer's Quality Checklist

Before merging your PR, did you:

• Run spell checker
• Run link checker to check for broken xrefs
• Check for orphan files
• Perform a local build and do a final visual check of your content, including checking for:
  • Broken images
  • Dead links
  • Correct rendering of partials if they are used in your content
  • Formatting issues, such as:
    • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
    • Messed up tables
    • Proper indentation
    • Correct header levels
• Receive final review and signoff from:
  • Technical SME
  • Product Manager
  • Editor or peer reviewer
  • Reporter, if this content is in response to a reported issue (internal or external feedback)
• If applicable, verify that the software actually got released

[dhirsch1]

Some general comments:

• I see that some of the H1s don't match what is in the TOC. They should match unless you need to shorten the wording in the TOC.
• There is one indented topic under Explore Trace Data for Apps and APIs in the TOC. It is better not to have only one topic at this level if you can help it.
• It seems like you are documenting the interface in places where you don't need to do this. Can you see if you can make some of this information more task oriented and/or delete some of the interface documentation, such as when you list values?
• Consider using tables for lists of field descriptions. This is not a necessity, but they are easy to skim. If you want to keep descriptions in lists, separate the description from the field name with a + so that the description is on a different line. I marked this once but not everywhere it applies.
• Global: using > by using
• Remove lead articles from descriptions.

I didn't edit the commented text.

[dhirsch1]

Two "You can also..." in a row. Can you change the wording of one of them?

[dhirsch1]

I suggest using this format to make it easier to skim:

• Anypoint Monitoring Archive API

Enables...

[sarathecoubian]

Suggested change

	* `entry_api_version`: The version number of the API for which you want to see traces.
	* `entry_entity_id`: The ID of the entity for which you want to see traces.
	* `entry_entity_name`: The name of the entity for which you want to see traces.
	* `entry_entity_type`: The type of entity for which you want to see traces. You can query apps or APIs.
	* `entry_span_id`: The ID of a span contained in traces.
	* `entry_span_name`: The name of a span contained in traces.
	* `environment_name`: The name of the environment that contains entities for which you want to see traces.
	* `http_status_code`: The HTTP status code associated with a trace. You can query 0, 200, or 500 codes.
	* `trace_id`: The ID associated with a trace.
	* `entry_api_version`: TVersion number of the API for which you want to see traces.
	* `entry_entity_id`: ID of the entity for which you want to see traces.
	* `entry_entity_name`: Name of the entity for which you want to see traces.
	* `entry_entity_type`: Type of entity for which you want to see traces. You can query apps or APIs.
	* `entry_span_id`: ID of a span contained in traces.
	* `entry_span_name`: Name of a span contained in traces.
	* `environment_name`: Name of the environment that contains entities for which you want to see traces.
	* `http_status_code`: HTTP status code associated with a trace. You can query 0, 200, or 500 codes.
	* `trace_id`: ID associated with a trace.