This repository was archived by the owner on Mar 30, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathoverview.html
More file actions
502 lines (384 loc) · 28.5 KB
/
Copy pathoverview.html
File metadata and controls
502 lines (384 loc) · 28.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>1. What is Flopsar — Flopsar Documentation</title>
<link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="_static/hacks.css" type="text/css" />
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="1. Installation" href="admin.html" />
<link rel="prev" title="Flopsar 2.4 Documentation" href="index.html" />
<script src="_static/js/modernizr.min.js"></script>
</head>
<body class="wy-body-for-nav">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-scroll">
<div class="wy-side-nav-search">
<a href="index.html">
<img src="_static/flopsar_logo.png" class="logo" alt="Logo"/>
</a>
<div class="version">
2.4
</div>
<div role="search">
<form id="rtd-search-form" class="wy-form" action="search.html" method="get">
<input type="text" name="q" placeholder="Search docs" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
<p class="caption"><span class="caption-text">Overview</span></p>
<ul class="current">
<li class="toctree-l1 current"><a class="current reference internal" href="#">1. What is Flopsar</a></li>
<li class="toctree-l1"><a class="reference internal" href="#versioning">2. Versioning</a></li>
<li class="toctree-l1"><a class="reference internal" href="#releasing">3. Releasing</a></li>
<li class="toctree-l1"><a class="reference internal" href="#licensing">4. Licensing</a></li>
<li class="toctree-l1"><a class="reference internal" href="#architectural-fundamentals">5. Architectural Fundamentals</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#networking">5.1. Networking</a></li>
<li class="toctree-l2"><a class="reference internal" href="#agent">5.2. Agent</a></li>
<li class="toctree-l2"><a class="reference internal" href="#manager">5.3. Manager</a></li>
<li class="toctree-l2"><a class="reference internal" href="#database">5.4. Database</a></li>
<li class="toctree-l2"><a class="reference internal" href="#workstation">5.5. Workstation</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="#supported-platforms-and-requirements">6. Supported Platforms and Requirements</a></li>
<li class="toctree-l1"><a class="reference internal" href="#distribution-package">7. Distribution Package</a></li>
<li class="toctree-l1"><a class="reference internal" href="#release-notes">8. Release Notes</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#how-to-upgrade-from-flopsar-2-3">8.1. How to upgrade from Flopsar 2.3</a></li>
</ul>
</li>
</ul>
<p class="caption"><span class="caption-text">Administrator Guide</span></p>
<ul>
<li class="toctree-l1"><a class="reference internal" href="admin.html">1. Installation</a></li>
<li class="toctree-l1"><a class="reference internal" href="admin.html#logging">2. Logging</a></li>
<li class="toctree-l1"><a class="reference internal" href="admin.html#id2">3. Agent</a></li>
<li class="toctree-l1"><a class="reference internal" href="manager.html">4. Manager</a></li>
<li class="toctree-l1"><a class="reference internal" href="database.html">5. Database</a></li>
</ul>
<p class="caption"><span class="caption-text">User Guide</span></p>
<ul>
<li class="toctree-l1"><a class="reference internal" href="user.html">1. Workstation Installation</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#accessing-flopsar-environment">2. Accessing Flopsar Environment</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#start-page">3. Start Page</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#settings">4. Settings</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#configurations">5. Configurations</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#galaxies">6. Galaxies</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#agents">7. Agents</a></li>
<li class="toctree-l1"><a class="reference internal" href="user.html#queries">8. Queries</a></li>
</ul>
<p class="caption"><span class="caption-text">Developer Guide</span></p>
<ul>
<li class="toctree-l1"><a class="reference internal" href="developer.html">1. Agent API</a></li>
<li class="toctree-l1"><a class="reference internal" href="developer.html#agent-formatters">2. Agent Formatters</a></li>
<li class="toctree-l1"><a class="reference internal" href="developer.html#database-api">3. Database API</a></li>
<li class="toctree-l1"><a class="reference internal" href="developer.html#plugins">4. Plugins</a></li>
</ul>
<p class="caption"><span class="caption-text">Miscellaneous</span></p>
<ul>
<li class="toctree-l1"><a class="reference internal" href="tshooting.html">Troubleshooting</a></li>
<li class="toctree-l1"><a class="reference internal" href="demo.html">Demo</a></li>
<li class="toctree-l1"><a class="reference internal" href="contrib.html">Third-party Components</a></li>
</ul>
</div>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" aria-label="top navigation">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="index.html">Flopsar</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href="index.html">Docs</a> »</li>
<li>1. What is Flopsar</li>
<li class="wy-breadcrumbs-aside">
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
<div class="section" id="what-is-flopsar">
<h1>1. What is Flopsar<a class="headerlink" href="#what-is-flopsar" title="Permalink to this headline">¶</a></h1>
<p>What is the most important thing in systems maintenance? Systems maintenance relies on making the systems highly available and responsive. This implies that we must maintain the number of outages as low as possible and the time needed to resolve any issues must be as short as possible. However, if the worst happens and the system fails, besides the fact it failed we need to know why. Knowing why is not sufficient if finding the cause lasts for a whole day or even longer. These are the main problems which need to be addressed.</p>
<p>Flopsar is a <em>Fault Detection and Diagnosis</em> software for Java systems. Its main goal is to detect errors and problems in your Java systems and help to find the root cause quickly. Unlike other APM-like tools, Flopsar does not require users to predict what may go wrong in their systems. Moreover, we do not lose information about your business processing by collecting only some vague averages and aggregated data. Flopsar is highly customizable and extensible product. It does not adhere to any specific Java applications, it just needs JVM.</p>
<p>How do we help users to find the root cause of problems, actually? Flopsar GUI application has a novel feature, called <em>Galaxy</em> view. This is a system overview, which enables users to observe any suspicious behavior. Usually, when something goes wrong in the system it is clearly visible in the Galaxy view. It is manifested by some anomaly patterns emergence. Users can quickly investigate what causes such patterns. In fact, by two-step drill down users are able to know the root cause of the problems represented by these patterns very quickly.</p>
<p>The whole idea standing behind our Galaxy view is simply a human brilliant feature of pattern recognition. It is so powerful, that the more users work with the Galaxy view, the faster he or she is able to find the root cause of the problem. If users are experienced enough they do not have to investigate deeper, they just know what goes wrong only by the pattern itself!</p>
<p>Flopsar has more key features which helps users to maintain their systems better. Its area of application is not only limited to systems maintenance, it is also used in applications development processes successfully. Its features can be extended by using so-called <em>formatters</em>, which enable users to perform extra processing at runtime, with no application source code changes.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Flopsar ® is a trademark of Flopsar Technology Sp. z o.o., registered in the EU.</p>
</div>
</div>
<div class="section" id="versioning">
<h1>2. Versioning<a class="headerlink" href="#versioning" title="Permalink to this headline">¶</a></h1>
<p>Every version label is composed of three numbers <span class="code">X.Y.Z</span>:</p>
<dl class="docutils">
<dt><span class="opt">X</span></dt>
<dd>Major version number: major changes, e.g. architecture change.</dd>
<dt><span class="opt">Y</span></dt>
<dd>Minor version number: minor changes, e.g. new functionalities.</dd>
<dt><span class="opt">Z</span></dt>
<dd>Small version number: bugs fixes.</dd>
</dl>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Versions <span class="opt">X.Y</span> are equivalent to <span class="opt">X.Y.0</span>.</p>
</div>
<p>You should not mix binaries form different releases, since they are usually not compatible. You can mix only those binaries, which have the same both major and minor release numbers.</p>
<div class="admonition warning">
<p class="first admonition-title">Warning</p>
<p class="last">Incompatible components are unable to work together. Any connection between two incompatible components is dropped.</p>
</div>
</div>
<div class="section" id="releasing">
<h1>3. Releasing<a class="headerlink" href="#releasing" title="Permalink to this headline">¶</a></h1>
<p>Flopsar major/minor (<span class="opt">X.Y</span>) versions are released once a year. Bug fixes releases (<span class="opt">X.Y.Z</span>) do not follow this rule, which means they can be released more often.</p>
</div>
<div class="section" id="licensing">
<h1>4. Licensing<a class="headerlink" href="#licensing" title="Permalink to this headline">¶</a></h1>
<p>Flopsar is a proprietary software and you need a valid license to run it. The license is a <code class="docutils literal notranslate"><span class="pre">license.key</span></code> file, which should be obtained separately. There are some restrictions on the Flopsar usage depending on the license type you purchased.</p>
</div>
<div class="section" id="architectural-fundamentals">
<h1>5. Architectural Fundamentals<a class="headerlink" href="#architectural-fundamentals" title="Permalink to this headline">¶</a></h1>
<p>Flopsar consists of four main components, i.e. <a class="reference internal" href="#agent"><span class="std std-ref">Agent</span></a>, <a class="reference internal" href="#manager"><span class="std std-ref">Manager</span></a>, <a class="reference internal" href="#database"><span class="std std-ref">Database</span></a> and <a class="reference internal" href="#workstation"><span class="std std-ref">Workstation</span></a>. There is one extra component Flopsar Database Connector (<span class="flp">fdbc</span>), which allow to access Flopsar environment.</p>
<div class="figure align-center" id="id8">
<img alt="_images/architecture.svg" src="_images/architecture.svg" /><p class="caption"><span class="caption-number">Fig. 5.1 </span><span class="caption-text">Flopsar Architecture</span></p>
</div>
<p>The picture above shows the Flopsar architecture of the entire environment. There can be only one <span class="flp">manager</span> instance per environment. The rest of the components can run in multiple instances. The links denote all the TCP connections in the environment. The arrows denote data flow direction. Almost all of the connections are bidirectional except the ones from <span class="flp">agent</span> to <span class="flp">database</span> instances.</p>
<div class="section" id="networking">
<h2>5.1. Networking<a class="headerlink" href="#networking" title="Permalink to this headline">¶</a></h2>
<p>There are three TCP servers running in the Flopsar environment. In order to run the environment successfully, you must prepare your network so that it allows all the required connections to be established.</p>
<div class="figure align-center" id="id9">
<span id="id1"></span><img alt="_images/networking.svg" src="_images/networking.svg" /><p class="caption"><span class="caption-number">Fig. 5.2 </span><span class="caption-text">Flopsar Environment Networking</span></p>
</div>
<p>The servers addresses are configured in the corresponding configuration files of each relevant component (see <a class="reference internal" href="manager.html#manager-conf"><span class="std std-ref">Configuration</span></a> and <a class="reference internal" href="database.html#database-conf"><span class="std std-ref">Configuration</span></a> for details). Each FDBC client establishes two TCP connections per single database instance. The first connection is responsible for providing online data, while the second one for handling user queries.</p>
</div>
<div class="section" id="agent">
<span id="id2"></span><h2>5.2. Agent<a class="headerlink" href="#agent" title="Permalink to this headline">¶</a></h2>
<p>The agent is a single jar file <code class="file docutils literal notranslate"><span class="pre">flopsar-agent-2.4.jar</span></code>. It is written entirely in Java and is based on <a class="reference external" href="http://asm.ow2.org">ASM</a> instrumentation framework. It was designed with performance in mind, so that it has a minimal impact on the JVM performance. It does not perform any processing, it just collects the data and sends them as soon as possible.</p>
<p>When a JVM starts, the agent connects to the <span class="flp">manager</span> instance. It is the agent that initiates a connection to the <span class="flp">manager</span>, i.e. there is no agent internal server, waiting for connections. When the agent establishes its connection to the <span class="flp">manager</span>, it starts a separate thread which opens a channel for incoming <span class="flp">manager</span> messages. The communication between agent and <span class="flp">manager</span> is bidirectional. If the agent loses its connection to the <span class="flp">manager</span> it will try to reconnect automatically.</p>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last">If you want to change the agent file name, you should also change the value of <span class="opt">Boot-Class-Path</span> entry in the manifest file of the agent jar accordingly.</p>
</div>
</div>
<div class="section" id="manager">
<span id="id3"></span><h2>5.3. Manager<a class="headerlink" href="#manager" title="Permalink to this headline">¶</a></h2>
<p><span class="flp">manager</span> is a central point of the entire environment. It stores and serves Agent configurations, manages users authentication, forwards data from agents to <span class="flp">fdbc</span> clients, etc. It is a single point of failure because there is only one instance of it per environment. However, when the environment is set, i.e. agents configurations are deployed and agents are attached to their databases, <span class="flp">manager</span> is not required as long as no configuration changes or data query operations are needed.
In other words, if <span class="flp">manager</span> is down the data acquisition process goes on.</p>
<div class="figure align-center" id="id10">
<img alt="_images/manager.svg" src="_images/manager.svg" /><p class="caption"><span class="caption-number">Fig. 5.3 </span><span class="caption-text"><span class="flp">manager</span> Processes</span></p>
</div>
<p><span class="flp">manager</span> operates two processes, the <span class="opt">MASTER</span> process and its child process: <span class="opt">FSM</span>.
If a child process crashes <span class="opt">MASTER</span> will spawn a new one immediately.
<span class="flp">manager</span> runs a single TCP server, which accepts connections from three types of clients: <span class="flp">agent</span>, <span class="flp">database</span> and <span class="flp">fdbc</span>.
There can be multiple Flopsar environments running on the same server machine as long as they use their own license files with distinct IP addresses.</p>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last">License file cannot be shared between different Flopsar environments that run on the very same machine.</p>
</div>
</div>
<div class="section" id="database">
<span id="id4"></span><h2>5.4. Database<a class="headerlink" href="#database" title="Permalink to this headline">¶</a></h2>
<p><span class="flp">database</span> operates four processes: <span class="opt">MASTER</span>, <span class="opt">FDB</span>, <span class="opt">FPU</span> and <span class="opt">ADM</span>. When <span class="flp">database</span> starts it creates its <span class="opt">MASTER</span> process, which spawns the other processes. Whenever one of the child processes crashes (except <span class="opt">ARCH</span>), <span class="opt">MASTER</span> respawns it immediately. There is an additional child process <span class="opt">ARCH</span>, which is spawned periodically to do its job. When the job is done it is closed.</p>
<div class="figure align-center" id="id11">
<img alt="_images/database.svg" src="_images/database.svg" /><p class="caption"><span class="caption-number">Fig. 5.4 </span><span class="caption-text"><span class="flp">database</span> Processes</span></p>
</div>
<p>Each child process has its own area of responsibility:</p>
<dl class="docutils">
<dt><span class="opt">MASTER</span></dt>
<dd>This process is responsible for watching its children mainly.</dd>
<dt><span class="opt">FDB</span></dt>
<dd>This process runs a TCP server, which receives data from agents. It is responsible for data persistence.</dd>
<dt><span class="opt">FPU</span></dt>
<dd>This process runs a TCP server, which handles <span class="flp">fdbc</span> requests.</dd>
<dt><span class="opt">ADM</span></dt>
<dd>This process runs a TCP client, which communicates with <span class="flp">manager</span>.</dd>
<dt><span class="opt">ARCH</span></dt>
<dd>This process is responsible for data archiving (see <a class="reference internal" href="database.html#archive"><span class="std std-ref">Data Archiving</span></a> for details). It is spawned if and only if the archive feature is enabled in the configuration file.</dd>
</dl>
<p><span class="flp">database</span> is a native application and it supports platforms specified in <a class="reference internal" href="#support"><span class="std std-ref">Supported Platforms and Requirements</span></a>. The memory and CPU requirements strongly depend on how much data the database will be receiving and how many clients will be handling.</p>
<p><span class="flp">database</span> is designed to take advantage of multiple CPU cores. There are internal tasks that can run in parallel provided that there are enough CPU cores. These tasks are responsible for collecting and persisting data. Every four additional CPU cores enable to run a new, additional task. How many tasks <span class="flp">database</span> will run is decided at the database initialization step and cannot be changed later. So if you can provide a multiple cores CPU, do it before you initialize a database environment.</p>
<p><span class="flp">database</span> collects received method calls in so-called collectors in memory. The collector is assigned to each agent connection and its size depends on methods instrumentation and your application. 8 GB of RAM is a reasonable minimum you should provide.</p>
</div>
<div class="section" id="workstation">
<span id="id5"></span><h2>5.5. Workstation<a class="headerlink" href="#workstation" title="Permalink to this headline">¶</a></h2>
<p>It is written in <a class="reference external" href="http://kotlinlang.org">Kotlin</a> and based on the <a class="reference external" href="http://docs.oracle.com/javase/8/javafx/get-started-tutorial/jfx-overview.htm#JFXST784">JavaFX</a> platform.</p>
</div>
</div>
<div class="section" id="supported-platforms-and-requirements">
<span id="support"></span><h1>6. Supported Platforms and Requirements<a class="headerlink" href="#supported-platforms-and-requirements" title="Permalink to this headline">¶</a></h1>
<p><span class="flp">agent</span> is written entirely in Java and supports JVM 1.6, 1.7, 1.8 and 9.
<span class="flp">workstation</span> is written in <a class="reference external" href="http://kotlinlang.org">Kotlin</a> and requires JVM 1.8u131+. It can be run only on those platforms which are supported by <a class="reference external" href="http://docs.oracle.com/javase/8/javase-clienttechnologies.htm">JavaFX</a>.</p>
<table border="1" class="docutils">
<colgroup>
<col width="63%" />
<col width="37%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Virtual Machine</th>
<th class="head">Version</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>JVM</td>
<td>1.8u131+</td>
</tr>
</tbody>
</table>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last"><span class="flp">workstation</span> does not support JVM 9.</p>
</div>
<p>Both <span class="flp">manager</span> and <span class="flp">database</span> are native executables and they can be run only on the platforms listed below:</p>
<table border="1" class="docutils">
<colgroup>
<col width="63%" />
<col width="37%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Operating System</th>
<th class="head">Architecture</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>GNU/Linux 2.6.33+</td>
<td>x86_64</td>
</tr>
</tbody>
</table>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last">Native components do not support 32bit platforms.</p>
</div>
</div>
<div class="section" id="distribution-package">
<h1>7. Distribution Package<a class="headerlink" href="#distribution-package" title="Permalink to this headline">¶</a></h1>
<p>Flopsar distribution binaries include:</p>
<dl class="docutils">
<dt><code class="file docutils literal notranslate"><span class="pre">flopsar-2.4-Linux.deb</span></code></dt>
<dd>Flopsar <span class="flp">manager</span> and <span class="flp">database</span> Debian package.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">flopsar-2.4-Linux.rpm</span></code></dt>
<dd>Flopsar <span class="flp">manager</span> and <span class="flp">database</span> RPM package.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">workstation-2.4.zip</span></code></dt>
<dd>Flopsar Workstation application.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">flopsar-agent-2.4.jar</span></code></dt>
<dd>Flopsar Agent for JVM 8 and earlier.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">flopsar-agent-2.4-jvm9.jar</span></code></dt>
<dd>Flopsar Agent for JVM 9+.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">EULA</span></code></dt>
<dd>End User License Agreement</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">SHA256</span></code></dt>
<dd>sha256 checksums of all the binaries.</dd>
<dt><code class="file docutils literal notranslate"><span class="pre">SHA256.sig</span></code></dt>
<dd>PGP signed <code class="docutils literal notranslate"><span class="pre">SHA256</span></code> file. In order to verify the signature use our <a class="reference external" href="http://flopsar.com/pgp">PGP public key</a>. You can find it at <a class="reference external" href="http://flopsar.com/pgp">http://flopsar.com/pgp</a>.</dd>
</dl>
</div>
<div class="section" id="release-notes">
<h1>8. Release Notes<a class="headerlink" href="#release-notes" title="Permalink to this headline">¶</a></h1>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last">Flopsar 2.2 and earlier versions are no longer supported.</p>
</div>
<div class="topic">
<p class="topic-title first">Changes in <span class="flp">workstation</span></p>
<ul class="simple">
<li>GC graphs removed from agent details view.</li>
<li>Start page redesigned.</li>
<li>Optimizations.</li>
</ul>
</div>
<div class="topic">
<p class="topic-title first">Changes in <span class="flp">database</span>/<span class="flp">manager</span></p>
<ul class="simple">
<li>Parameters compression algorithm changed to LZ4.</li>
<li>Internal authentication embedded in the <span class="flp">manager</span>.</li>
<li>Optimizations.</li>
</ul>
</div>
<div class="topic">
<p class="topic-title first">Changes in <span class="flp">fdbc</span></p>
<ul class="simple">
<li>New C/C++ API for accessing database data.</li>
</ul>
</div>
<div class="section" id="how-to-upgrade-from-flopsar-2-3">
<h2>8.1. How to upgrade from Flopsar 2.3<a class="headerlink" href="#how-to-upgrade-from-flopsar-2-3" title="Permalink to this headline">¶</a></h2>
<p>In order to upgrade to 2.4 you must replace each 2.3 component with the new one.</p>
<div class="admonition important">
<p class="first admonition-title">Important</p>
<p class="last">License keys have been changed. Please, request a new license key before upgrade. Your current license files will not work with Flopsar 2.3.</p>
</div>
<p>If you already have Flopsar 2.3 installed and running, follow the instructions below to upgrade your environment:</p>
<ol class="arabic">
<li><p class="first">Stop your manager and databases.</p>
</li>
<li><p class="first">Install Flopsar 2.4 version binaries.</p>
</li>
<li><p class="first">Migrate your current database to a new version. Before you start migrating, make a copy of your current database files. In order to migrate your database files, execute the following command:</p>
<blockquote>
<div><div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ fs2db start --action migrate <database_home>
</pre></div>
</div>
</div></blockquote>
</li>
<li><p class="first">If you use Flopsar internal authentication, comment out the <span class="opt">plugins</span> option in the manager configuration file.</p>
</li>
<li><p class="first">Upgrade agents and workstation.</p>
</li>
<li><p class="first">Start the manager and databases.</p>
</li>
</ol>
</div>
</div>
</div>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="admin.html" class="btn btn-neutral float-right" title="1. Installation" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right"></span></a>
<a href="index.html" class="btn btn-neutral" title="Flopsar 2.4 Documentation" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left"></span> Previous</a>
</div>
<hr/>
<div role="contentinfo">
<p>
© Copyright 2018, Flopsar Technology Sp. z o.o..
</p>
</div>
</footer>
</div>
</div>
</section>
</div>
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT:'./',
VERSION:'2.4',
LANGUAGE:'None',
COLLAPSE_INDEX:false,
FILE_SUFFIX:'.html',
HAS_SOURCE: false,
SOURCELINK_SUFFIX: '.txt'
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="_static/js/theme.js"></script>
<script type="text/javascript">
jQuery(function () {
SphinxRtdTheme.Navigation.enable(true);
});
</script>
</body>
</html>