← Featured work

Professional · Observability

PRTG Infrastructure Monitoring & Remediation

Auditing ESXi and network monitoring, correcting safe configuration issues, validating discovery, and documenting the exceptions that still need investigation.

Production monitoring review

I want an alert to tell us something useful. Clearing a warning without fixing or understanding it doesn’t help.

  1. 01Audit coverage
  2. 02Check configuration
  3. 03Validate sensors
  4. 04Track exceptions

Coverage you can trust

A monitoring system needs to identify the intended endpoint, use appropriate credentials and protocols, and produce meaningful sensors. A reachable device or a green status does not establish that the important infrastructure is covered.

What I worked on

  • Audited ESXi and network infrastructure monitoring and reviewed VMware configuration.
  • Identified ESXi devices with overridden but missing VMware credentials and HTTP/HTTPS inconsistencies.
  • Reviewed auto-discovery behavior and tested discovery after configuration changes.
  • Investigated WAN/network endpoint identity and whether monitoring covered the intended resources.
  • Corrected safe configuration issues while preserving monitoring behavior; documented exceptions requiring manual follow-up.

Validate the effect of a change

A corrected configuration is followed by a sensor or discovery check. When discovery returns zero sensors, I keep that as an unresolved coverage issue and investigate the endpoint, credentials, protocol, and discovery behavior. A successful settings save is not evidence that monitoring now works.

What I take from this work

I document the configuration changes, the coverage I could verify, and the warnings that still need investigation. A device that responds on the network may still be missing the sensors we need.

Selected technical details

Investigate the result.

Generalized examples from hands-on work. Expand each to see the observation, interpretation, and follow-up.

Discovery without sensorsConfiguration changed → discovery returned zero sensors

Observed

A discovery test produced no sensors after a configuration change.

Interpretation

The intended monitoring coverage remained unverified.

Follow-up

Preserve the result, investigate the discovery path, and document the next manual check rather than report the device as fully monitored.

Reachable certificate, unresolved trustReachability ≠ certificate-chain validation

Observed

Reviewed SSL warnings where certificates were reachable and unexpired.

Interpretation

Certificate-chain trust or revocation validation could still be unresolved.

Follow-up

Keep the warning visible and document the trust or revocation investigation. Avoid suppressing validation simply to clear the dashboard.

Examples describe engineering methods. Client identities, endpoint identifiers, credentials, and ticket contents are omitted.

Need help with something similar?

Facing a similar technical problem?

This is an example of my experience, not an endorsement from an independent client. If you need similar help, take a look at my services or send me a description of the problem.