Quickstart with Docker-Compose
This document describes the steps needed to bring up the Apica Ascent observability stack using docker-compose for trial and demo use
Last updated
Was this helpful?
This document describes the steps needed to bring up the Apica Ascent observability stack using docker-compose for trial and demo use
Last updated
Was this helpful?
docker-compose based deployment should not be used for production envornments.
Log aggregation, search, reporting, and live tailing
APM using built-in Prometheus, using external Prometheus
Data sources - 21 data source connectors
Alerting
Incident response - PagerDuty, ServiceNow, Slack, Email
apicactl CLI connectivity
Dashboards and visualizations
Filtering rules and rule packs
User and group management
Log flow RBAC
UI Audit trail
You can spin-up Apica Ascent using docker-compose. Install guide for docker-compose can be found here -
The first step is to get the docker-compose YAML file from the URL below.
You are now ready to bring up the Apica Ascent stack.
If you are done with your evaluation and want to cleanup your environment, please run the following command to stop and delete the Apica Ascent stack and free up the used system resources.
Once the Apica Ascent server is up and running, the Apica Ascent UI can be accessed as described above on port 80 on the server docker-compose. You will be presented with a login screen as shown below.
The quickstart compose file includes a test data tool that will generate test log data and also has a couple of dashboards that show Apica Ascent's APM capabilities.
The test log data can be viewed under Explore page
Click on any Application and you will be taken to the Flows page with detailed logs and a search view. You can search for any log pattern, searches can also be run using regex expressions along with conditional statements using Advanced search across a time period.
Apica Ascent provides application performance monitoring (APM) which can help end-to-end monitoring for microservices architectures, traces can be sent over 14250 (gRPC port). To view traces, navigate to Trace page under Explore.
select the Service and a list of traces will appear on the right-hand side of the screen. The traces have titles that correspond to the Operator selector on the search form. The traces can be further analyzed by clicking on the Analyse icon which will pull up the entire logs for the corresponding trace-id.
Analyze icon displays all the logs for the respective trace-id in a given time range.
To view the detailed trace, you can select a specific trace instance and check details like the time taken by each service, errors during execution, and logs.
The Apica Ascent quickstart file includes Prometheus and Alertmanager services. 2 APM Dashboards to monitor the quickstart environments are included.
⬇ Download the YAML at the URL -
For setting up data ingestion from your endpoints and applications into Apica Ascent, please refer to the .
Please refer to the supported by Apica.
