REGEXVAULTv2.0
Dev & Systems/Log Parsing
Verified Safe

Duration / Time Elapsed Extraction Regex for Java

/([0-9]+(?:\.[0-9]+)?)\s*(ns|us|ms|s|m|h|min|sec|milliseconds?|microseconds?|seconds?|minutes?|hours?)\b/i

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching duration / time elapsed extraction, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// Duration / Time Elapsed Extraction
// ReDoS-safe | RegexVault — Dev & Systems > Log Parsing

import java.util.regex.Pattern;

public class DurationTimeElapsedExtractionValidator {
    private static final Pattern PATTERN =
        Pattern.compile("([0-9]+(?:\\.[0-9]+)?)\\s*(ns|us|ms|s|m|h|min|sec|milliseconds?|microseconds?|seconds?|minutes?|hours?)\\b");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("completed in 125ms")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
completed in 125msno unit
elapsed: 3.5sjust 125
took 200 milliseconds0.5
duration: 1h30mtime elapsed
response time 0.045 secondsduration: abc

When to use this pattern

This pattern is drawn from the Dev & Systems > Log Parsing category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Go's log output uses '1.234s' format. Java often uses 'ms'. Normalize to a common unit (milliseconds) after extraction for reliable comparison across services.

Technical Notes

Groups: 1=numeric value, 2=unit. Covers nanoseconds to hours. The \b prevents partial unit matches. Parse to a canonical duration type after extraction for comparison and aggregation.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern