> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.5.0/managing-akamas/akamas-logs.md). # Akamas logs Akamas allows dumping log entries from a specific service, workspace, workflow, study, trial, and experiment, for a specific timeframe and at different log levels. ## Akamas CLI for logs Akamas logs can be dumped via the following CLI command: ```bash akamas log ``` This command provides many filters which can be retrieved with the following command: ```bash akamas log --help ``` which should return ``` Usage: akamas log [OPTIONS] [MESSAGE] Show Akamas logs Options: -d, --debug Show extended error messages if present. --page-size INTEGER Number of log lines to be retrieved NOTE: This argument is mutually exclusive with arguments: [dump, no_pagination]. --no-pagination Disable pagination and print all logs NOTE: This argument is mutually exclusive with arguments: [dump, page_size]. --dump Print the logs without pagination and formatting NOTE: This argument is mutually exclusive with arguments: [page_size, no_pagination]. -f, --from [%Y-%m-%d|%Y-%m-%dT%H:%M:%S|%Y-%m-%d %H:%M:%S|%Y-%m-%dT%H:%M:%S.%f|%Y-%m-%d %H:%M:%S.%f|[-]nw|[-]nd|[-]nh|[-]nm|[-]ns] The start timestamp of the logs -t, --to [%Y-%m-%d|%Y-%m-%dT%H:%M:%S|%Y-%m-%d %H:%M:%S|%Y-%m-%dT%H:%M:%S.%f|%Y-%m-%d %H:%M:%S.%f|[-]nw|[-]nd|[-]nh|[-]nm|[-]ns] The end timestamp of the logs -s, --study TEXT UUID or name of the Study -e, --exp INTEGER Number of the experiment --trial INTEGER Number of the trial -y, --system TEXT UUID or name of the System -W, --workflow TEXT UUID or name of the Workflow -l, --log-level TEXT Log level -S, --service TEXT Akamas service --without-metadata Hide metadata --sorting [ASC|DESC] Sorting order of the timestamps -ws, --workspace TEXT UUID or name of the Workspace to visualize. When empty, system logs will be returned instead --help Show this message and exit. ``` For example, to get the list of the most recent Akamas errors: ```bash akamas log -l ERROR ``` which should return something similar to: ``` timestamp system provider service message ============================================================================================================================================================================================================================================================== 2022-05-02T15:51:26.88 - - airflow Task failed with exception 2022-05-02T15:51:26.899 - - airflow Failed to execute job 2 for task Akamas_LogCurator_Task 2022-05-02T15:56:29.195 - - airflow Task failed with exception 2022-05-02T15:56:29.215 - - airflow Failed to execute job 3 for task Akamas_LogCurator_Task 2022-05-02T16:01:55.587 - - license 2022-05-02 16:01:47.426 ERROR 1 --- [ main] c.a.m.utils.rest.RestHandlers : has failed with returning a response: {"httpStatus":400,"timestamp":"2022-05-02T16:01:47.413638","error":"Bad Request","message":"The following metrics: 'spark.spark_application_duration' were not found in any of the components of the system 'analytics_cluster'","path":null} 2022-05-02T16:01:55.587 - - license 2022-05-02 16:01:47.434 ERROR 1 --- [ main] c.a.m.MigrationApplication : Unable to complete operation. Mode: RESTORE. Cause: A request to a downstream service CampaignService has failed: 400 : [{"httpStatus":400,"timestamp":"2022-05-02T16:01:47.413638","error":"Bad Request","message":"The following metrics: 'spark.spark_application_duration' were not found in any of the components of the system 'analytics_cluster'","path":null}] 2022-05-02T16:01:55.678 - - license 2022-05-02 16:01:47.434 ERROR 1 --- [ main] c.a.m.MigrationApplication : Unable to complete operation. Mode: RESTORE. Cause: A request to a downstream service CampaignService has failed: 400 : [{"httpStatus":400,"timestamp":"2022-05-02T16:01:47.413638","error":"Bad Request","message":"The following metrics: 'spark.spark_application_duration' were not found in any of the components of the system 'analytics_cluster'","path":null}] 2022-05-02T16:01:55.678 - - license 2022-05-02 16:01:47.426 ERROR 1 --- [ main] c.a.m.utils.rest.RestHandlers : has failed with returning a response: {"httpStatus":400,"timestamp":"2022-05-02T16:01:47.413638","error":"Bad Request","message":"The following metrics: 'spark.spark_application_duration' were not found in any of the components of the system 'analytics_cluster'","path":null} 2022-05-02T16:12:10.261 - - license 2022-05-02 16:05:53.209 ERROR 1 --- [ main] c.a.m.services.CampaignService : de9f5ff9-418e-4e25-ae2c-12fc8e72cafc 2022-05-02T16:32:07.216 - - license 2022-05-02 16:31:37.330 ERROR 1 --- [ main] c.a.m.services.CampaignService : 06c4b858-8353-429c-bacd-0cc56cc44634 2022-05-02T16:38:18.522 - - campaign Internal Server Error: Object of class [com.akamas.campaign_service.entities.campaign.experiment.Experiment] with identifier [ExperimentIdentifier(workspace=ac8481d3-d031-4b6a-8ae9-c7b366f027e8, study=de9f5ff9-418e-4e25-ae2c-12fc8e72cafc, id=2)]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [com.akamas.campaign_service.entities.campaign.experiment.Experiment#ExperimentIdentifier(workspace=ac8481d3-d031-4b6a-8ae9-c7b366f027e8, study=de9f5ff9-418e-4e25-ae2c-12fc8e72cafc, id=2)] ``` ## Viewing platform logs By default akamas cli only shows logs of the current workspace. In order to see platform logs for events such as installation or optimization packs or telemetry providers you can specify the -ws option with an empty workspace name such as: ```bash akamas logs -ws ' -S license ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.akamas.io/akamas-docs/3.5.0/managing-akamas/akamas-logs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.