W E K A
4.0
4.0
  • WEKA v4.0 documentation
  • WEKA System Overview
    • About the WEKA system
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • Weka networking
    • Data lifecycle management
    • Weka client and mount modes
    • Weka containers architecture overview
    • Glossary
  • Getting Started with Weka
    • Quick installation guide
    • Manage the system using the Weka CLI
    • Manage the system using the Weka GUI
    • Run first IOs with WekaFS
    • Getting started with Weka REST API
  • Planning & Installation
    • Prerequisites for installation
    • Weka installation on bare metal
      • Planning a Weka System Installation
      • Prepare the system for Weka installation
        • SR-IOV enablement
      • Obtain the Weka software installation package
      • Weka cluster installation
      • WEKA legacy system installation process
      • Add clients
    • Weka installation on AWS
      • Self-service portal
      • CloudFormation template generator
      • Deployment types
      • AWS outposts deployment
      • Supported EC2 instance types
      • Add clients
      • Auto scaling group
      • Troubleshooting
  • Performance
    • Weka performance tests
      • Test environment details
  • WekaFS Filesystems & Object Stores
    • Manage object stores
      • Manage object stores using the GUI
      • Manage object stores using the CLI
    • Manage filesystem groups
      • Manage filesystem groups using the GUI
      • Manage filesystem groups using the CLI
    • Manage filesystems
      • Manage filesystems using the GUI
      • Manage filesystems using the CLI
    • Attach or detach object store buckets
      • Attach or detach object store bucket using the GUI
      • Attach or detach object store buckets using the CLI
    • Advanced data lifecycle management
      • Advanced time-based policies for data storage location
      • Data management in tiered filesystems
      • Transition between tiered and SSD-only filesystems
      • Manual fetch and release of data
    • Mount filesystems
    • Snapshots
      • Manage snapshots using the GUI
      • Manage snapshots using the CLI
    • Snap-To-Object
      • Manage Snap-To-Object using the GUI
      • Manage Snap-To-Object using the CLI
    • Quota management
  • Additional Protocols
    • NFS
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • SMB
      • Manage SMB using the GUI
      • Manage SMB using the CLI
    • S3
      • S3 cluster management
        • Manage the S3 service using the GUI
        • Manage the S3 service using the CLI
      • S3 buckets management
        • Manage S3 buckets using the GUI
        • Manage S3 buckets using the CLI
      • S3 users and authentication
        • Manage S3 users and authentication using the CLI
        • Manage S3 service accounts using the CLI
      • S3 rules information lifecycle management (ILM)
        • Manage S3 rules using the CLI
      • Audit S3 APIs
        • Configure audit webhook using the GUI
        • Configure audit webhook using the CLI
        • Example: How to use Splunk to audit S3
      • S3 supported APIs and limitations
      • S3 examples using boto3
  • Operation Guide
    • Alerts
      • Manage alerts using the GUI
      • Manage alerts using the CLI
      • List of alerts and corrective actions
    • Events
      • Manage events using the GUI
      • Manage events using the CLI
      • List of events
    • Statistics
      • Manage statistics using the GUI
      • Manage statistics using the CLI
      • List of statistics
    • System congestion
    • Security management
      • Obtain authentication tokens
      • KMS management
        • Manage KMS using the GUI
        • Manage KMS using the CLI
      • TLS certificate management
        • Manage the TLS certificate using the GUI
        • Manage the TLS certificate using the CLI
      • CA certificate management
        • Manage the CA certificate using the GUI
        • Manage the CA certificate using the CLI
      • Account lockout threshold policy management
        • Manage the account lockout threshold policy using GUI
        • Manage the account lockout threshold policy using CLI
      • Manage the login banner
        • Manage the login banner using the GUI
        • Manage the login banner using the CLI
    • User management
      • Manage users using the GUI
      • Manage users using the CLI
    • Organizations management
      • Manage organizations using the GUI
      • Manage organizations using the CLI
      • Mount authentication for organization filesystems
    • Expand and shrink cluster resources
      • Expand and shrink overview
      • Workflow: Add a backend host
      • Expansion of specific resources
      • Shrink a Cluster
    • Background tasks
    • Upgrade Weka versions
  • Billing & Licensing
    • License overview
    • Classic license
    • Pay-As-You-Go license
  • Support
    • Prerequisites and compatibility
    • Get support for your Weka system
    • Diagnostics management
      • Traces management
        • Manage traces using the GUI
        • Manage traces using the CLI
      • Protocols debug level management
        • Manage protocols debug level using the GUI
        • Manage protocols debug level using the CLI
      • Collect and upload diagnostics data
    • Weka Home - The Weka support cloud
      • Local Weka Home overview
      • Local Weka Home deployment
      • Set the Local Weka Home to send alerts or events
      • Download the Usage Report or Analytics
  • Appendix
    • Weka CSI Plugin
    • Set up the Weka-mon external monitoring
    • Set up the SnapTool external snapshots manager
  • REST API Reference Guide
Powered by GitBook
On this page
  • Configure traces
  • Freeze traces
  • Change traces verbosity level
  • Restore traces default settings
  1. Support
  2. Diagnostics management
  3. Traces management

Manage traces using the GUI

PreviousTraces managementNextManage traces using the CLI

Last updated 2 years ago

Using the GUI, you can:

Configure traces

The tracking tool collects the traces on the backends and clients and retains them on their disks. You can limit the capacity used by the traces by ensuring minimum free capacity and by setting the maximum capacity that traces can use.

Procedure

  1. From the menu, select Configure > Cluster Settings.

  2. From the left pane, select Support.

  3. On the Traces section, select Configure traces.

  4. On the Configure Traces dialog set the following properties:

    • The minimum free capacity to preserve on the backends.

    • The minimum free capacity to preserve on the clients.

    • The maximum capacity traces can use on backends.

    • The maximum capacity traces can use on clients.

  5. Select Save.

Freeze traces

Sometimes you may need to investigate an issue that occurred during a certain period. You can retain the tracing data of that period using the freeze traces action.

Procedure

  1. From the menu, select Configure > Cluster Settings.

  2. From the left pane, select Support.

  3. On the Traces section, select Freeze traces.

  4. On the Freeze Traces dialog set the following properties:

    • Start: The start date and time of the period to freeze (mandatory).

    • End: The end date and time of the period to freeze.

    • Retention: The time to retain the tracing data. After this time, the tracking tool may purge the tracing data according to its purging cycle.

    • Override: If a freezing period is already set, you can override it by setting the Override button to On.

  5. Select Save.

6. To clear the freeze period, select Reset traces freeze. Then, in the confirmation message, select Yes.

Change traces verbosity level

The verbosity level determines the amount of information in the tracing data. Switching the verbosity level to high provides more troubleshooting details but may use more space on the disk.

Procedure

  1. In the Traces section, depending on the current verbosity level (low or high), select Change traces level to high or Change traces level to low.

Restore traces default settings

You can restore the traces configuration to its default settings as shown in the following image.

The default maximum capacity per IO-node is 50 GB and the minimum for all IO-nodes is 100 GB. The minimum free capacity is 3.22 GB

Procedure

  1. In the Traces section, select Restore traces default settings. Then, in the confirmation message, select Yes.

Configure traces
Freeze traces
Change traces verbosity level
Restore traces default settings
Manage traces
Configure traces
Freeze traces
Example of a freeze period
Change verbosity level
Traces default settings