You've already forked dockerfiles
							
							
				mirror of
				https://github.com/vimagick/dockerfiles.git
				synced 2025-10-30 23:47:48 +02:00 
			
		
		
		
	update apm-server
This commit is contained in:
		
							
								
								
									
										15
									
								
								apm-server/README.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										15
									
								
								apm-server/README.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,15 @@ | ||||
| apm-server | ||||
| ========== | ||||
|  | ||||
| The [APM Server][1] receives data from [APM agents][2] and transforms them into | ||||
| Elasticsearch documents. It does this by exposing an HTTP server endpoint to | ||||
| which agents stream the APM data they collect. After the APM Server has | ||||
| validated and processed events from the APM agents, the server transforms the | ||||
| data into Elasticsearch documents and stores them in corresponding | ||||
| Elasticsearch indices. | ||||
|  | ||||
| The APM Server works in conjunction with APM agents, Elasticsearch, and Kibana. | ||||
| Please view the APM Overview for details on how these components work together. | ||||
|  | ||||
| [1]: https://www.elastic.co/guide/en/apm/server/current/index.html | ||||
| [2]: https://www.elastic.co/guide/en/apm/agent/index.html | ||||
| @@ -1,14 +0,0 @@ | ||||
| apm-server | ||||
| ========== | ||||
|  | ||||
| [Elastic APM][1] is an application performance monitoring system built on the | ||||
| Elastic Stack. It allows you to monitor software services and applications in | ||||
| real time, collecting detailed performance information on response time for | ||||
| incoming requests, database queries, calls to caches, external HTTP requests, | ||||
| etc. This makes it easier to pinpoint and fix performance problems quickly. | ||||
|  | ||||
| Elastic APM also automatically collects unhandled errors and exceptions. Errors | ||||
| are grouped based primarily on the stacktrace, so you can identify new errors | ||||
| as they appear and keep an eye on how many times specific errors happen. | ||||
|  | ||||
| [1]: https://www.elastic.co/guide/en/apm/get-started/current/index.html | ||||
		Reference in New Issue
	
	Block a user