# Knowledge Hub

The **Knowledge Hub** is a centralised space for deep-dive answers, quick resolutions, and edge-case documentation across various Sprinto modules. Unlike primary documentation that covers broad workflows or standard operating procedures, the Knowledge Hub serves as a living library of:

* Platform-specific technical behaviours
* Unexpected system errors and how to resolve them
* Policy interpretation in product contexts
* Advanced monitoring or integration configurations
* Clarifications around timeframes, data logic, and sync expectations

These articles are often the result of internal investigations, support escalations, or configuration pitfalls that require nuanced understanding. If you’ve ever wondered about *why an ElastiCache CPU alarm is failing*, *which Linux distros Dr. Sprinto supports*, or *how GDPR applies to your company vs your product*, this is where you’ll find the answer.

***

### What You’ll Find

<table><thead><tr><th width="215.9765625">Topic</th><th>Description</th></tr></thead><tbody><tr><td><strong>Monitoring Troubleshooting</strong></td><td>Examples include CPU utilisation alarms for AWS ElastiCache or KnowBe4 training logic across 12 months.</td></tr><tr><td><strong>Platform Behaviour Clarification</strong></td><td>Explains why policies and trainings may not show up on the employee portal, or the role of 'identifiers' in critical access systems.</td></tr><tr><td><strong>Regulatory Interpretations</strong></td><td>Provides clear responses to compliance-related questions such as GDPR scope and coverage.</td></tr><tr><td><strong>Product Compatibility</strong></td><td>Documents OS-level compatibility and features, e.g. DrSprinto for various Linux distributions.</td></tr><tr><td><strong>Infrastructure Integration Guidance</strong></td><td>Covers use cases like adding alias names to AWS account IDs for better visibility in Sprinto.</td></tr></tbody></table>

***

### Use Cases

<table><thead><tr><th width="174.38671875">Use Case</th><th>Who It Helps</th><th>Example</th></tr></thead><tbody><tr><td>Troubleshooting failed monitors</td><td>Engineers, support teams</td><td>CPU alarms not working due to incorrect CloudWatch dimensions</td></tr><tr><td>Clarifying training check logic</td><td>Customer success, auditors</td><td>Understanding how Sprinto counts the “last 12 months” for KnowBe4 training</td></tr><tr><td>Compliance context</td><td>Legal, security teams</td><td>Understanding if GDPR applies to the company or the product</td></tr><tr><td>System configuration accuracy</td><td>DevOps, IT admins</td><td>Adding AWS aliases for better infrastructure visibility</td></tr><tr><td>Device management support</td><td>IT admins, endpoint managers</td><td>Identifying compatible Linux distros for DrSprinto deployment</td></tr></tbody></table>

***

### Knowledge Hub Articles

#### 1. AWS ElastiCache Datastore CPU Utilisation Failing Even After Alarm Set

**Problem:** CloudWatch alarms set on a replication group for AWS ElastiCache do not work as expected.

**Solution:**

* Identify if the instance is part of a replication group.
* Modify the CloudWatch dimension to monitor individual member nodes (e.g., `rh-prod-cache-cluster-001`, `rh-prod-cache-cluster-002`).
* Create separate CPU utilisation alarms for each node.

**Outcome:** More accurate monitoring and resolved failing checks.

***

#### 2. From Which Date Does Sprinto Start Counting the Last 12 Months for KnowBe4 Training Monitoring?

**Clarification:**

* Sprinto calculates the 12-month period for KnowBe4 training checks from the **current date**, looking back over the last 365 days.

***

#### 3. Is GDPR Meant to Apply to the Company or the Product?

**Answer:**

* GDPR applies to the **company** as a whole.
* The company must ensure that all its products and services that process personal data are GDPR-compliant.

***

#### 4. Trainings and Policies Not Showing Up in the Employee Portal

**Issue:** Policies and trainings may not appear immediately after onboarding.

**Resolution:**

* Wait 24 hours after onboarding and ensure that the user's **DOJ (Date of Joining)** is recorded.
* The employee portal syncs these details after the delay.

***

#### 5. What Are Identifiers in an Auto Critical Access System?

**Explanation:**

* Identifiers are unique tags or data points used to track and control access.
* Examples: usernames, employee IDs, email addresses.

***

#### 6. What Linux Distributions Are Compatible with DrSprinto?

**Supported Distributions:**

* Ubuntu
* Fedora
* Pop OS
* Manjaro
* Debian
* Linux Mint
* Kali OS

**DrSprinto Capabilities:**

* Native MDM tool for endpoint protection
* Ensures device-level encryption and secure handling of sensitive data

***

#### 7. How to Add an Alias Name for AWS Account IDs in Sprinto

**Steps:**

* Add an account alias in AWS.
* Once configured, it will be automatically reflected in the Infra section of Sprinto, displaying both the alias and the account ID.

***

### Why It Matters

As Sprinto scales across environments and customer types, nuanced platform behaviours and exception cases become increasingly common. The Knowledge Hub allows us to:

* Share resolutions faster
* Prevent repeated support escalations
* Educate internal teams and customers
* Reduce ambiguity around data logic and platform response

***

### When to Use Knowledge Hub Articles

Refer to the Knowledge Hub when:

* You’re facing a monitor that’s failing despite correct configuration
* A system behaviour doesn’t match the documentation
* You need platform-specific behaviour clarified
* You’re dealing with regulatory interpretation questions
* A customer needs proof of feature compatibility

***

### What’s Next?

This hub will continue to evolve with time. Expect more articles derived from actual implementation questions, audit scenarios, and integration setups.

For any unresolved edge cases, please contact Sprinto Support. If a solution is derived from your issue, it may just end up in the Knowledge Hub.