amp events

このページはまだあなたの言語に翻訳されていません。 現在取り組んでいますので、後でもう一度確認してください。

amp events manages the events in a project's taxonomy. Taxonomy commands use the taxonomy:read and taxonomy:write scopes. Ingestion checks use analytics:read, or an ingestion API key with no OAuth scopes.

amp events list

List event taxonomy entries.

bash
amp events list --project <project_id> --limit 5

Requires the taxonomy:read scope.

amp events get

Get event taxonomy entry.

bash
amp events get --project <project_id> --event <event_type>

Requires the taxonomy:read scope.

amp events create

Create event taxonomy entry.

bash
amp events create --project <project_id> --event-type my_event

Requires the taxonomy:write scope.

amp events update

Update event taxonomy entry.

Use --project and --event to identify an existing event, then pass the fields to update. Pass --body-json to merge fields that don't have their own flag.

bash
amp events update --project <project_id> --event my_event --description "Updated description"

Requires the taxonomy:write scope.

amp events delete

Soft-deletes an event. Preview the deletion with --dry-run. At a terminal, the command asks for confirmation; pass --yes to skip the prompt.

bash
amp events delete --project <project_id> --event my_event --dry-run   # preview
amp events delete --project <project_id> --event my_event --yes       # confirm

Requires the taxonomy:write scope.

amp events check-ingestion-by-api-key

Checks whether Amplitude received any events for the project associated with the supplied ingestion API key during the preceding eight hours.

observed means at least one event was received in the evaluated window. not_observed means no events were received. inconclusive means no events were found, but the available data could not confirm their absence. Use the returned window when reporting or comparing results.

The window uses server upload time: when Amplitude received each event, rather than the event time supplied by the sender.

Provide polling_timeout_seconds to request server polling guidance. While another check is advised, successful responses include poll_after_seconds; its omission means clients should stop polling.

Checks recent event ingestion using an ingestion API key. This command requires --region <us|eu> and never infers an endpoint from credentials or configuration.

This command doesn't use your OAuth profile or PAT.

bash
amp events check-ingestion-by-api-key --api-key AMPLITUDE_API_KEY --region us
amp events check-ingestion-by-api-key --api-key AMPLITUDE_API_KEY --region us --timeout-seconds 10

amp events check-ingestion

Checks whether events reached an Amplitude project during a recent time window. Provide event_type to check one exact event type, or omit it to check for any event. The default lookback is 10 minutes. The returned window can begin up to five minutes earlier so the evaluation covers the complete starting interval.

observed means at least one matching event was found. not_observed means no matching event was found in the evaluated window. inconclusive means no matching event was found, but complete recent data was not available to confirm its absence. Use the returned window when reporting or comparing results.

This POST computes a result and does not mutate state, so it does not require an Idempotency-Key.

Provide polling_timeout_seconds to request server polling guidance. While another check is advised, successful responses include poll_after_seconds; its omission means clients should stop polling.

bash
amp events check-ingestion --project <project_id>
amp events check-ingestion --project <project_id> --event-type my_event
amp events check-ingestion --project <project_id> --lookback-minutes 30 --timeout-seconds 10

Requires the analytics:read scope.

amp events scheduled-actions list

List scheduled event deletions and blocks.

Requires the taxonomy:read scope.

amp events scheduled-actions get

Get a scheduled event deletion or block.

Requires the taxonomy:read scope.

amp events scheduled-actions create

Each event_type must already exist on the project and may appear only once in items. Update and cancel take scheduled-action ids, so they do not look up the event again. One pending scheduled action is allowed per event type. If that event already has a pending deletion or block, cancel it before creating another. The whole request fails if any item cannot be created.

Requires the taxonomy:write scope.

amp events scheduled-actions update

The whole request fails if any id is not a pending scheduled action on the project.

Requires the taxonomy:write scope.

amp events scheduled-actions delete

The whole request fails if any id is not a pending scheduled action on the project.

Requires --yes to apply changes, or --dry-run when supported to validate without applying changes.

Requires the taxonomy:write scope.

これは役に立ちましたか?

For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

このページでは