Skip to content

Commit

Permalink
Merge pull request #198 from ss1796/markdown-link-check-fixes
Browse files Browse the repository at this point in the history
Fixed broken links
  • Loading branch information
sguruvar authored Jan 14, 2025
2 parents 5c7b665 + df10994 commit 3b1aa72
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 12 deletions.
2 changes: 1 addition & 1 deletion docusaurus/docs/faq/adot.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
1. **I have a fleet of ADOT collectors, how can I manage them?**
This is an area of active development and we expect that it will mature in 2023, see the upstream OpenTelemetry docs on [Management](https://opentelemetry.io/docs/collector/management/) for more details, specifically on the [Open Agent Management Protocol (OpAMP)](https://opentelemetry.io/docs/collector/management/#opamp).
1. **How do you monitor the health and performance of the ADOT collector?**
1. [Monitoring the collector](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/monitoring.md) - default metrics exposed on port 8080 that can be scraped by the Prometheus receiver
1. [Monitoring the collector](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/observability.md) - default metrics exposed on port 8080 that can be scraped by the Prometheus receiver
2. Using the [Node Exporter](https://prometheus.io/docs/guides/node-exporter/), running node exporter would also provide several performance and health metrics about the node, pod, and operating system the collector is running in.
3. [Kube-state-metrics (KSM)](https://github.com/kubernetes/kube-state-metrics), KSM can also produce interesting events about the collector.
4. [Prometheus `up` metric](https://github.com/open-telemetry/opentelemetry-collector/pull/2918)
Expand Down
9 changes: 4 additions & 5 deletions docusaurus/docs/patterns/multiaccount.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,8 +39,7 @@ According to Gartner, by 2025, more than 95% of new digital workloads will be de

## References:

1. AWS Documentation: "Monitoring Multiple AWS Accounts" (https://docs.aws.amazon.com/solutions/latest/multi-account-monitoring/welcome.html)
2. Gartner Research: "Cloud Adoption Trends and Key Considerations for 2023" (https://www.gartner.com/en/documents/4009858)
3. Cloud Conformity Report: "The State of AWS Security and Compliance in the Cloud" (https://www.cloudconformity.com/knowledge-base/the-state-of-aws-security-and-compliance-in-the-cloud.html)
4. Forrester Research: "The Total Economic Impact™ Of AWS Cloud Governance Solutions" (https://d1.awsstatic.com/
5. How Audible used Amazon CloudWatch cross-account observability to resolve severity tickets faster (https://aws.amazon.com/blogs/mt/how-audible-used-amazon-cloudwatch-cross-account-observability-to-resolve-severity-tickets-faster/)
1. AWS Documentation: "CloudWatch cross-account observability" (https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html)
2. Cloud Conformity Report: "The State of AWS Security and Compliance in the Cloud" (https://www.trendmicro.com/cloudoneconformity/knowledge-base/aws/)
3. Forrester Research: "The Total Economic Impact™ Of AWS Cloud Operations" (https://pages.awscloud.com/rs/112-TZM-766/images/GEN_forrester-tei-cloud-ops_May-2022.pdf)
4. How Audible used Amazon CloudWatch cross-account observability to resolve severity tickets faster (https://aws.amazon.com/blogs/mt/how-audible-used-amazon-cloudwatch-cross-account-observability-to-resolve-severity-tickets-faster/)
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
これは活発に開発が進められている分野で、2023 年には成熟すると予想しています。詳細については、OpenTelemetry のアップストリームドキュメントの [管理](https://opentelemetry.io/docs/collector/management/) をご覧ください。特に [Open Agent Management Protocol (OpAMP)](https://opentelemetry.io/docs/collector/management/#opamp) に注目してください。

9. **ADOT コレクターの健全性とパフォーマンスをどのようにモニタリングしますか?**
1. [コレクターのモニタリング](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/monitoring.md) - ポート 8080 で公開されるデフォルトのメトリクスを Prometheus レシーバーでスクレイピングできます。
1. [コレクターのモニタリング](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/observability.md) - ポート 8080 で公開されるデフォルトのメトリクスを Prometheus レシーバーでスクレイピングできます。
2. [Node Exporter](https://prometheus.io/docs/guides/node-exporter/) を使用すると、コレクターが実行されているノード、Pod、オペレーティングシステムに関する様々なパフォーマンスと健全性のメトリクスも提供されます。
3. [Kube-state-metrics (KSM)](https://github.com/kubernetes/kube-state-metrics) は、コレクターに関する興味深いイベントを生成することもできます。
4. [Prometheus の `up` メトリクス](https://github.com/open-telemetry/opentelemetry-collector/pull/2918)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,7 @@ Gartner によると、2025 年までに新しいデジタルワークロード

## 参考文献:

1. AWS ドキュメント:「複数の AWS アカウントのモニタリング」(https://docs.aws.amazon.com/solutions/latest/multi-account-monitoring/welcome.html)
2. Gartner リサーチ:「2023 年のクラウド採用トレンドと主要な考慮事項」(https://www.gartner.com/en/documents/4009858)
3. Cloud Conformity レポート:「クラウドにおける AWS セキュリティとコンプライアンスの現状」(https://www.cloudconformity.com/knowledge-base/the-state-of-aws-security-and-compliance-in-the-cloud.html)
4. Forrester リサーチ:「AWS クラウドガバナンスソリューションの総経済的影響™」(https://d1.awsstatic.com/
5. Audible が Amazon CloudWatch クロスアカウントオブザーバビリティを使用して重大度チケットをより迅速に解決した方法 (https://aws.amazon.com/blogs/mt/how-audible-used-amazon-cloudwatch-cross-account-observability-to-resolve-severity-tickets-faster/)
1. AWS ドキュメント:「複数の AWS アカウントのモニタリング」(https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html)
2. Cloud Conformity レポート:「クラウドにおける AWS セキュリティとコンプライアンスの現状」(https://www.trendmicro.com/cloudoneconformity/knowledge-base/aws/)
3. Forrester リサーチ:「AWS クラウドガバナンスソリューションの総経済的影響™」(https://pages.awscloud.com/rs/112-TZM-766/images/GEN_forrester-tei-cloud-ops_May-2022.pdf)
4. Audible が Amazon CloudWatch クロスアカウントオブザーバビリティを使用して重大度チケットをより迅速に解決した方法 (https://aws.amazon.com/blogs/mt/how-audible-used-amazon-cloudwatch-cross-account-observability-to-resolve-severity-tickets-faster/)

0 comments on commit 3b1aa72

Please sign in to comment.