Post release Alloy documentation cleanup

[clayton-cornell]

Documentation across most of the Grafana stack contains references and content describing how to use the various modes of Grafana Agent. This documentation needs to be found, assessed, and either removed, updated, or completely rewritten for Alloy.

Challenges

• Old content. There are sections of the documentation that were written only for Agent Static or Agent Operator. This content will require either a full rewrite or removal.
• The Grafana UI hasn't been updated. If we update the documentation with Alloy-based content, we have to make sure that the UI has actually been updated. There are still cases where the UI only references Static or Operator.

Product areas that need to be assessed for Agent-->Alloy work

• Grafana
  • Tracking issue
• Cloud
  • Tracking issue
• K8s
  • Tracking issue
• AWS
  • Tracking issue
• Asserts
  • Tracking issue
• AppO11y
  • Tracking issue
• K6
  • Only references Datadog Agent. Nothing to change here
• Loki
  • Alloy issue: Update Loki documentation, Agent-->Alloy #884
• Tempo
  • Tempo tracking issue: [DOC] Update Tempo docs for Agent > Alloy tempo#3648
  • Alloy issue: Update Tempo documentation, Agent-->Alloy #881
• Pyroscope
  • Pyroscope tracking issue: [DOC] Update Pyroscope for Agent > Alloy pyroscope#3271
  • Alloy issue: Update Pyroscope documentation, Agent-->Alloy #883
• Mimir
  • Alloy issue: Update Mimir documentation, Agent-->Alloy #885
• Enterprise Metrics
  • Alloy issue: Update Enterprise Metrics documentation, Agent-->Alloy #946
• Cloud Metrics
  • Alloy issue: Update Cloud Metrics documentation, Agent-->Alloy #947
• Alerting
  • Tracking issue
• Incident
  • Tracking issue
• OnCall
  • Tracking issue
• Beyla
  • Tracking issue
• Other?
  • Tracking issue

List of Blogs and other pages that link to Agent: FROM -_ TO.txt