alibabacloud-pai-feature-store-featuredb-usage-query

What this skill does

# PAI-FeatureStore FeatureDB Usage Query and Analysis

**Architecture**: PAI-FeatureStore Instance → FeatureDB Datasource → Feature Views → Usage Statistics

### Key Features

1. **Total Usage Analysis**: Query daily read/write totals across a date range (up to 30 days)
2. **Feature View Details**: Query specific feature view usage on a given date with sorting by read/write count
3. **Project-Level Analysis**: Query daily read/write totals for a specific project (up to 30 days)
4. **Feature View Trends**: Query daily read/write trends for a specific feature view (up to 30 days)
5. **Cost Calculation**: Calculate costs based on official pricing tiers for different regions

### Supported Regions

`cn-beijing`, `cn-hangzhou`, `cn-shanghai`, `cn-shenzhen`, `cn-hongkong`, `ap-southeast-1`, `ap-southeast-5`, `us-west-1`, `eu-central-1`

---

## Installation

> **Pre-check: Aliyun CLI >= 3.3.3 required**
>
> Run `aliyun version` to verify >= 3.3.3. If not installed or version too low,
> run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to update,
> or see `references/cli-installation-guide.md` for installation instructions.
>
> Then **[MUST]** run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation.
> **[MUST]** run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date.

**[MUST] CLI User-Agent** — Every `aliyun` CLI command invocation must include:
`--user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-feature-store-featuredb-usage-query`

The PAI-FeatureStore CLI plugin will be automatically installed when first used if auto-plugin-install is enabled.

**Timeout**: Default 10s is sufficient for all API calls.

---

## Authentication

> **Pre-check: Alibaba Cloud Credentials Required**
>
> **Security Rules:**
> - **NEVER** read, echo, or print AK/SK values (e.g., `echo $ALIBABA_CLOUD_ACCESS_KEY_ID` is FORBIDDEN)
> - **NEVER** ask the user to input AK/SK directly in the conversation or command line
> - **NEVER** use `aliyun configure set` with literal credential values
> - **NEVER** output any string resembling a key (e.g., `LTAI5t***`, `AccessKeyId: xxx`, `ak-***`)
> - **ONLY** use `aliyun configure list` to check credential status
>
> ```bash
> aliyun configure list
> ```
> Check the output for a valid profile (AK, STS, or OAuth identity).
>
> **If no valid profile exists, STOP here.**

---

## Required Parameters

> **IMPORTANT: Parameter Confirmation** — Before executing any command or API call, ALL user-customizable parameters (e.g., RegionId, instance names, CIDR blocks, passwords, domain names, resource specifications, etc.) MUST be confirmed with the user. Do NOT assume or use default values without explicit user approval.

| Parameter Name | Required/Optional | Description | Default Value |
|---------------|-------------------|-------------|---------------|
| RegionId | Required | Alibaba Cloud region ID. Must be one of the supported regions listed above. | None |
| WorkspaceId | Optional* | PAI workspace ID (numeric, e.g., `12345`). Required if DatasourceId is not provided. | None |
| DatasourceId | Optional* | FeatureDB datasource ID (numeric, e.g., `67890`). Required if WorkspaceId is not provided. | None |
| StartDate | Optional | Query start date in yyyy-MM-dd format. | 30 days ago (for total usage) or 7 days ago (for project/feature view) |
| EndDate | Optional | Query end date in yyyy-MM-dd format. | Yesterday |
| ProjectName | Optional | Project name (required for project-level and feature view queries). | None |
| FeatureViewName | Optional | Feature view name (required for feature view trend queries). | None |
| SortBy | Optional | Sort field: `ReadCount` or `WriteCount` | `ReadCount` |
| Order | Optional | Sort order: `ASC` or `DESC` | `DESC` |

**Note:** Either WorkspaceId or DatasourceId must be provided. If neither is provided, the skill will list all available FeatureDB datasources for user selection.

---

## RAM Permissions

This skill requires the following RAM permissions. See `references/ram-policies.md` for detailed policy configuration.

**Required Actions:**
- `paifeaturestore:ListInstances`
- `paifeaturestore:GetDatasource`
- `paifeaturestore:ListDatasources`
- `paifeaturestore:ListDatasourceFeatureViews`

---

## Core Workflow

### Functional Scope (MUST CHECK FIRST)

**This skill ONLY supports querying FeatureDB read/write usage statistics.** Any requests outside of "querying historical read/write counts or costs" are out of scope and must be politely declined with a list of supported features.

> **[MUST]** If request is out of scope, reject politely and list supported features:
>> "Sorry, this Skill only supports querying FeatureDB read/write usage statistics, not [user request]. Supported features: 1) Daily read/write totals 2) Feature view details 3) Usage trends 4) Cost calculation"

## Feature Selection Logic

Which features to execute depends on user's request:

| Scenario | Action |
|----------|--------|
| **Request out of scope or unsupported** | **Reject and list supported features** (see above) |
| User specifies supported feature(s) | Execute the specified feature(s) |
| User doesn't specify any feature | Execute **default behavior** (see below) |

### Supported Functions

1. **Query daily FeatureDB read/write totals from StartDate to EndDate** with analysis (max 30-day span)
2. **Query per-feature-view read/write counts for a specific date**, with sorting and analysis
3. **Query daily FeatureDB read/write totals for a specific project** from StartDate to EndDate with analysis (max 30-day span)
4. **Query daily FeatureDB read/write trends for a specific feature view** from StartDate to EndDate with analysis (max 30-day span)
5. **Calculate costs** based on official pricing and query results

### User-Friendly Prompts

Use descriptive names instead of function numbers when prompting, because "Function 3" is meaningless to users who haven't read this document.

### Execution Steps

#### Step 1: Verify PAI-FeatureStore Instance

```bash
aliyun paifeaturestore list-instances \
  --region <RegionId> \
  --status Running \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-feature-store-featuredb-usage-query
```

**Expected Output**: A list of running instances with their InstanceIds.

**Error Handling** (if no running instances found — **STOP, do NOT guess InstanceId**):
> No running PAI-FeatureStore instances found in this region. Please verify:
> 1. Is the RegionId correct?
> 2. Do you need to switch to a different region?
> 3. To activate PAI-FeatureStore, visit the [console](https://pai.console.aliyun.com/)

#### Step 2: Identify FeatureDB Datasource

**Case A: User provided WorkspaceId**

```bash
aliyun paifeaturestore list-datasources \
  --region <RegionId> \
  --instance-id <InstanceId> \
  --type FeatureDB \
  --workspace-id <WorkspaceId> \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-feature-store-featuredb-usage-query
```

**Case B: User provided DatasourceId**

> **[MUST]** When user provides DatasourceId, you MUST call GetDatasource or ListDatasources to verify the datasource type is `FeatureDB`. Do NOT skip this validation step.

```bash
aliyun paifeaturestore get-datasource \
  --region <RegionId> \
  --instance-id <InstanceId> \
  --datasource-id <DatasourceId> \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-feature-store-featuredb-usage-query
```

**Validation**: Check the `Type` field in the response. If `Type` is NOT `FeatureDB`, stop and inform the user that this datasource is not a FeatureDB datasource.

**Case C: Neither WorkspaceId nor DatasourceId provided**

```bash
aliyun paifeaturestore list-datasources \
  --region <RegionId> \
  --instance-id <InstanceId> \
  --type FeatureDB \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-feature-store-featuredb-usage-query
```

**Note**: This API is paginated. Calculate total pages from `TotalCount` and `Pa