Issue Management Guide (for Users)

Learn how to check and manage various failures and threat situations occurring during infrastructure operations.

📁 Go to Issue Management →

📋 Overview

Issue Management is a menu for centrally managing all abnormal statuses detected by GIIP agents and security modules. Administrators can prioritize failures and record action results here.

🔍 Key Feature Descriptions

1. Issue List & Filtering

Classification by Severity: Categorized into
```
Critical
```
(Immediate action required),
```
Warning
```
(Caution), and
```
Info
```
(Simple information).
Status Filter: You can view unaddressed
```
Pending
```
issues and already resolved
```
Done
```
issues separately.
CSN Switcher: If managing multiple customer accounts (CSNs), you can filter issues for a specific CSN using the top switcher.

2. Issue Detailed View

Clicking an issue in the list reveals the following details:

Occurrence Time & Target: Indicates which server and when the failure started.
Failure Content: Provides specific text data such as error messages or security threat types.
Related Logs: Instantly check system logs before and after the time the issue occurred.

🛠️ Actions & Status Changes

Mark as Done: If you have completed the failure response, click the [Done] button at the bottom of the detailed page. The issue will either disappear from the list or be archived with a 'Completed' status.
Force Done: For known issues that occur persistently, you can use administrator permissions to forcefully mark them as done and temporarily suspend alarms.

💡 Tips

Regular Inspection: Manage technical debt by checking every morning if there are any issues remaining in a
```
Pending
```
status.
Search: Quickly find similar failure cases by searching with specific keywords (for example,
```
Disk Full
```
,
```
Unauthorized
```
).

🛠️ API Specification (for Developers)

We provide a dedicated API (SK-based) to integrate GIIP issue management functionality with external systems or scripts.

1. Authentication

Header:
```
x-api-key: {YOUR_SECRET_KEY}
```
Query:
```
?sk={YOUR_SECRET_KEY}
```

2. List Issues

Endpoint:
```
GET /api/giipIssuesSk
```
Parameters:
- ```
status
```
  (Optional):
```
PENDING
```
  ,
```
IN_PROGRESS
```
  ,
```
DONE
```
  ,
```
READY
```
  ,
```
REVIEW
```
  , etc.
- ```
csn
```
  (Optional): Specific Customer Serial Number

Response:

{
  "issues": [
    {
      "isn": 123,
      "title": "Disk Usage 95%",
      "status": "PENDING",
      "regdate": "2026-04-30T14:00:00Z",
      "summary": "Disk usage on Web-01 is critical...",
      "cSn": 71199
    }
  ]
}

3. Get Issue Details

Endpoint:
```
GET /api/giipIssuesSk
```
Parameters:
- ```
isn
```
  : Issue Serial Number (Integer)

Response:

{
  "issue": {
    "isn": 123,
    "title": "Disk Usage 95%",
    "content": "Full stack trace or detailed message here...",
    "status": "PENDING",
    "regdate": "2026-04-30T14:00:00Z",
    "cSn": 71199
  }
}

4. Create & Update Issue

Endpoint:

POST /api/giipIssuesSk

(Create) /

PUT /api/giipIssuesSk

(Update)

Body (JSON):
- ```
isn
```
  : (Required for Update) Issue Serial Number
- ```
title
```
  : Issue title
- ```
content
```
  : Detailed content
- ```
status
```
  : Status value (
```
PENDING
```
  ,
```
IN_PROGRESS
```
  ,
```
DONE
```
  ,
```
READY
```
  ,
```
REVIEW
```
  )
- ```
csn
```
  : Customer Serial Number

Example (Update Status Only):

curl -X PUT "https://giipfaw.azurewebsites.net/api/giipIssuesSk" \
  -H "Content-Type: application/json" -H "x-api-key: YOUR_SECRET_KEY" \
  --data '{"isn": 123, "status": "DONE"}'

Success Response:

{
  "success": true,
  "isn": 123,
  "message": "Success"
}

API Reference

For detailed API specifications of this feature, refer to the separate guide.

📘 GIIP Issue API Guide

Version: 1.1 Last Updated: 2026-04-30 Source:

giipv3/public/help/giip-issue-user.en.md