Diagnostics, logs & application monitoring
The diagnosis requires benchmarks on the operation of the chain. Dtouch reconciles symptoms, events and logs to prepare for an intervention and verify its effect.
Concrete functions.
Tools in situ.
Interfaces used to organize work, prepare data and track files. Each screen shows a specific function, with presentation data.
Enlarge screen Read the state of the park in the same list
Servers, systems, sites, packages, certificates and date of survey are gathered to guide the diagnosis.
Real interface · test environment · demo data.
Enlarge screen View folder progress
Requests are grouped by status, with their subject, an overview of the exchanges and the team in charge.
Real interface · test environment · demo data.Reconstitute the route of the operation
We identify the request, the data used, the services called and the result obtained. Context information helps distinguish between an interface, file, or processing problem.
Editorial platforms and ERPs bring varied situations: task waiting, document not generated, import interrupted or resource unavailable.
Making states and errors exploitable
The logs must make it possible to situate an operation and understand what remains to be processed. The request and its result are compared to the business objects.
Rey’actif task monitoring, for example, supplemented the processing engines with a log management and consultation interface. These benchmarks serve the dialogue between production and developers.
Check assumptions before intervening
The diagnosis compares the observations with the data and the execution conditions. Testing and comparisons help isolate the step in question.
A visible error may have several origins. The work must avoid generalizing a correction without checking that it corresponds to the case encountered.
Follow the result and prepare for recovery
After intervention, we check the route and the logs concerned. The remaining treatments and restart conditions must be understood with the operation.
Useful information is kept for maintenance: problem context, correction, checks and dependencies. This transmission facilitates monitoring of the solution.
Projects and concrete situations.
Reymann : pilot developers and specialists
Founder's Experience · Reymann
Building an editorial platform requires an organization capable of linking internal developers, specialized partners and production teams. The Reymann route gives concrete reality to this piloting.
Explore the caseRey-Active: Connecting a complete platform
Founder's Experience · Reymann
PIM, office applications, web services, image tasks, InDesign Server and business bases: experience in the articulation between the components of a production platform.
Explore the caseDalim TWIST: unify flows and their parameters
Founder's Experience · Reymann
Moving from around twenty production flows to generic flows linked to file data: integration between 4D, Rey’actif, Dalim TWIST and ICC profiles.
Explore the caseYour job deserves
the right tools.
A specific need, a software to evolve, a project to frame.