[Docs][Maps] Update the asset tracking tutorial

[jsanz]

Fixes #167484

Updates the asset tracking tutorial with the following improvements:

• From [Maps][Docs] Improve the asset tracking tutorial to work with Elastic Agent #167484, @Danouchka contributed improvements to the way the Elasticsearch assets are defined to work with Elastic Agent
• Moved some content to use the Kibana Console to generate assets, instead of going through all the UI elements
• Updated references to the data that tracks not only Portland buses but also trains and light trains
• Replaces the alert to use the Index connector
• Adds a new section on visualizing the alerts
• Images updated to Kibana 8.11 UI

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[jsanz]

Hi @nickpeihl @Danouchka I volunteered you to review this update to the Asset Tracking tutorial 😃 No rush about this at all!

The preview is available at

https://kibana_173999.docs-preview.app.elstc.co/guide/en/kibana/master/asset-tracking-tutorial.html

[Danouchka]

Hello I have followed the tutorial on a brand new 8.11.3 in Elastic Cloud and I get this in the Discover (despite the indice is growing and the agent is healthy)

[Danouchka]

Seems there's an issue with the ingest pipeline as the remove processor is not executed but the issue might be somewhere else

[nickpeihl]

lgtm! Thanks for updating the docs!

Added a comment where calling kbn APIs from DevTools in development returns an error. But it seems to work in production.

[nickpeihl]

Testing this on main returns an error. But it looks like this only happens in development environments right now. Tested a similar API on a 8.12 pre-production instance which works fine. Here is an existing issue about this.

I think we can keep this as it is as long as production environments are not affected.

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Please specify a version via elastic-api-version header. Available versions: [2023-10-31]"
}

[jsanz]

Hello I have followed the tutorial on a brand new 8.11.3 in Elastic Cloud and I get this in the Discover (despite the indice is growing and the agent is healthy)

Hi, the issue I see is that your index is not correctly defined, leaving a mapping of the trimet.time field as long, and that clashes with the Data View definition that expects that file to be a date (as far as I can see).

The root cause may be in the ingest process, where the index is not getting the correct template and ingest pipeline.

[Danouchka]

OK I see the issue, I missed the component template definition and the index template definition while going through the tutorial

[Danouchka]

Thanks @jsanz ! Now it's ok , I have corrected

[jsanz]

Thanks @jsanz ! Now it's ok , I have corrected

No worries, in d274496 I've set up the snippets as opened so they are easier to follow. It was my fault to put them collapsed making them harder to spot.