【问题标题】:how to Filter the full Log context using PowerShell如何使用 PowerShell 过滤完整的日志上下文
【发布时间】:2020-01-13 12:46:57
【问题描述】:

我正在尝试使用 Powershell 中的 Select-String 过滤掉日志及其完整上下文。我知道上下文的参数及其含义,但这限制了我想要实现的目标。下面是日志 sn-p,我想以日期作为搜索参数来搜索日志以选择字符串过滤器。

[AD Thread-Metric Reporter1] 16 Dec 2019 19:03:32,371 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
    at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
    at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
    at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
    at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
    at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
    at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
    at java.lang.Thread.run(Thread.java:748)
[AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956 ERROR SystemAgentPollingForUpdate - Fatal transport error while connecting to URL [/controller/instance/417/systemagentpolling]: org.apache.http.conn.ConnectTimeoutException: Connect to imswt01.ecbt1.tadnet.net:8090 [imswt01.ecbt1.tadnet.net/10.228.18.71] failed: connect timed out
[AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956  WARN SystemAgentPollingForUpdate - Invalid response for configuration request from controller/could not connect. Msg: Fatal transport error while connecting to URL [/controller/instance/417/systemagentpolling]
[AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956  WARN SystemAgentPollingForUpdate - System configuration request failed 5 times consecutively.
[AD Thread-Metric Reporter1] 16 Dec 2019 19:03:42,362 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
    at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
    at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
    at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
    at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
    at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
    at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
    at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
    at java.lang.Thread.run(Thread.java:748)

如果我运行我的代码

Select-String "16 Dec 2019" -context 0,10

然后它过滤匹配表达式下方的 10 行。我的问题是,如果日志条目的上下文较大且包含许多行怎么办?无论如何,我们是否一直在搜索和打印,直到记录新的日志条目?喜欢并且我们在不限制上下文的情况下获得整个 Log 条目上下文?

非常感谢,

【问题讨论】:

    标签: windows powershell logging powershell-5.0 select-string


    【解决方案1】:

    Select-String 可以工作,但它会很麻烦。 我会使用 switch 语句来代替实现一个简单的状态机。

    $inContext = $false
    gc yourlog | % {
        switch -RegEx ($_) {
            "16 Dec 2019" {$inContext = $true; $_ ; continue} 
            "^\[" {$inContext = $false; continue}
            default {if ($inContext) {$_}}
        }
    }
    

    编辑 cudo's to mklement0

    $inContext = $false
    switch -File yourlog -RegEx {
            "16 Dec 2019" {$inContext = $true; $_ ; continue} 
            "^\[" {$inContext = $false; continue}
            default {if ($inContext) {$_}}
    }
    

    Edit2 poc 使用提供的示例

    $inContext = $false
    @'
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:03:32,371 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
    [AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956 ERROR SystemAgentPollingForUpdate - Fatal transport error while connecting to URL [/controller/instance/417/systemagentpolling]: org.apache.http.conn.ConnectTimeoutException: Connect to imswt01.ecbt1.tadnet.net:8090 [imswt01.ecbt1.tadnet.net/10.228.18.71] failed: connect timed out
    [AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956  WARN SystemAgentPollingForUpdate - Invalid response for configuration request from controller/could not connect. Msg: Fatal transport error while connecting to URL [/controller/instance/417/systemagentpolling]
    [AD Thread Pool-Global0] 16 Dec 2019 19:03:37,956  WARN SystemAgentPollingForUpdate - System configuration request failed 5 times consecutively.
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:03:42,362 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:03:52,369 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
    [extension-scheduler-pool-1] 16 Dec 2019 19:03:55,283  WARN ProcessMonitor - ProcessMonitor::Caught exception during collection and reporting.
    feign.RetryableException: Connect to imswt01.ecbt1.tadnet.net:8090 [imswt01.ecbt1.tadnet.net/10.228.18.71] failed: Connection refused: connect executing PUT http://imswt01.ecbt1.tadnet.net:8090/controller/sim/v2/agent/machines/imswd97/processes
        at feign.FeignException.errorExecuting(FeignException.java:67)
        at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:102)
        at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:76)
        at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103)
        at com.sun.proxy.$Proxy126.updateProcessMetadata(Unknown Source)
        at com.appdynamics.sim.agent.extensions.servers.DoubleBufferedProcessProperties.reportProcesses(DoubleBufferedProcessProperties.java:75)
        at com.appdynamics.sim.agent.extensions.servers.ProcessMonitor.run(ProcessMonitor.java:78)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
    Caused by: org.apache.http.conn.HttpHostConnectException: Connect to imswt01.ecbt1.tadnet.net:8090 [imswt01.ecbt1.tadnet.net/10.228.18.71] failed: Connection refused: connect
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:159)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:221)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:165)
        at com.appdynamics.voltron.rest.client.impl.apache.ManagedHttpClient.execute(ManagedHttpClient.java:83)
        at com.appdynamics.voltron.rest.client.impl.apache.ApacheClientImpl.execute(ApacheClientImpl.java:77)
        at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:97)
        ... 12 more
    Caused by: java.net.ConnectException: Connection refused: connect
        at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
        ... 25 more
    [system-thread-0] 16 Dec 2019 19:03:55,643  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [AD Thread-Metric Reporter0] 16 Dec 2019 19:04:00,003  WARN ManagedMonitorDelegate - Metric Reporter Queue full. Dropping metrics.
    [system-thread-0] 16 Dec 2019 19:04:02,013  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:04:02,357 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
    [system-thread-0] 16 Dec 2019 19:04:08,387  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:04:12,358 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/417/metrics
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
    [Agent-Scheduler-1] 16 Dec 2019 19:04:23,615 ERROR ControllerTimeSkewHandler - Error response from controller: Connection back off limitation in effect: /controller/instance/417/current-time
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:04:27,365 ERROR ManagedMonitorDelegate - Fatal transport error while connecting to URL [/controller/instance/417/metrics]: org.apache.http.conn.ConnectTimeoutException: Connect to imswt01.ecbt1.tadnet.net:8090 [imswt01.ecbt1.tadnet.net/10.228.18.71] failed: connect timed out
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:04:27,365  WARN ManagedMonitorDelegate - Error sending metric data to controller:Fatal transport error while connecting to URL [/controller/instance/417/metrics]
    [AD Thread-Metric Reporter1] 16 Dec 2019 19:04:27,365 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
    com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Fatal transport error while connecting to URL [/controller/instance/417/metrics]
        at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350)
        at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:113)
        at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
        at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
        at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
        at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
        at java.lang.Thread.run(Thread.java:748)
      [system-thread-0] 16 Dec 2019 19:05:54,030  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,030  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,030  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,030  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,030  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,046  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,046  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,046  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,046  WARN DynamicMonitoringModeTask - Encountered error checking monitoring mode. Will retry in 60 seconds.
    [system-thread-0] 16 Dec 2019 19:05:54,046  WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
    [extension-scheduler-pool-6] 18 Dec 2019 19:31:36,365  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-3] 18 Dec 2019 19:36:36,369  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-9] 18 Dec 2019 19:41:36,374  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-11] 18 Dec 2019 19:46:36,378  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-1] 18 Dec 2019 19:51:36,382  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-7] 18 Dec 2019 19:56:36,387  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-8] 18 Dec 2019 20:01:36,391  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-7] 18 Dec 2019 20:06:36,396  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-9] 18 Dec 2019 20:11:36,400  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-6] 18 Dec 2019 20:16:36,405  INFO ReportMetricsConfigSupplier - Basic metrics will be collected and reported through the SIM extension because SIM is enabled.
    [extension-scheduler-pool-4] 18 Dec 2019 20:21:36,409  INFO ReportMetricsConfigSupplier - 
    '@ -split "`r`n" | % {
        switch -RegEx ($_) {
            "16 Dec 2019" { $inContext = $true; $_ ; continue} 
            "^\["{ $inContext = $false; continue}
            default { if ($inContext) {$_}}
        }
    }
    

    【讨论】:

    • 您好,感谢您的回复,但您的逻辑是打印出整个日志文件,而不是打印出匹配的参数“2019 年 12 月 16 日”及其上下文。
    • @MuntazirAbbas - 你能发布你的日志文件吗?
    • 即使上面的脚本也没有产生正确的输出。只需匹配匹配的字符串@LievenKeersmaekers
    • @MuntazirAbbas - 我们看不到你所看到的。我假设在[AD 上停止了上下文,但是查看您发布的内容,这是不正确的。我已将停止条件调整为^\[(以[开头的一行)
    • 非常感谢@LievenKeersmaekers 我现在明白了。你救了我的一天。
    猜你喜欢
    • 2011-01-23
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多